[
https://issues.apache.org/jira/browse/BEAM-3588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Kedin updated BEAM-3588:
------------------------------
Description:
GBK (and consequently Beam SQL aggregations) rejects
GlobalWindows+DefaultTrigger combination.
* are there more of known unsupported window/trigger combinations?
* should Repeatedly.forever(AfterWatermark.pastEndOfWindow()) be allowed where
DefaultTrigger isn't? At what level should this stop?
* can some version of this problem be solved analytically in general case?
* should there be a separate validation component on a higher level above GBK?
was:
GBK (and consequently Beam SQL aggregations) rejects
GlobalWindows+DefaultTrigger combination.
* are there more of known unsupported window/trigger combinations?
* can some version of this problem be solved analytically in general case?
* should there be a separate validation component on a higher level above GBK?
> Reject invalid windowing configurations
> ---------------------------------------
>
> Key: BEAM-3588
> URL: https://issues.apache.org/jira/browse/BEAM-3588
> Project: Beam
> Issue Type: Improvement
> Components: beam-model
> Reporter: Anton Kedin
> Priority: Major
>
> GBK (and consequently Beam SQL aggregations) rejects
> GlobalWindows+DefaultTrigger combination.
> * are there more of known unsupported window/trigger combinations?
> * should Repeatedly.forever(AfterWatermark.pastEndOfWindow()) be allowed
> where DefaultTrigger isn't? At what level should this stop?
> * can some version of this problem be solved analytically in general case?
> * should there be a separate validation component on a higher level above GBK?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
