gengliangwang opened a new pull request, #56537:
URL: https://github.com/apache/spark/pull/56537

   ### What changes were proposed in this pull request?
   
   Follow-up to #54394 (SPARK-55617). Two documentation-only changes to the 
DSv2 connector expression `VariantGet`:
   
   - Correct the `@since` tag from `4.1.0` to `4.3.0`.
   - Expand the class Javadoc (previously just "Variant get expression.") to 
describe what the expression represents.
   
   ### Why are the changes needed?
   
   This addresses a [review 
comment](https://github.com/apache/spark/pull/54394#discussion_r3417960739) on 
the original PR: `VariantGet` was marked `@since 4.1.0`, which does not match 
where the API actually ships. The change lands on master (5.0.0) and is 
backported to branch-4.x, so the API first appears in 4.3.0; the `@since` tag 
should reflect that. The original one-line class doc also did not explain what 
the expression is or how it maps to `variant_get` / `try_variant_get`.
   
   > Note: `VariantExtraction` and `SupportsPushDownVariantExtractions` (added 
under SPARK-54656) carry the same `@since 4.1.0` and likely need an analogous 
follow-up under that ticket. They are intentionally left out of this PR to keep 
it scoped to SPARK-55617.
   
   ### Does this PR introduce _any_ user-facing change?
   
   No behavior change. This only updates Javadoc and the `@since` tag so the 
published API documentation is accurate.
   
   ### How was this patch tested?
   
   Documentation-only change (Javadoc and `@since`); there is no code change, 
so no tests were added. Verified the new comment lines stay within the Java 
checkstyle line-length limit.
   
   ### Was this patch authored or co-authored using generative AI tooling?
   
   Yes, generated with the assistance of Claude Code (Anthropic).
   
   This pull request and its description were written by Isaac.
   


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

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to