[
https://issues.apache.org/jira/browse/FLINK-11398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-11398:
-----------------------------------
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 a dedicated phase to materialize time indicators for nodes produce updates
> ------------------------------------------------------------------------------
>
> Key: FLINK-11398
> URL: https://issues.apache.org/jira/browse/FLINK-11398
> Project: Flink
> Issue Type: Improvement
> Components: Table SQL / Legacy Planner
> Reporter: Hequn Cheng
> Priority: Major
> Labels: auto-unassigned, stale-major
>
> As discussed
> [here|https://github.com/apache/flink/pull/6787#discussion_r247926320], we
> need a dedicated phase to materialize time indicators for nodes produce
> updates.
> Details:
> Currently, we materialize time indicators in `RelTimeInidicatorConverter`. We
> need to introduce another materialize phase that materializes all time
> attributes on nodes that produce updates. We can not do it inside
> `RelTimeInidicatorConverter`, because only later, after physical optimization
> phase, we know whether it is a non-window outer join which will produce
> updates
> There are a few other things we need to consider.
> - Whether we can unify the two converter phase.
> - Take window with early fire into consideration(not been implemented yet).
> In this case, we don't need to materialize time indicators even it produces
> updates.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
