[
https://issues.apache.org/jira/browse/FLINK-21863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-21863:
-----------------------------------
Labels: auto-deprioritized-major stale-minor (was:
auto-deprioritized-major)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is
still Minor, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> SortPartition should allow chaining of KeySelectors to support different
> sorting orders for the fields
> ------------------------------------------------------------------------------------------------------
>
> Key: FLINK-21863
> URL: https://issues.apache.org/jira/browse/FLINK-21863
> Project: Flink
> Issue Type: Improvement
> Components: API / DataSet
> Reporter: Etienne Chauchot
> Priority: Minor
> Labels: auto-deprioritized-major, stale-minor
>
> If we need to sort data in a DataSet using a KeySelector (for example to
> extract avro fields or when sort using field index or name is not available)
> we cannot have different sort orders for the fields. We can sort by a list of
> fields by making the keySelector return a tuple but they will all be sorted
> in the same order.
> To allow _sort by field 1 ASC, field 2 DESC_ kind of semantics with
> KeySelectors we need to be able to chain the KeySelectors like this
> {code:java}
> DataSet.sortPartition(field1KeySelector , Order.ASCENDING)
> .sortPartition(field2KeySelector, Order.DESCENDING)
> {code}
> which is currently not possible.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
