Reject invalid windowing configurations
- Dominant language
- Java
- Stars
- 8.7k
- Forks
- 4.7k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 205
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?
Imported from Jira [BEAM-3588](https://issues.apache.org/jira/browse/BEAM-3588). Original Jira may contain additional context.
Reported by: kedin.
Contributor guide
Research direction
Start by reading the GBK behavior used by Beam SQL aggregations, focusing on GlobalWindows, DefaultTrigger, Repeatedly.forever, and AfterWatermark.pastEndOfWindow. The issue names no files or tests; first establish which window/trigger combinations are unsupported and where validation belongs, then define completion as consistently rejecting invalid configurations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, sql
- Domain
- data-engineering, stream-processing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100