One possibility is adding type annotations sort of in the style of the Parquet format. So these would run parallel to the types in https://github.com/apache/arrow/blob/master/format/Schema.fbs#L194
On Wed, Feb 21, 2018 at 11:53 AM, Jacques Nadeau <jacq...@apache.org> wrote: > I think we should consider at introducing these "business" types > differently. Same could be said for a US zipcode type, for example. > > On Thu, Feb 15, 2018 at 6:36 PM, Wes McKinney <wesmck...@gmail.com> wrote: > >> hi Uwe, >> >> This seems like a good idea to me given the widespread use of UUIDs, >> and would make use more natural for application developers. >> >> - Wes >> >> On Tue, Feb 13, 2018 at 10:03 AM, Uwe L. Korn <uw...@xhochy.com> wrote: >> > Hello, >> > >> > I just opened https://issues.apache.org/jira/browse/ARROW-2152 to start >> the discussion about adding a UUID type to the Arrow format specification. >> In its essence a UUID is simply a 128bit array but there are often special >> classes used for it, e.g. java.util.UUID in Java and uuid.UUID in Python. >> These provide special functions for them as well as sometimes the knowledge >> that a column is a UUID could be beneficial during computations. Other data >> systems like Postgres or Parquet also have a special UUID type. >> > >> > While there is only a small difference to a 128bit fixed sized binary >> array, I think providing the respective object model accessor is already a >> good benefit. >> > >> > Uwe >>
