Timestamp precision and byte representation should be consistent across SDKs
- Dominant language
- Java
- Stars
- 8.7k
- Forks
- 4.7k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 196
Description
Runners cannot have a timestamp precision that is lesser than what a SDK uses. Also with Fn API a runner should be able to support multiple SDKs that maybe written in different languages. It is important that we standardize the precision of timestamp to ensure that runners are compatible across all the SDKs.
NOTE: Timestamps are shifted such that lexicographic ordering of the bytes corresponds to chronological order. This also needs to be consistent across SDKs.
Imported from Jira [BEAM-1524](https://issues.apache.org/jira/browse/BEAM-1524). Original Jira may contain additional context.
Reported by: vikasrk.
Contributor guide
Research direction
Start with the imported Jira issue BEAM-1524 for additional context, then trace timestamp handling at the Fn API boundary across the SDKs and runners. Done means timestamp precision and shifted-byte representation are standardized so runners can interoperate with multiple SDK languages.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, java, python
- Domain
- api, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100