[
https://issues.apache.org/jira/browse/BEAM-12095?focusedWorklogId=577894&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-577894
]
ASF GitHub Bot logged work on BEAM-12095:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 06/Apr/21 20:57
Start Date: 06/Apr/21 20:57
Worklog Time Spent: 10m
Work Description: ibzib commented on pull request #14434:
URL: https://github.com/apache/beam/pull/14434#issuecomment-814435402
> is this caught be a test? can I verify it?
It's not caught in a test, though it probably should be. I'll write a unit
test for it.
You can verify it by running any Python pipeline using
`--runner=SparkRunner`, like I usually do for release verification. e.g.
```
python -m apache_beam.examples.wordcount --input /path/to/input \
--output /path/to/output \
--runner SparkRunner \
--spark_submit_uber_jar \
--spark_rest_url
https://localhost:6066 \
--environment_type LOOPBACK
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 577894)
Time Spent: 3h (was: 2h 50m)
> spark_runner.py broken by Spark 3 upgrade.
> ------------------------------------------
>
> Key: BEAM-12095
> URL: https://issues.apache.org/jira/browse/BEAM-12095
> Project: Beam
> Issue Type: Bug
> Components: runner-spark
> Reporter: Kyle Weaver
> Assignee: Kyle Weaver
> Priority: P1
> Fix For: 2.29.0
>
> Time Spent: 3h
> Remaining Estimate: 0h
>
> The logic that finds the Spark job server jar has been broken by the Spark 3
> upgrade, since it assumes the name of the jar corresponds directly to the
> Gradle target, which is no longer true.
> This path is still not documented properly, but some folks out there have
> already started using it (including TFX).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
