Well, that is only true if you dont have a BigInteger to hold it :) see: https://java-ipv6.googlecode.com/svn/artifacts/0.14/doc/apidocs/com/googlecode/ipv6/IPv6Address.html
Regards, -Stefan On Fri, Jul 24, 2015 at 2:39 PM, Jim Scott <[email protected]> wrote: > an IPv6 address is actually two longs. Depending on the type of analysis > you are doing you may prefer to store them that way. > > e.g. the range on the left side is a home / location and the range on the > right side are sub values (devices within the home). > > Depending on your use case you may want to store them separately. > > Other than that tidbit, I cannot speak to Drill's capability to leverage > said data. > > On Fri, Jul 24, 2015 at 4:20 AM, Stefán Baxter <[email protected]> > wrote: > > > Hi, > > > > Has anyone here opinion/ideas on how ipv6 addresses might be stored > > efficiently in Parquet via Drill. > > > > The Java BigInteger class handles the 128 variant but the BigIntHolder in > > Drill relies on a Long. Storing it in two longs is not optimal and it > would > > surprise me if the variable binary field can do range queries. > > > > all input is welcome :). > > > > This minuscule UDF project (https://github.com/acmeguy/asdrill) now also > > includes a IPv4 conversion (One may exist already) . > > > > Regards, > > -Stefan > > > > > > -- > *Jim Scott* > Director, Enterprise Strategy & Architecture > +1 (347) 746-9281 > > <http://www.mapr.com/> > [image: MapR Technologies] <http://www.mapr.com> > > Now Available - Free Hadoop On-Demand Training > < > http://www.mapr.com/training?utm_source=Email&utm_medium=Signature&utm_campaign=Free%20available > > >
