You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Flink Jira Bot (Jira)" <ji...@apache.org> on 2021/10/27 22:40:01 UTC

[jira] [Updated] (FLINK-21763) Extend Data Stream's batch mode to handle partitioning/grouping/ordering

     [ https://issues.apache.org/jira/browse/FLINK-21763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Flink Jira Bot updated FLINK-21763:
-----------------------------------
    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.


> Extend Data Stream's batch mode to handle partitioning/grouping/ordering
> ------------------------------------------------------------------------
>
>                 Key: FLINK-21763
>                 URL: https://issues.apache.org/jira/browse/FLINK-21763
>             Project: Flink
>          Issue Type: Improvement
>          Components: API / DataStream
>            Reporter: Alexis Sarda-Espinosa
>            Priority: Minor
>              Labels: auto-deprioritized-major, stale-minor
>
> In the DataSet API, an undocumented (?) feature is using [SplitDataProperties|[https://ci.apache.org/projects/flink/flink-docs-release-1.12/api/java/org/apache/flink/api/java/io/SplitDataProperties.html]] to specify different grouping/partitioning/sorting properties, so if the data is pre-sorted (e.g. when reading from a database), some operations can be optimized. Based on this, I assume the Flink scheduler already knows about such optimizations.
> The new batch mode for the Data Stream API doesn't have a way to specify this. I imagine something like this would be useful even for transformation operators, not only for sources, e.g. a flat map that gets an input "batch" and outputs new data with a different kind of grouping/sorting.
> I suppose these diractives would have to be ignored for the normal stream mode.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)