I think that there are a lot of good discussions and initial efforts for larger system changes that would be easier to move forward with on a "dev" branch. On top of the items listed so far, I think that we need to pick back up your proposal on workload management and put that work here as well.
A bit of a more minor point, as we are the only current consumers of the Java arrow code, I think it may be worth considering moving back to the old names and packages for the Drill classes that we are trying to move to Arrow. The code should still be moved out of the Drill repo, but this would make applying patches to both of these branches a little easier. The proper rename could happen very easily at Drill 2.0. As a more general note on your follow up message, I would really like to see more effort being put towards finalizing the union type feature. We have been getting consistent requests for handling of JSON files (as well as other formats) with changing types throughout the life of the project and we are so close to being the best solution for this problem, that for myself at least, it has been very frustrating that we haven't been able to deliver a this as a clear cut feature. I will open a separate thread on this discussion topic, I just wanted to include my extra push for inclusion of this work on the branch. Jason Altekruse Software Engineer at Dremio Apache Drill Committer On Thu, Mar 24, 2016 at 2:36 PM, Jacques Nadeau <jacq...@dremio.com> wrote: > I also propose that we should turn on the union type as part of this as > well. I've opened DRILL-4538 to track that. > > -- > Jacques Nadeau > CTO and Co-Founder, Dremio > > On Thu, Mar 24, 2016 at 8:55 AM, Jacques Nadeau <jacq...@dremio.com> > wrote: > > > There are some changes that either have reviews pending or are in > progress > > that would require breaking changes to Drill core. > > > > Examples Include: > > DRILL-4455 (arrow integration) > > DRILL-4417 (jdbc/odbc/rpc changes) > > DRILL-4534 (improve null performance) > > > > I've created a new 2.0.0 release version in JIRA and moved these tasks to > > that umbrella. > > > > I'd like to propose a new v2 release branch where we can start > > incorporating these changes without disrupting v1 stability and > > compatibility. > > > > > > -- > > Jacques Nadeau > > CTO and Co-Founder, Dremio > > >
