Python and Java SDKs differ on name of AfterCount
- Dominant language
- Java
- Stars
- 8.7k
- Forks
- 4.7k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 205
Description
* https://cloud.google.com/dataflow/model/triggers#window-accumulation-modes refers to an AfterCount trigger
* There is no AfterCount trigger in java SDK
* There is an AfterCount trigger in python SDK
My wild guess hypothesis is that AfterCount got renamed between Dataflow and Beam, but that the python beam SDK did not also execute the same rename?
Imported from Jira [BEAM-2024](https://issues.apache.org/jira/browse/BEAM-2024). Original Jira may contain additional context.
Reported by: wtanaka.
Contributor guide
Research direction
Start by comparing the Java and Python SDK trigger APIs, then check the Dataflow window-accumulation documentation at the linked URL and the imported Jira issue BEAM-2024 for context. The discrepancy is resolved when the SDK naming and referenced documentation agree, with the intended AfterCount behavior clearly established.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, python
- Domain
- data-engineering, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100