[Bug]: Correctly handle Int64_MAX as a key in ordered list state - Githubissues

apache / beam

Apache Beam is a unified programming model for Batch and Streaming data processing.

https://beam.apache.org/

Apache License 2.0

7.7k stars 4.2k forks source link

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

Open shunping opened 1 month ago

shunping commented 1 month ago

What happened?

This is a follow-up issue from comment https://github.com/apache/beam/pull/30317#discussion_r1638540287.

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
[X] 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 commented 1 month ago

.take-issue