autophagy opened a new pull request, #27775:
URL: https://github.com/apache/flink/pull/27775

   ## What is the purpose of the change
   
   This pull request fixes the ROW function to preserve field names when 
arguments use AS aliases or field references. 
   
   Previously, the ROW function would always generate default field names (f0, 
f1, f2, etc.) even when users explicitly provided meaningful names through AS 
expressions or field references, requiring the user of the `f` columns or 
casting in things like subsequent `where` clauses.
   
   ## Brief change log
   
   - Added `getArgumentName(int pos)` method to the `CallContext` interface to 
expose argument names/aliases
   - Implemented name extraction in `ResolveCallByArgumentsRule` and 
`CallBindingCallContext` to extract names from AS expressions and 
FieldReferenceExpressions.
   - Modified `RowTypeStrategy` to use extracted argument names when available, 
falling back to default `f{idx}` naming when not
   
   ## Verifying this change
   
   This change added tests and can be verified as follows:
   
   - Added integration test `RowFunctionITCase` test case.
   
   ## Does this pull request potentially affect one of the following parts:
   
     - Dependencies (does it add or upgrade a dependency): no
     - The public API, i.e., is any changed class annotated with 
`@Public(Evolving)`: yes
     - The serializers: no
     - The runtime per-record code paths (performance sensitive): no
     - Anything that affects deployment or recovery: JobManager (and its 
components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
     - The S3 file system connector: no
   
   ## Documentation
   
     - Does this pull request introduce a new feature? yes
     - If yes, how is the feature documented? JavaDocs


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

Reply via email to