[
https://issues.apache.org/jira/browse/BEAM-11026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17241839#comment-17241839
]
Brian Hulette commented on BEAM-11026:
--------------------------------------
We should also consider how this will work for development environments.
Currently a nice feature of BeamJarExpansionService is that, when it detects
its running in a dev build (version number ends in .dev), it will look for the
gradle built jar, and if its not there, it prints the command necessary for the
user to build it. This makes some possibly incorrect assumptions about mapping
gradle task to directory, but it works for the current use-cases.
I wonder if we can do something similar when we identify the expansion service
by maven coords?
> When determining expansion service jar, depend on Maven coords instead of
> Gradle target
> ---------------------------------------------------------------------------------------
>
> Key: BEAM-11026
> URL: https://issues.apache.org/jira/browse/BEAM-11026
> Project: Beam
> Issue Type: Improvement
> Components: cross-language, sdk-py-core
> Reporter: Chamikara Madhusanka Jayalath
> Priority: P2
>
> For example here:
> https://github.com/apache/beam/blob/release-2.24.0/sdks/python/apache_beam/io/kafka.py#L107
> Maven coords is more stable than the Gradle target name so it's better to
> depend on the prior. See [1] for details.
> [1] https://issues.apache.org/jira/browse/BEAM-10986
>
> cc: [~robertwb] [~bhulette] [~kenn]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
