[
https://issues.apache.org/jira/browse/FLINK-9620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-9620:
----------------------------------
Labels: auto-unassigned stale-major (was: auto-unassigned)
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
Major but is unassigned and neither itself nor its Sub-Tasks have been updated
for 30 days. I have gone ahead and added a "stale-major" to the issue". If this
ticket is a Major, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> Add an alternative option to choose when deal with eventtime cep
> ----------------------------------------------------------------
>
> Key: FLINK-9620
> URL: https://issues.apache.org/jira/browse/FLINK-9620
> Project: Flink
> Issue Type: Improvement
> Components: Library / CEP
> Reporter: Aitozi
> Priority: Major
> Labels: auto-unassigned, stale-major
>
> Now when deal with eventtime, it use the elementQueue to buffer event to work
> with the out of order data, I think its ok. But when the key is very
> fragmented, every time the watermark advanced , all key's timer have to been
> evaluted. What about add an alternative option that indicates the stream has
> been ordered updtream, which will simply the logic when deal with cep
> eventtime, the work of ordering a stream by time can be done upstream by
> userself by the window or other way.
> What's your guys idea [~dawidwys] [~kkl0u]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
