[CdapIO] Integration CdapIO with SparkReceiverIO
Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:
- [ ] Choose reviewer(s) and mention them in a comment (
R: @username). - [ ] Mention the appropriate issue in your description (for example:
addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, commentfixes #<ISSUE NUMBER>instead. - [ ] Update
CHANGES.mdwith noteworthy changes. - [ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.
See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)
See CI.md for more information about GitHub Actions CI.
Run Java PreCommit
Assigning reviewers. If you would like to opt out of this review, comment assign to next reviewer:
R: @lukecwik for label java. R: @Abacn for label io.
Available commands:
-
stop reviewer notifications- opt out of the automated review tooling -
remind me after tests pass- tag the comment author after tests pass -
waiting on author- shift the attention set back to the author (any comment or push by the author will return the attention set to the reviewers)
The PR bot will only process comments in the main thread (not review comments).
@chamikaramj @aromanenko-dev [CdapIO] Integration CdapIO with SparkReceiverIO PR is ready for review Thank you!
@chamikaramj @aromanenko-dev kindly remind you that PR is ready for the review :)
Run RAT PreCommit
Run Java_Examples_Dataflow PreCommit
@aromanenko-dev @chamikaramj @mosche All your comments have been addressed. Can we consider this PR ready for merge?
@chamikaramj @mosche Do you have additional comments on this PR?
LGTM @aromanenko-dev Though - unrelated - one more question @Lizzfox, what's the purpose / importance of Spark in the picture here? We're actually preparing the removal of the deprecated Spark2 runner (asap). The runner is badly broken and not usable anymore due to a Jackson dependency conflict (see #23568). Unfortunately this wasn't caught in local tests, but only if submitting a job to a Spark 2.4 cluster. Does this impact you?
@mosche we don't use Spark runner, we only support Dataflow runner in our implementation. Thanks