marc-pydantic opened a new pull request, #18303:
URL: https://github.com/apache/datafusion/pull/18303
## Which issue does this PR close?
- Closes #18302
## Rationale for this change
As described in the issue, this is a low-effort QoL fix for now.
## What changes are included in this PR?
Uses the existing function for naming fields to replace the hardcoded
`"is_set"` with a field-dependent name. Example output:
```
Field {
name: "first_value(records_partitioned.trace_id)[first_value]",
data_type: Utf8View,
nullable: true,
dict_id: 0,
dict_is_ordered: false,
metadata: {},
},
Field {
name: "first_value(records_partitioned.trace_id)[first_value_is_set]",
data_type: Boolean,
nullable: true,
dict_id: 0,
dict_is_ordered: false,
metadata: {},
},
Field {
name: "first_value(records_partitioned.value)[first_value]",
data_type: Int32,
nullable: true,
dict_id: 0,
dict_is_ordered: false,
metadata: {},
},
Field {
name: "first_value(records_partitioned.value)[first_value_is_set]",
data_type: Boolean,
nullable: true,
dict_id: 0,
dict_is_ordered: false,
metadata: {},
},
```
## Are these changes tested?
No tests have been added, hopefully it should be covered by existing changes.
## Are there any user-facing changes?
There should not be any, I assume `is_set` is never user visible.
--
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]
