[
https://issues.apache.org/jira/browse/FLINK-6970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-6970:
----------------------------------
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.
> Add support for late data updates to group window aggregates
> ------------------------------------------------------------
>
> Key: FLINK-6970
> URL: https://issues.apache.org/jira/browse/FLINK-6970
> Project: Flink
> Issue Type: New Feature
> Components: Table SQL / API
> Reporter: Fabian Hueske
> Priority: Minor
> Labels: auto-deprioritized-major, stale-minor
>
> Late arriving data is a common issue for group window aggregates. At the
> moment, the Table API simply drops late arriving records. Another approach
> are deferred computation (FLINK-6969) and late data updates.
> This issue proposes to add late data updates for group window aggregates.
> Instead of discarding the state of a window when the result has been
> computed, the state is kept for a certain time interval. If a late record for
> a window is received within this interval, an updated result is emitted (and
> the previous result is retracted).
> This feature will require a new parameter to the {{QueryConfig}} to configure
> the size of the late data interval.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
