feat(bigtable): enable microsecond timestamps in client - #14057
feat(bigtable): enable microsecond timestamps in client#14057kanchi12P wants to merge 5 commits into
Conversation
kanchi12P
commented
Aug 12, 2026
- Enable microsecond timestamp flag in stub settings
- Plumb timestamp origin to Mutation setCell
- Skip emulator in mutation-based integration tests to prevent failures
There was a problem hiding this comment.
Code Review
This pull request introduces microsecond timestamp granularity for Bigtable mutations, including setting the timestamp origin (client auto-generated vs. user-specified) and enabling the microsecond timestamp feature flag in stub settings. Integration tests are updated to skip emulator environments that do not support this granularity, and several protobuf-generated files are regenerated. The review feedback suggests avoiding a potential JDK overflow bug in the year 2262 by directly calculating microseconds since epoch instead of using Instant.until, and recommends adding a @Nonnull annotation to the timestampOrigin parameter for consistency.
fe7343e to
41eff3e
Compare
|
@mutianf Please review |
41eff3e to
49bfa7c
Compare
e609c3b to
94f96f0
Compare
| public Mutation setCell( | ||
| @Nonnull String familyName, @Nonnull ByteString qualifier, @Nonnull ByteString value) { | ||
| long timestamp = System.currentTimeMillis() * 1_000; | ||
| Instant maxInstant = Instant.now(); |
There was a problem hiding this comment.
sorry, why is it called maxInstant and not just instant?
- Enable microsecond timestamp flag in stub settings - Plumb timestamp origin to Mutation setCell - Skip emulator in mutation-based integration tests to prevent failures Change-Id: Ifd8824a5934f17c9d6a5e0e8cf8b0a0a7343ccb1
Change-Id: I42a732ca9a82884ccf97afcb734e317b4384455a
3f50b5d to
7b5fb89
Compare
Change-Id: Iade245d7881798735bfb10598d9d1b4b4db0f4a1
7b5fb89 to
57aa60c
Compare
…estamps Change-Id: I934a296af5a401ba02da7b377b3a2ad913a4fc01
…bePointWriteCallableTest Change-Id: I0a719ae140ab3f455e54e0233b26949738d20743