-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Conversation
Refer to this link for build results (access rights to CI server needed): |
There was a problem hiding this 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"; |
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
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.
Refer to this link for build results (access rights to CI server needed): |
@kennknowles is the PR good to merge? |
Yes! |
Be sure to do all of the following to help us incorporate your contribution
quickly and easily:
[BEAM-<Jira issue #>] Description of pull request
mvn clean verify
. (Even better, enableTravis-CI on your fork and ensure the whole test matrix passes).
<Jira issue #>
in the title with the actual Jira issuenumber, if there is one.
Individual Contributor License Agreement.
R: @kennknowles