lksvenoy-r7 opened a new issue, #8175:
URL: https://github.com/apache/iceberg/issues/8175
### Feature Request / Improvement
This feature request encompasses supporting specifying partitions and sort
order on nested structs. It does not make sense to support this on lists nor
maps, as these are collections with multiple values.
When ingesting data from different sources today, you have to flatten
structs to the root-level of the table to allow partitioning and sorting on a
specific column. While this is fine, being able to support partitioning on
structs would allow for more flexibility in how a schema is defined.
For a concrete example, consider a schema for a table that looks like this
```
{
eventId,
...
timestamps {
createdAt,
lastSeenAt,
}
}
```
If nested partitioning and sorting on structs was natively supported,
defining a partition spec or sort order could be achieved without unnesting the
structure. A json path could be used to define these specs, for example:
```
day(timestamps.createdAt)
```
And for sort order, in the same vein
```
{
sortBy: timestamps.lastSeenAt,
sortDirection: DESC,
nullOrder: NULLS_LAST,
caseSensitive: false
}
```
### Query engine
None
--
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]
