Skip to content
New issue

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

[Bug]: Correctly handle Int64_MAX as a key in ordered list state #31593

Open
1 of 16 tasks
shunping opened this issue Jun 13, 2024 · 1 comment
Open
1 of 16 tasks

[Bug]: Correctly handle Int64_MAX as a key in ordered list state #31593

shunping opened this issue Jun 13, 2024 · 1 comment
Assignees

Comments

@shunping
Copy link
Contributor

What happened?

This is a follow-up issue from comment #30317 (comment).

The ordered list implementations or RunnerV2 and direct runner are impacted.

Issue Priority

Priority: 2 (default / most bugs should be filed as P2)

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: Spark Runner
  • Component: Flink Runner
  • Component: Samza Runner
  • Component: Twister2 Runner
  • Component: Hazelcast Jet Runner
  • Component: Google Cloud Dataflow Runner
@shunping
Copy link
Contributor Author

.take-issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant