marc-pydantic opened a new issue, #18302:
URL: https://github.com/apache/datafusion/issues/18302
Here's an excerpt from the a `SELECT first_value(trace_id),
first_value(value), ...` query's schema:
```
...
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: "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: "is_set",
data_type: Boolean,
nullable: true,
dict_id: 0,
dict_is_ordered: false,
metadata: {},
},
```
The code generated field names for the value columns, but the `"is_set"`
name is fixed and clashes. While I do not know if duplicate field names are
okay in this place (I suspect they are), it would still be nice to have unique
names (this for now mitigates a bug in `datafusion-distributed`), as this is
can be added with little effort.
--
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]
