Optimized SparkRunner ParDo Operation

[twosom]

Please add a meaningful description for your change here

fixes #32537

This PR contains these changes

• optimized to skip filter operation when there is only single output
• add related test

---

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

• 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, comment fixes #<ISSUE NUMBER> instead.
• Update CHANGES.md with 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 or the workflows README to see a list of phrases to trigger workflows.

[github-actions]

Assigning reviewers. If you would like to opt out of this review, comment assign to next reviewer:

R: @damondouglas added as fallback since no labels match configuration

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).

[Abacn]

Thanks for the change. I saw several changes of Spark runner improvement this PR and #32610 . If you are looking for reviewer a suggestion here is to send an email to beam devlist (https://lists.apache.org/list.html?dev@beam.apache.org) introducing these changes and ask people who are familiar with Beam Spark Runner for review

[Abacn]

thanks, just had a minor comment

By any chance is it able to test the performance diff?

[twosom]

thanks, just had a minor comment

By any chance is it able to test the performance diff?

@Abacn
I tested it on a 40GB DNA dataset.
It's a pipeline that simply counts the number of DNA elements.
Firstly, the DAG is less verbose because it's stripped of unnecessary filters.
In terms of performance, unfortunately, I didn't see a dramatic change at 40GB, which I don't think you'll notice unless you're working with very large datasets, as it simply removes redundant filter operations.
(It did have a slight effect though).
In the picture, the left side is the pipeline after this PR, and the right side is the old pipeline.