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/ > >
