We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
There are a couple of V2 even V3 coders:
TimerDataCoderV2 MetadataCoderV2 TableDestinationCoderV2 TableDestinationCoderV3
created due to streaming update compatibility concerns. As a tech debt, we should deduplicate them for Beam 3.
Unfortunately we may preserve "V2/V3" suffix in class naming if it is possible to preserve upgrade compatibility, while deduping the (V1)/V2 classes
Priority: 2 (default / most normal work should be filed as P2)
The text was updated successfully, but these errors were encountered:
No branches or pull requests
What needs to happen?
There are a couple of V2 even V3 coders:
created due to streaming update compatibility concerns. As a tech debt, we should deduplicate them for Beam 3.
Unfortunately we may preserve "V2/V3" suffix in class naming if it is possible to preserve upgrade compatibility, while deduping the (V1)/V2 classes
Issue Priority
Priority: 2 (default / most normal work should be filed as P2)
Issue Components
The text was updated successfully, but these errors were encountered: