Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BEAM-980] Support configuration of Apex DAG through properties file. #1850

Merged
merged 1 commit into from
Jan 27, 2017

Conversation

tweise
Copy link
Contributor

@tweise tweise commented Jan 26, 2017

Be sure to do all of the following to help us incorporate your contribution
quickly and easily:

  • Make sure the PR title is formatted like:
    [BEAM-<Jira issue #>] Description of pull request
  • Make sure tests pass via mvn clean verify. (Even better, enable
    Travis-CI on your fork and ensure the whole test matrix passes).
  • Replace <Jira issue #> in the title with the actual Jira issue
    number, if there is one.
  • If this contribution is large, please file an Apache
    Individual Contributor License Agreement.

R: @kennknowles

@coveralls
Copy link

Coverage Status

Coverage decreased (-0.003%) to 69.751% when pulling 02bbf43 on tweise:BEAM-980 into 1c6e667 on apache:master.

@asfbot
Copy link

asfbot commented Jan 26, 2017

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/beam_PreCommit_Java_MavenInstall/6821/
--none--

Copy link
Member

@kennknowles kennknowles left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me. One little comment/question.

* The runner will look for this file in the classpath for Apex configuration properties
* unless an alternative location was specified in pipeline options.
*/
public static final String RUNNER_PROPERTIES_RESOURCE = "/beam-runners-apex.properties";
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Any reason it isn't a @Default on the pipeline option?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, wanted to do that also, would be better from a documentation perspective. But a value starting with '/' is interpreted as local file path, while the default is a classpath resource. Any idea how to handle that?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated with explicit URL scheme for classpath and made the default visible through the options.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 69.742% when pulling 31c63cb on tweise:BEAM-980 into 47304d1 on apache:master.

@asfbot
Copy link

asfbot commented Jan 27, 2017

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/beam_PreCommit_Java_MavenInstall/6850/
--none--

@tweise
Copy link
Contributor Author

tweise commented Jan 27, 2017

@kennknowles is the PR good to merge?

@kennknowles
Copy link
Member

Yes!

@asfgit asfgit merged commit 31c63cb into apache:master Jan 27, 2017
asfgit pushed a commit that referenced this pull request Jan 27, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants