[SPARK-41398][SQL][FOLLOWUP] Update runtime filtering javadoc to reflect relaxed partition constraints

[yyanyy]

Update the javadoc for SupportsRuntimeV2Filtering.filter() and SupportsRuntimeFiltering.filter() to reflect the changes made in SPARK-41398, which relaxed the constraint on partition values during runtime filtering.

After that change, scans can now either:

• Replace partitions with no matching data with empty InputPartitions, or
• Report only a subset of the original partition values (omitting those with no data)

The previous documentation stated that the "overall number of partitions" must be preserved, which is no longer required. The only constraint is that new partition values not present in the original partitioning cannot be introduced.

What changes were proposed in this pull request?

A javadoc update to follow up on #38924

Why are the changes needed?

To make the java doc up to date for future implementer

Does this PR introduce any user-facing change?

No

How was this patch tested?

compile and checkstyle

Was this patch authored or co-authored using generative AI tooling?

Yes - Claude Opus 4.5

[github-actions]

JIRA Issue Information

=== Sub-task SPARK-41398 ===
Summary: SPJ: Relax constraints on Storage-Partitioned Join when partition keys after runtime filtering do not match
Assignee: Chao Sun
Status: Resolved
Affected: ["3.3.1"]

---

This comment was automatically generated by GitHub Actions

[yyanyy]

@sunchao @huaxingao @cloud-fan when you have a chance do you mind taking a look at this javadoc update PR, since you were involved in the original doc/changes that this modified? Thank you!

[cloud-fan]

thanks, merging to maser! (comment only, no need to run test)

[dongjoon-hyun]

Hi, @yyanyy and @cloud-fan .

SPARK-41398 was released as a part of Apache Spark 3.4.0 three years ago.
We cannot make a follow-up like this.

[dongjoon-hyun]

Maybe, it's a mistake of Claude Opus 4.5?

[yyanyy]

SPARK-41398 was released as a part of Apache Spark 3.4.0 three years ago. We cannot make a follow-up like this.

Thanks for the feedback @dongjoon-hyun ! Sorry I just joined the community and didn't realize follow-ups should be against open JIRA and not the old resolved ones, feedback noted.

[dongjoon-hyun]

Thank you for your participation, @yyanyy . Since we can mitigate before Apache Spark 4.2.0 release, there is no big deal here. It's a world-wide open-source community. :)

We just want to have a trace-ability for all commits at least in terms of Fix Version. So, we recommend to use [FOLLOWUP] tag inside a single release version only. Feel free to open a new JIRA issue, @yyanyy .