Re: IPv6 in Drill/Parquet

2015-07-24 Thread Jim Scott
let me clarify... If you were grouping by household, you may want to group on the left side. If it is stored in a single valued field, then you would have to manipulate the value in some way to get the portion you want to group by. Thusly, storing it in two parts would be optimal for the use

Re: IPv6 in Drill/Parquet

2015-07-24 Thread Stefán Baxter
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 jsc...@maprtech.com wrote: an IPv6 address is actually two

Re: IPv6 in Drill/Parquet

2015-07-24 Thread Jim Scott
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

Re: IPv6 in Drill/Parquet

2015-07-24 Thread Stefán Baxter
thank you! On Fri, Jul 24, 2015 at 3:23 PM, Jim Scott jsc...@maprtech.com wrote: let me clarify... If you were grouping by household, you may want to group on the left side. If it is stored in a single valued field, then you would have to manipulate the value in some way to get the