[KUDU-3247] UUID column type

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Labels: roadmap-candidate
• Assignee: Abhishek Chennaka
• Reporter: Grant Henke
• Created: 18/Feb/21 16:46
• Updated: 16/Mar/21 16:44

Description

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

Issue Links

• is related to: KUDU-1879 Support table without a primary key