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 ( https://github.com/arrow-data/arrow-cpp/tree/master/src/arrow) -- once we have the Apache repo, I can propose this code as a patch, and we can proceed with C++ API design discussions and merging in the non-Drill C++ functionality (need to write unit tests). My main priorities are a) being able to easily wrap the column containers in Python C extensions and b) being a suitable container for data going in and out of Parquet format. cheers, Wes On Thu, Jan 21, 2016 at 3:02 PM, Jacques Nadeau <jacq...@dremio.com> wrote: > We can do it either way. The main charter is we will work to extract the > code. My suggestion is to avoid a bulk copy and extract what makes sense. > In the Drill community, we've already refactored large chunks of code to > make this portion independent. We probably need to do one more pass to get > all the way there (a few annoying dangling chads remain). > > The primary pieces are in these places: > > Java: > https://github.com/apache/drill/tree/master/exec/vector > > C++ (depending on where Wes/Parth/others land) > https://github.com/apache/drill/tree/master/contrib/native/client > > > > -- > Jacques Nadeau > CTO and Co-Founder, Dremio > > On Thu, Jan 21, 2016 at 2:00 PM, Julian Hyde <jh...@apache.org> wrote: > >> To expand on what “straight to TLP” means (correct me if I’m wrong, >> Jacques). >> >> From an IP standpoint, the new project is a clone of Drill. It starts off >> with Drill’s code base. We then, as the sculptor said [1], chip away >> everything that doesn’t look like Arrow. >> >> Julian >> >> [1] http://quoteinvestigator.com/2014/06/22/chip-away/ >> >>
