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

[Task]: Prepare removal of Spark2 runner #23728

Closed
8 tasks done
mosche opened this issue Oct 19, 2022 · 2 comments
Closed
8 tasks done

[Task]: Prepare removal of Spark2 runner #23728

mosche opened this issue Oct 19, 2022 · 2 comments

Comments

@mosche
Copy link
Member

mosche commented Oct 19, 2022

What needs to happen?

The Spark 2 has been deprecated for a while. Even more significant, it's actually in a badly broken state since long due to classpath issues when running on a Spark cluster (#23568).

Before Spark 2 support can be removed, all documentation and dependent components should be migrated to use Spark 3.

Notes:

  • Test examples against Spark 3
  • Java Quickstart on Spark 3
  • Remove obsolete sparkRunner from Hadoop-format
  • Use Spark 3 as default for portable Spark job-server.
  • Validate Go & Python against Spark 3
  • Bump metrics-core to match version used by Spark 3 (4.1.1)
  • Nexmark, Tpcds, Load tests
  • Jpms tests (cleanup build)

Issue Priority

Priority: 2

Issue Component

Component: runner-spark

mosche pushed a commit to mosche/beam that referenced this issue Oct 19, 2022
mosche pushed a commit to mosche/beam that referenced this issue Oct 19, 2022
mosche pushed a commit to mosche/beam that referenced this issue Oct 19, 2022
@github-actions github-actions bot added the P2 label Oct 19, 2022
mosche pushed a commit to mosche/beam that referenced this issue Oct 20, 2022
mosche pushed a commit to mosche/beam that referenced this issue Oct 20, 2022
mosche pushed a commit to mosche/beam that referenced this issue Oct 20, 2022
mosche pushed a commit to mosche/beam that referenced this issue Oct 20, 2022
mosche pushed a commit to mosche/beam that referenced this issue Oct 21, 2022
@mosche mosche self-assigned this Oct 21, 2022
@aromanenko-dev
Copy link
Contributor

Should all sub-tasks be finished within one Beam release or it's not required?

@mosche
Copy link
Member Author

mosche commented Oct 24, 2022

Should all sub-tasks be finished within one Beam release or it's not required?

No need for that, these tasks are pretty independent.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants