[jira] [Updated] (FLINK-1493) Support for streaming jobs preserving global ordering of records
[ https://issues.apache.org/jira/browse/FLINK-1493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flink Jira Bot updated FLINK-1493: -- Labels: auto-deprioritized-major auto-deprioritized-minor (was: auto-deprioritized-major stale-minor) Priority: Not a Priority (was: Minor) This issue was labeled "stale-minor" 7 days ago and has not received any updates so it is being deprioritized. If this ticket is actually Minor, please raise the priority and ask a committer to assign you the issue or revive the public discussion. > Support for streaming jobs preserving global ordering of records > > > Key: FLINK-1493 > URL: https://issues.apache.org/jira/browse/FLINK-1493 > Project: Flink > Issue Type: New Feature > Components: API / DataStream >Reporter: Márton Balassi >Priority: Not a Priority > Labels: auto-deprioritized-major, auto-deprioritized-minor > > Distributed streaming jobs do not give total, global ordering guarantees for > records only partial ordering is provided by the system: records travelling > on the same exact route of the physical plan are ordered, but they aren't > between routes. > It turns out that although this feature can only be implemented via "merge > sorting" in the input buffers on a timestamp field thus creating substantial > latency is still desired for a number of applications. > Just a heads up for the implementation: the sorting introduces back pressure > in the buffers and might cause deadlocks. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (FLINK-1493) Support for streaming jobs preserving global ordering of records
[ https://issues.apache.org/jira/browse/FLINK-1493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flink Jira Bot updated FLINK-1493: -- 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. > Support for streaming jobs preserving global ordering of records > > > Key: FLINK-1493 > URL: https://issues.apache.org/jira/browse/FLINK-1493 > Project: Flink > Issue Type: New Feature > Components: API / DataStream >Reporter: Márton Balassi >Priority: Minor > Labels: auto-deprioritized-major, stale-minor > > Distributed streaming jobs do not give total, global ordering guarantees for > records only partial ordering is provided by the system: records travelling > on the same exact route of the physical plan are ordered, but they aren't > between routes. > It turns out that although this feature can only be implemented via "merge > sorting" in the input buffers on a timestamp field thus creating substantial > latency is still desired for a number of applications. > Just a heads up for the implementation: the sorting introduces back pressure > in the buffers and might cause deadlocks. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (FLINK-1493) Support for streaming jobs preserving global ordering of records
[ https://issues.apache.org/jira/browse/FLINK-1493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flink Jira Bot updated FLINK-1493: -- Labels: auto-deprioritized-major (was: stale-major) > Support for streaming jobs preserving global ordering of records > > > Key: FLINK-1493 > URL: https://issues.apache.org/jira/browse/FLINK-1493 > Project: Flink > Issue Type: New Feature > Components: API / DataStream >Reporter: Márton Balassi >Priority: Major > Labels: auto-deprioritized-major > > Distributed streaming jobs do not give total, global ordering guarantees for > records only partial ordering is provided by the system: records travelling > on the same exact route of the physical plan are ordered, but they aren't > between routes. > It turns out that although this feature can only be implemented via "merge > sorting" in the input buffers on a timestamp field thus creating substantial > latency is still desired for a number of applications. > Just a heads up for the implementation: the sorting introduces back pressure > in the buffers and might cause deadlocks. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FLINK-1493) Support for streaming jobs preserving global ordering of records
[ https://issues.apache.org/jira/browse/FLINK-1493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flink Jira Bot updated FLINK-1493: -- Priority: Minor (was: Major) > Support for streaming jobs preserving global ordering of records > > > Key: FLINK-1493 > URL: https://issues.apache.org/jira/browse/FLINK-1493 > Project: Flink > Issue Type: New Feature > Components: API / DataStream >Reporter: Márton Balassi >Priority: Minor > Labels: auto-deprioritized-major > > Distributed streaming jobs do not give total, global ordering guarantees for > records only partial ordering is provided by the system: records travelling > on the same exact route of the physical plan are ordered, but they aren't > between routes. > It turns out that although this feature can only be implemented via "merge > sorting" in the input buffers on a timestamp field thus creating substantial > latency is still desired for a number of applications. > Just a heads up for the implementation: the sorting introduces back pressure > in the buffers and might cause deadlocks. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FLINK-1493) Support for streaming jobs preserving global ordering of records
[ https://issues.apache.org/jira/browse/FLINK-1493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flink Jira Bot updated FLINK-1493: -- Labels: stale-major (was: ) > Support for streaming jobs preserving global ordering of records > > > Key: FLINK-1493 > URL: https://issues.apache.org/jira/browse/FLINK-1493 > Project: Flink > Issue Type: New Feature > Components: API / DataStream >Reporter: Márton Balassi >Priority: Major > Labels: stale-major > > Distributed streaming jobs do not give total, global ordering guarantees for > records only partial ordering is provided by the system: records travelling > on the same exact route of the physical plan are ordered, but they aren't > between routes. > It turns out that although this feature can only be implemented via "merge > sorting" in the input buffers on a timestamp field thus creating substantial > latency is still desired for a number of applications. > Just a heads up for the implementation: the sorting introduces back pressure > in the buffers and might cause deadlocks. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FLINK-1493) Support for streaming jobs preserving global ordering of records
[ https://issues.apache.org/jira/browse/FLINK-1493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aljoscha Krettek updated FLINK-1493: Component/s: (was: Streaming) DataStream API > Support for streaming jobs preserving global ordering of records > > > Key: FLINK-1493 > URL: https://issues.apache.org/jira/browse/FLINK-1493 > Project: Flink > Issue Type: New Feature > Components: DataStream API >Reporter: Márton Balassi > > Distributed streaming jobs do not give total, global ordering guarantees for > records only partial ordering is provided by the system: records travelling > on the same exact route of the physical plan are ordered, but they aren't > between routes. > It turns out that although this feature can only be implemented via "merge > sorting" in the input buffers on a timestamp field thus creating substantial > latency is still desired for a number of applications. > Just a heads up for the implementation: the sorting introduces back pressure > in the buffers and might cause deadlocks. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
