Details
-
Bug
-
Resolution: Fixed
-
Blocker
-
3.0.0, 3.0.1, 3.0.2, 3.0.3, 3.0.4, 3.0.5
-
None
-
None
-
1
Description
Expected behavior:
If the user specifies a duration longer than 30 days, the SDK automatically converts the duration to an absolute timestamp in UNIX epoch seconds.
Actual behavior:
The SDK always uses the number of seconds in the duration, which leads to problems because Couchbase Server interprets an expiry value longer than 30 days as an absolute timestamp in UNIX epoch seconds... this causes the document to expire prematurely.
Attachments
Issue Links
For Gerrit Dashboard: JCBC-1645 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
131215,6 | JCBC-1645 Expiry durations longer than 30 days are interpreted incorrectly | master | couchbase-jvm-clients | Status: MERGED | +2 | +1 |
131951,2 | JCBC-1645 Expiry durations longer than 30 days are interpreted incorrectly | colossus | couchbase-jvm-clients | Status: MERGED | +2 | +1 |
131954,2 | JCBC-1645 Followup: fix KeyValueIntegrationTest.checkExpiryBeyond2038 | colossus | couchbase-jvm-clients | Status: MERGED | +2 | +1 |
132041,2 | JCBC-1645 Followup: fix KeyValueIntegrationTest.checkExpiryBeyond2038 | master | couchbase-jvm-clients | Status: MERGED | +2 | +1 |
132097,2 | JCBC-1645 Followup: Integration test for expiry > 30 days | colossus | couchbase-jvm-clients | Status: MERGED | +2 | +1 |
132324,2 | JCBC-1645 Followup: Integration test for expiry > 30 days | master | couchbase-jvm-clients | Status: MERGED | +2 | +1 |
132602,2 | KAFKAC-214 Upgrade Couchbase Java Client from 3.0.5 to 3.0.6 | master | kafka-connect-couchbase | Status: MERGED | +2 | +1 |
136892,4 | JCBC-1718 Incorrect interpretation of the "expiry". | master | couchbase-jvm-clients | Status: MERGED | +2 | +1 |
137249,2 | JCBC-1718 Incorrect interpretation of the "expiry". | colossus | couchbase-jvm-clients | Status: MERGED | +2 | +1 |
155395,2 | JCBC-1787 Validate expiry instants | master | couchbase-jvm-clients | Status: MERGED | +2 | +1 |