DRILL-3874: Flattening large JSON objects uses too much direct memory. (This one is nearly ready to merge)
On Thu, Oct 1, 2015 at 6:35 PM, Jacques Nadeau <jacq...@dremio.com> wrote: > We went through the list. I propose that we include only the following > issues in 1.2 and move the rest to 1.3 > > DRILL-1065 Provide a reset command to reset an option to its default value > DRILL-3884 Hive native scan has lower parallelization leading to > performance degradation > DRILL-2879 Add Remaining portion of "Drill extended json's support $oid" > DRILL-3887 Parquet metadata cache not being used (regression caused by > DRILL-3788) > > What do other people think? > > > -- > Jacques Nadeau > CTO and Co-Founder, Dremio > > On Thu, Oct 1, 2015 at 5:46 PM, Jacques Nadeau <jacq...@dremio.com> wrote: > > > I'm on: > > > > https://plus.google.com/hangouts/_/event/ci4rdiju8bv04a64efj5fedd0lc > > > > -- > > Jacques Nadeau > > CTO and Co-Founder, Dremio > > > > On Thu, Oct 1, 2015 at 5:45 PM, Jacques Nadeau <jacq...@dremio.com> > wrote: > > > >> How about now? > >> > >> > >> > >> -- > >> Jacques Nadeau > >> CTO and Co-Founder, Dremio > >> > >> On Thu, Oct 1, 2015 at 5:38 PM, Parth Chandra <par...@apache.org> > wrote: > >> > >>> What time do you want the hangout? I'm in favour of bumping if we > cannot > >>> get decided by tomorrow. > >>> > >>> > >>> > >>> On Thu, Oct 1, 2015 at 2:05 PM, Jacques Nadeau <jacq...@dremio.com> > >>> wrote: > >>> > >>> > On Thu, Oct 1, 2015 at 11:17 AM, Abdel Hakim Deneche < > >>> > adene...@maprtech.com> > >>> > wrote: > >>> > > >>> > > I can manage the release. > >>> > > > >>> > > >>> > Great! I use a manual variation of these steps [1] typically. Julian > >>> Hyde > >>> > made a much nicer set of steps (for Incubator) here: [2] if you want > >>> to use > >>> > those. > >>> > > >>> > On Thu, Oct 1, 2015 at 2:32 PM, Parth Chandra <par...@apache.org> > >>> wrote: > >>> > > >>> > > +1 on the release. I'm all for starting the process ASAP. > >>> > > > >>> > > >>> > I've moved all the non-critical, non-active jiras out of 1.2. > However, > >>> that > >>> > still leaves 63 issues open. Do you want to do a quick hangout to try > >>> to > >>> > figure what we really want to include versus bump? > >>> > > >>> > J > >>> > > >>> > [1] > >>> > > >>> > > >>> > https://gist.github.com/jacques-n/be0d2f584171d832aedb#file-release_commands > >>> > [2] > >>> > > >>> > > >>> > https://calcite.incubator.apache.org/docs/howto.html#making-a-release-for-calcite-committers > >>> > > >>> > > >>> > > >>> > > > >>> > > > >>> > > > >>> > > On Thu, Oct 1, 2015 at 8:17 AM, Abdel Hakim Deneche < > >>> > adene...@maprtech.com > >>> > > > > >>> > > wrote: > >>> > > > >>> > > > I can manage the release. > >>> > > > > >>> > > > On Wed, Sep 30, 2015 at 6:10 PM, Aman Sinha <asi...@maprtech.com > > > >>> > wrote: > >>> > > > > >>> > > > > +1 for starting the process of finalizing the 1.2 release and > >>> 'bounce > >>> > > > > everything not critical (and not in-progress or reviewable) off > >>> of > >>> > this > >>> > > > > release'. > >>> > > > > > >>> > > > > Aman > >>> > > > > > >>> > > > > On Wed, Sep 30, 2015 at 5:36 PM, Jacques Nadeau < > >>> jacq...@dremio.com> > >>> > > > > wrote: > >>> > > > > > >>> > > > > > Hey All, > >>> > > > > > > >>> > > > > > It seems like we should finalize on the 1.2 release pretty > >>> soon. I > >>> > > > > > currently see something like 174 bugs currently open. Of > >>> those, ~20 > >>> > > are > >>> > > > > > reviewable and ~20 are in progress. I'm inclined to bounce > >>> > everything > >>> > > > not > >>> > > > > > critical (and not in-progress or reviewable) off of this > >>> release. > >>> > Any > >>> > > > > > thoughts on when everyone would like to do a release? Also, > >>> anyone > >>> > > want > >>> > > > > to > >>> > > > > > be release manager? > >>> > > > > > > >>> > > > > > Jacques > >>> > > > > > > >>> > > > > > -- > >>> > > > > > Jacques Nadeau > >>> > > > > > CTO and Co-Founder, Dremio > >>> > > > > > > >>> > > > > > On Tue, Aug 18, 2015 at 7:58 PM, Parth Chandra < > >>> par...@apache.org> > >>> > > > > wrote: > >>> > > > > > > >>> > > > > > > A couple of reasons - > >>> > > > > > > a) We definitely need more QA time for the features that > >>> are > >>> > > ready. > >>> > > > > > > b) Some features, in particular, Parquet metadata caching > >>> > > (Steven) > >>> > > > > and > >>> > > > > > > Faster Hive reads (Jason) are close enough to completion > >>> that we > >>> > > > really > >>> > > > > > > should include them. Again the team could use the extra > time > >>> to > >>> > QA > >>> > > > > these. > >>> > > > > > > > >>> > > > > > > > >>> > > > > > > On Tue, Aug 18, 2015 at 4:32 PM, Chris Westin < > >>> > > > chriswesti...@gmail.com > >>> > > > > > > >>> > > > > > > wrote: > >>> > > > > > > > >>> > > > > > > > Unfortunately, we've had to modify our plans, and are now > >>> > > thinking > >>> > > > of > >>> > > > > > > > aiming for a vote on September 10th. > >>> > > > > > > > > >>> > > > > > > > On Thu, Aug 13, 2015 at 1:29 PM, Chris Westin < > >>> > > > > chriswesti...@gmail.com > >>> > > > > > > > >>> > > > > > > > wrote: > >>> > > > > > > > > >>> > > > > > > > > We were thinking of targetting for a vote on August > 26th. > >>> > > > > > > > > > >>> > > > > > > > > On Thu, Aug 13, 2015 at 1:19 PM, Jacques Nadeau < > >>> > > > > jacq...@dremio.com> > >>> > > > > > > > > wrote: > >>> > > > > > > > > > >>> > > > > > > > >> Following up since we haven't discussed the 1.2 > release > >>> in a > >>> > > > > while. > >>> > > > > > > How > >>> > > > > > > > >> are people feeling about trying to get a candidate out > >>> in > >>> > the > >>> > > > next > >>> > > > > > > week > >>> > > > > > > > or > >>> > > > > > > > >> two? > >>> > > > > > > > >> > >>> > > > > > > > >> thanks, > >>> > > > > > > > >> Jacques > >>> > > > > > > > >> > >>> > > > > > > > >> -- > >>> > > > > > > > >> Jacques Nadeau > >>> > > > > > > > >> CTO and Co-Founder, Dremio > >>> > > > > > > > >> > >>> > > > > > > > >> > >>> > > > > > > > >> > >>> > > > > > > > >> > ---------- Forwarded message ---------- > >>> > > > > > > > >> > From: Parth Chandra <pchan...@maprtech.com> > >>> > > > > > > > >> > Date: Thu, Jul 9, 2015 at 11:29 AM > >>> > > > > > > > >> > Subject: Re: Timing for 1.2 release, ideas around > >>> things > >>> > to > >>> > > > > > include > >>> > > > > > > > >> > To: dev@drill.apache.org > >>> > > > > > > > >> > > >>> > > > > > > > >> > > >>> > > > > > > > >> > I just moved DRILL-3201 to 1.2. It's one of the > >>> candidates > >>> > > for > >>> > > > > > > > inclusion > >>> > > > > > > > >> > into 1.2 > >>> > > > > > > > >> > > >>> > > > > > > > >> > On Thu, Jul 9, 2015 at 7:04 AM, < > >>> > michael.engl...@nomura.com > >>> > > > > >>> > > > > > wrote: > >>> > > > > > > > >> > > >>> > > > > > > > >> > > I'm not sure what the appetite is for pushing this > >>> into > >>> > > 1.2 > >>> > > > vs > >>> > > > > > the > >>> > > > > > > > >> > planned > >>> > > > > > > > >> > > 1.3, but Drill UI Authentication would be really > >>> great > >>> > for > >>> > > > > > > > >> > companies/users > >>> > > > > > > > >> > > that run multi-tenant Hadoop clusters with Drill. > >>> At the > >>> > > > > moment > >>> > > > > > > any > >>> > > > > > > > >> user > >>> > > > > > > > >> > > can change storage plugins and cancel running > >>> queries, > >>> > > even > >>> > > > if > >>> > > > > > > they > >>> > > > > > > > >> did > >>> > > > > > > > >> > not > >>> > > > > > > > >> > > submit them. This is a bit of a blocker for Drill > on > >>> > > > > > multi-tenant > >>> > > > > > > > >> > > production clusters for now. > >>> > > > > > > > >> > > > >>> > > > > > > > >> > > JIRA link: > >>> > > > > > > > >> > > https://issues.apache.org/jira/browse/DRILL-3201 > >>> > > > > > > > >> > > > >>> > > > > > > > >> > > > >>> > > > > > > > >> > > > >>> > > > > > > > >> > > -----Original Message----- > >>> > > > > > > > >> > > From: Jacques Nadeau [mailto:jacq...@apache.org] > >>> > > > > > > > >> > > Sent: 08 July 2015 17:19 > >>> > > > > > > > >> > > To: dev@drill.apache.org > >>> > > > > > > > >> > > Subject: Timing for 1.2 release, ideas around > >>> things to > >>> > > > > include > >>> > > > > > > > >> > > > >>> > > > > > > > >> > > Hey Guys, > >>> > > > > > > > >> > > > >>> > > > > > > > >> > > What do you think about planning the 1.2 feature > >>> cutoff > >>> > > > around > >>> > > > > > Aug > >>> > > > > > > > >> 21st > >>> > > > > > > > >> > > and target a release vote a week or so after that? > >>> > > > > > > > >> > > > >>> > > > > > > > >> > > What are different features people want to get > into > >>> 1.2? > >>> > > > > > > > >> > > > >>> > > > > > > > >> > > Here are couple of things that I'd like to help > >>> > facilitate > >>> > > > > > > > >> contribution > >>> > > > > > > > >> > > and/or inclusion: > >>> > > > > > > > >> > > > >>> > > > > > > > >> > > - Mongo improvements (including extended type > fixes > >>> > 2879 , > >>> > > > > test > >>> > > > > > > > cases > >>> > > > > > > > >> > 1666, > >>> > > > > > > > >> > > etc) > >>> > > > > > > > >> > > - httpd log parser format plugin (3423) > >>> > > > > > > > >> > > - rpc enhancements (local 2941 and off-thread > 3242) > >>> > > > > > > > >> > > - First merge of Magnus' JDBC connector (3180) > >>> > > > > > > > >> > > - New allocator (1942) > >>> > > > > > > > >> > > > >>> > > > > > > > >> > > Other key goals? What do people think about the > >>> > proposed > >>> > > > > > timing? > >>> > > > > > > > >> > > > >>> > > > > > > > >> > > > >>> > > > > > > > >> > > This e-mail (including any attachments) is private > >>> and > >>> > > > > > > confidential, > >>> > > > > > > > >> may > >>> > > > > > > > >> > > contain proprietary or privileged information and > is > >>> > > > intended > >>> > > > > > for > >>> > > > > > > > the > >>> > > > > > > > >> > named > >>> > > > > > > > >> > > recipient(s) only. Unintended recipients are > >>> strictly > >>> > > > > prohibited > >>> > > > > > > > from > >>> > > > > > > > >> > > taking action on the basis of information in this > >>> e-mail > >>> > > and > >>> > > > > > must > >>> > > > > > > > >> contact > >>> > > > > > > > >> > > the sender immediately, delete this e-mail (and > all > >>> > > > > attachments) > >>> > > > > > > and > >>> > > > > > > > >> > > destroy any hard copies. Nomura will not accept > >>> > > > responsibility > >>> > > > > > or > >>> > > > > > > > >> > liability > >>> > > > > > > > >> > > for the accuracy or completeness of, or the > >>> presence of > >>> > > any > >>> > > > > > virus > >>> > > > > > > or > >>> > > > > > > > >> > > disabling code in, this e-mail. If verification is > >>> > sought > >>> > > > > please > >>> > > > > > > > >> request > >>> > > > > > > > >> > a > >>> > > > > > > > >> > > hard copy. Any reference to the terms of executed > >>> > > > transactions > >>> > > > > > > > should > >>> > > > > > > > >> be > >>> > > > > > > > >> > > treated as preliminary only and subject to formal > >>> > written > >>> > > > > > > > >> confirmation by > >>> > > > > > > > >> > > Nomura. Nomura reserves the right to retain, > >>> monitor and > >>> > > > > > intercept > >>> > > > > > > > >> e-mail > >>> > > > > > > > >> > > communications through its networks (subject to > and > >>> in > >>> > > > > > accordance > >>> > > > > > > > with > >>> > > > > > > > >> > > applicable laws). No confidentiality or privilege > is > >>> > > waived > >>> > > > or > >>> > > > > > > lost > >>> > > > > > > > by > >>> > > > > > > > >> > > Nomura by any mistransmission of this e-mail. Any > >>> > > reference > >>> > > > to > >>> > > > > > > > >> "Nomura" > >>> > > > > > > > >> > is > >>> > > > > > > > >> > > a reference to any entity in the Nomura Holdings, > >>> Inc. > >>> > > > group. > >>> > > > > > > Please > >>> > > > > > > > >> read > >>> > > > > > > > >> > > our Electronic Communications Legal Notice which > >>> forms > >>> > > part > >>> > > > of > >>> > > > > > > this > >>> > > > > > > > >> > e-mail: > >>> > > > > > > > >> > > http://www.Nomura.com/email_disclaimer.htm > >>> > > > > > > > >> > > > >>> > > > > > > > >> > > > >>> > > > > > > > >> > > >>> > > > > > > > >> > > >>> > > > > > > > >> > >>> > > > > > > > > > >>> > > > > > > > > > >>> > > > > > > > > >>> > > > > > > > >>> > > > > > > >>> > > > > > >>> > > > > >>> > > > > >>> > > > > >>> > > > -- > >>> > > > > >>> > > > Abdelhakim Deneche > >>> > > > > >>> > > > Software Engineer > >>> > > > > >>> > > > <http://www.mapr.com/> > >>> > > > > >>> > > > > >>> > > > Now Available - Free Hadoop On-Demand Training > >>> > > > < > >>> > > > > >>> > > > >>> > > >>> > http://www.mapr.com/training?utm_source=Email&utm_medium=Signature&utm_campaign=Free%20available > >>> > > > > > >>> > > > > >>> > > > >>> > > >>> > >> > >> > > >
