[
https://issues.apache.org/jira/browse/KUDU-3247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Henke updated KUDU-3247:
------------------------------
Labels: roadmap-candidate (was: )
> UUID column type
> ----------------
>
> Key: KUDU-3247
> URL: https://issues.apache.org/jira/browse/KUDU-3247
> Project: Kudu
> Issue Type: Improvement
> Reporter: Grant Henke
> Priority: Major
> Labels: roadmap-candidate
>
> It could be useful to have a UUID column type in Kudu given often when users
> can't find a natural key, they look to a UUID as an alternate option. The
> problem with this is that the UUID value is often stored in a STRING or
> BINARY column resulting a random ordered write workload which puts a lot of
> strain on Kudu compaction for high volumes.
> If Kudu has a native UUID type it can leverage the underlying structure of
> the UUID to benefit from the mostly ordered properties (version 1 and the
> proposed version 6 UUIDs have a date-time component).
> The implementation could be a logical type built on top of BYTES or INT128.
> The client should have methods to write the UUID type using encoded UUID
> strings or UUID objects.
> Here are some references/examples of a UUID type:
> * https://docs.yugabyte.com/latest/api/ycql/type_uuid/
> * https://cloud.google.com/spanner/docs/schema-design#uuid_primary_key
> * https://www.percona.com/blog/2014/12/19/store-uuid-optimized-way/
> * http://gh.peabody.io/uuidv6/
> * https://github.com/f4b6a3/uuid-creator#version-6-time-ordered-proposed
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
