You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Lineage and StringSet was introduced in Beam 2.58.0 as a feature for IOs. It relies on the new StringSet metrics and Beam metrics API. However we have found different limitations in Beam metrics system in addition to bugs in StringSet itself, mainly scalability ones which is difficult to test in small testing pipelines (e.g. #32649#33054)
We should add a gate to switch on / off this feature until it is stable and do not affect user pipeline functionality
Issue Priority
Priority: 1 (urgent / mostly reserved for critical bugs)
Issue Components
Component: Python SDK
Component: Java SDK
Component: Go SDK
Component: Typescript SDK
Component: IO connector
Component: Beam YAML
Component: Beam examples
Component: Beam playground
Component: Beam katas
Component: Website
Component: Infrastructure
Component: Spark Runner
Component: Flink Runner
Component: Samza Runner
Component: Twister2 Runner
Component: Hazelcast Jet Runner
Component: Google Cloud Dataflow Runner
The text was updated successfully, but these errors were encountered:
What needs to happen?
Lineage and StringSet was introduced in Beam 2.58.0 as a feature for IOs. It relies on the new StringSet metrics and Beam metrics API. However we have found different limitations in Beam metrics system in addition to bugs in StringSet itself, mainly scalability ones which is difficult to test in small testing pipelines (e.g. #32649 #33054)
We should add a gate to switch on / off this feature until it is stable and do not affect user pipeline functionality
Issue Priority
Priority: 1 (urgent / mostly reserved for critical bugs)
Issue Components
The text was updated successfully, but these errors were encountered: