Re: Naming the new ValueVector Initiative

2016-01-21 Thread Wes McKinney
Parth just split out the non-Drill-related bits here, we've been talking on the side about it https://github.com/parthchandra/arrow-cpp/commit/7565e570f7eabebcbba3a7fb3ccb6a0e605e6ef1 I've been assembling a C++ library from scratch from the specification (

Re: Naming the new ValueVector Initiative

2016-01-21 Thread Wes McKinney
>> thanks to everyone! >>> Jacques >>> >>> >>> -- >>> Jacques Nadeau >>> CTO and Co-Founder, Dremio >>> >>> On Tue, Jan 12, 2016 at 11:03 PM, Julien Le Dem <jul...@dremio.com> >>> wrote: >>> >

Re: Naming the new ValueVector Initiative

2016-01-20 Thread Wes McKinney
>> thanks to everyone! >> Jacques >> >> >> -- >> Jacques Nadeau >> CTO and Co-Founder, Dremio >> >> On Tue, Jan 12, 2016 at 11:03 PM, Julien Le Dem <jul...@dremio.com> >> wrote: >> >>> +1 on a repo for the spec. &g

Re: Naming the new ValueVector Initiative

2016-01-12 Thread Wes McKinney
On Tue, Jan 12, 2016 at 6:21 PM, Parth Chandra <par...@apache.org> wrote: > > > On Tue, Jan 12, 2016 at 9:57 AM, Wes McKinney <w...@cloudera.com> wrote: >> >> >> > >> > As far as the existing work is concerned, I'm not sure everyone is aware

Re: Naming the new ValueVector Initiative

2016-01-12 Thread Wes McKinney
ished, we can break >> any independent progress you've made into a set of patches to add to the >> existing repo through the normal Apache commit process. >> >> >> >> >> >> -- >> Jacques Nadeau >> CTO and Co-Founder, Dremio >> &

Re: Naming the new ValueVector Initiative

2015-12-30 Thread Wes McKinney
thwhile discussion, parallel vs independent >> >> releases, but I don't understand why it relates to one repo or not. >> >> Couldn't >> >> the release tag names just include the language (cpp, java python)? What >> >> other parts of version control are r

Re: Naming the new ValueVector Initiative

2015-12-15 Thread Wes McKinney
testing. I can convert the Google doc spec floating around to Markdown and perhaps we can discuss specific details in GitHub issues? I'll use a separate repo for the format docs. best, Wes On Mon, Dec 14, 2015 at 9:43 AM, Wes McKinney <w...@cloudera.com> wrote: > hi folks, > > I

Re: Naming the new ValueVector Initiative

2015-12-14 Thread Wes McKinney
ache Herringbone (9) > Apache Joist (8) > Apache Colbuf (8) > > I'll up a PODLINGNAMESEARCH-* shortly for Arrow. > > --- > > > > > > > -- > Jacques Nadeau > CTO and Co-Founder, Dremio > > On Thu, Dec 3, 2015 at 1:23 AM, Marcel Kornacker <m

Re: Naming the new ValueVector Initiative

2015-12-02 Thread Wes McKinney
gt; If someone would like to vet other names, use the links on >>> https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-90, and fill out >>> column C in the spreadsheet. >>> >>> Julian >>> >>> [1] https://github.com/stephenh/joist >>&

Re: Naming the new ValueVector Initiative

2015-11-30 Thread Wes McKinney
We do the naming in the following steps >>>>>>> - 1: Collect a set of names to be considered >>>>>>> - 2: Run a vote for 2 days where each member ranks their top 10 >>>>>>> options >>>>>>> 1..10 >>>

Re: [DISCUSS] Proposal to turn ValueVectors into separate reusable library & project

2015-10-26 Thread Wes McKinney
hi all, I am excited about this initiative and I personally am looking forward to seeing a standard in-memory columnar representation made available to data science languages like Python, R, and Julia, and it's also the ideal place to build out a reference vectorized Parquet implementation for