Use microsecond-precision clock to compute time-based UUIDs if available

Description

Currently UUIDs class uses System.currentTimeMillis() to compute time-based UUIDs.

It would be nice if it could use a Clock implementation just like AbstractTimestampGenerator, thus leveraging microsecond-precision timestamps if JNR is available.

Environment

None

Pull Requests

None

Activity

Show:
Alex Dutra
January 5, 2021, 10:01 AM

Also, we need to ensure that GraalVM substitutions aren’t broken because of the introduced changes.

Alex Dutra
January 5, 2021, 10:00 AM

Unfortunately we would have to turn the current Uuids class into a component that would be injected with a Clock instance when instantiated. This won't be possible within the scope of 4.10.0 release, but I will keep thinking about it.

Alex Dutra
November 23, 2020, 10:06 AM

Re-opening as this could be an interesting feature after

Alex Dutra
June 21, 2020, 5:51 PM

This ticket has been closed on 2020-06-22 due to prolonged inactivity, as part of an automatic housekeeping procedure.

If you think that this was inappropriate, feel free to re-open the ticket. If possible, please provide any context that could explain why the issue described in this ticket is still relevant.

Also, please note that enhancements and feature requests cannot be accepted anymore for legacy driver versions (OSS 1.x, 2.x, 3.x and DSE 1.x).

Thank you for your understanding.

Alex Dutra
March 21, 2016, 7:01 PM

Some other places might also benefit from JNR, e.g. the mapper metrics introduced by (if it gets fixed).
Although it probably means to raise Clock class visibility to public.

Assignee

Alex Dutra

Reporter

Alex Dutra

Labels

None

PM Priority

None

Affects versions

Fix versions

Pull Request

None

Doc Impact

None

Size

None

External issue ID

None

External issue ID

None

Priority

Minor