You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Kenneth Knowles (Jira)" <ji...@apache.org> on 2020/08/03 09:13:00 UTC
[jira] [Updated] (BEAM-10622) Prefix Gradle paths with a colon for
user-facing output
[ https://issues.apache.org/jira/browse/BEAM-10622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kenneth Knowles updated BEAM-10622:
-----------------------------------
Status: Open (was: Triage Needed)
> Prefix Gradle paths with a colon for user-facing output
> -------------------------------------------------------
>
> Key: BEAM-10622
> URL: https://issues.apache.org/jira/browse/BEAM-10622
> Project: Beam
> Issue Type: Bug
> Components: sdk-py-core
> Reporter: Maximilian Michels
> Assignee: Maximilian Michels
> Priority: P3
>
> When using the FlinkRunner with master, the job server needs to be build first. Beam prints out instructions for that, e.g.
> {noformat}
> RuntimeError: /Users/max/Dev/beam/runners/flink/1.10/job-server/build/libs/beam-runners-flink-1.10-job-server-2.24.0-SNAPSHOT.jar not found. Please build the server with
> cd /Users/max/Dev/beam; ./gradlew runners:flink:1.10:job-server:shadowJar
> {noformat}
> Note that the gradle path printed is not valid because it misses a colon before "runners".
> Internally, the Gradle path is used to resolve the jar locally or from Maven Central. Gradle paths always start with a colon. We should stick to that format although we can also parse Gradle paths which do not start with a colon.
> In order for the Gradle path printed to be valid, we should prefix Gradle path with colon.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)