Bound Instant values used as timestamps at TIMESTAMP_MIN_VALUE and TIMESTAMP_MAX_VALUE
Open
bug
core
java
P3
- Dominant language
- Java
- Stars
- 8.7k
- Forks
- 4.7k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 196
Description
Today the Java SDK allows arbitrary Instant values. If large magnitude Instant values reach a runner with greater precision but the same modulus for its representation, overflow will occur.
Imported from Jira [BEAM-29](https://issues.apache.org/jira/browse/BEAM-29). Original Jira may contain additional context.
Reported by: kenn.
Contributor guide
Research direction
No files or tests are named. Start by locating the Java SDK code that accepts Instant values as timestamps and any existing TIMESTAMP_MIN_VALUE and TIMESTAMP_MAX_VALUE definitions. Reproduce the large-magnitude case described in the issue, then verify coverage for values at both limits and values outside them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- data-engineering
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100