Isn't that easily decodable from the UUID data itself? If you allow the version to be specified as metadata, you now have to validate and make sure it's consistent with the version encoded in the contents of the UUID column. And UUID versions are more of a concern for UUID generation than consumption.
-- Felipe On Mon, Apr 29, 2024 at 2:31 PM Micah Kornfield <emkornfi...@gmail.com> wrote: > > Apologies for the late reply, but I think being able to specify the UUID > version as metadata might make sense in some cases? > > On Fri, Apr 19, 2024 at 1:22 PM Rok Mihevc <rok.mih...@gmail.com> wrote: > > > Hi all, > > > > Following initial requests [1][2] and recent tangential ML discussion [3] I > > would like to propose a vote to add language for UUID canonical extension > > type to CanonicalExtensions.rst as in PR [4] and written below. > > A draft C++ and Python implementation PR can be seen here [5]. > > > > [1] https://lists.apache.org/thread/k2zvgoq62dyqmw3mj2t6ozfzhzkjkc4j > > [2] https://github.com/apache/arrow/issues/15058 > > [3] https://lists.apache.org/thread/8d5ldl5cb7mms21rd15lhpfrv4j9no4n > > [4] https://github.com/apache/arrow/pull/41299 <- proposed change > > [5] https://github.com/apache/arrow/pull/37298 > > > > > > The vote will be open for at least 72 hours. > > > > [ ] +1 Accept this proposal > > [ ] +0 > > [ ] -1 Do not accept this proposal because... > > > > > > UUID > > ==== > > > > * Extension name: `arrow.uuid`. > > > > * The storage type of the extension is ``FixedSizeBinary`` with a length of > > 16 bytes. > > > > .. note:: > > A specific UUID version is not required or guaranteed. This extension > > represents > > UUIDs as FixedSizeBinary(16) and does not interpret the bytes in any > > way. > > > > > > > > Rok > >
