Re: Podling Report Reminder - June 2018

2018-06-20 Thread Gian Merlino
Hi Justin, As Julian said, he is active, and has been very helpful as a mentor. (Thanks Julian!!) Thanks for checking up on us. We'll make sure not to miss next month's report; we are aware they are a thing (we did a couple already -- Nishant did one and I did one or two) but it looks like nobody

Re: Update log4j version to >= 2.8

2018-06-20 Thread Gian Merlino
This sounds great to me too. Has anyone raised a PR yet? If not -- Abson, would you mind doing so at https://github.com/druid-io/druid? On Tue, Jun 12, 2018 at 9:02 AM Charles Allen wrote: > This would actually be helpful as more recent log4j json formats have > better and more controllable opti

Re: Podling Report Reminder - June 2018

2018-06-20 Thread P. Taylor Goetz
The pulsar community is aware that for convenience, they can continue to make releases using their pre-Apache process. As well as the caveat that any such releases are not hosted on ASF infrastructure, and are flagged with a prominent notice that such releases are not Apache releases. Many proj

Druid repo migration plan

2018-06-20 Thread Jonathan Wei
Hi all, The SGA for Druid has been sorted out, we can get started on migrating the old Github repo to Apache. Based on the discussion in our previous migration thread ( https://groups.google.com/forum/#!msg/druid-development/q1ip-L8xpBk/GPK1LhC7BQAJ), it seems we favor using our existing Github P

Re: Druid repo migration plan

2018-06-20 Thread Nishant Bangarwa
+1 -- Nishant Bangarwa Hortonworks On 6/20/18, 3:57 PM, "Jonathan Wei" wrote: Hi all, The SGA for Druid has been sorted out, we can get started on migrating the old Github repo to Apache. Based on the discussion in our previous migration thread ( https://groups.

Re: Druid repo migration plan

2018-06-20 Thread Jihoon Son
+1 Sounds good to me. Jihoon On Wed, Jun 20, 2018 at 5:12 PM Nishant Bangarwa wrote: > +1 > > -- > Nishant Bangarwa > > Hortonworks > > On 6/20/18, 3:57 PM, "Jonathan Wei" wrote: > > Hi all, > > The SGA for Druid has been sorted out, we can get started on migrating > the > old Gi

Re: Druid repo migration plan

2018-06-20 Thread Gian Merlino
+1; thanks Jon! On Wed, Jun 20, 2018 at 5:52 PM Jihoon Son wrote: > +1 > > Sounds good to me. > > Jihoon > > On Wed, Jun 20, 2018 at 5:12 PM Nishant Bangarwa < > nbanga...@hortonworks.com> > wrote: > > > +1 > > > > -- > > Nishant Bangarwa > > > > Hortonworks > > > > On 6/20/18, 3:57 PM, "Jonath

Re: Considering 0.12.2 release

2018-06-20 Thread Gian Merlino
+1 I would suggest adding these two as well. https://github.com/druid-io/druid/pull/5878 - Fix inefficient available segment cache population in SQLMetadataSegmentManager. https://github.com/druid-io/druid/pull/5873 - HdfsDataSegmentPusher: Close tmpIndexFile before copying it. On Tue, Jun 12, 2

Re: Considering 0.12.2 release

2018-06-20 Thread Roman Leventov
Why won't release 13.0 instead (as non-Apache)? On Thu, 21 Jun 2018, 08:18 Gian Merlino, wrote: > +1 > > I would suggest adding these two as well. > > https://github.com/druid-io/druid/pull/5878 - Fix inefficient available > segment cache population in SQLMetadataSegmentManager. > https://github

Re: Druid repo migration plan

2018-06-20 Thread Himanshu
+1 ... Major milestone, thanks On Wed, Jun 20, 2018, 9:13 PM Gian Merlino, wrote: > +1; thanks Jon! > > On Wed, Jun 20, 2018 at 5:52 PM Jihoon Son wrote: > > > +1 > > > > Sounds good to me. > > > > Jihoon > > > > On Wed, Jun 20, 2018 at 5:12 PM Nishant Bangarwa < > > nbanga...@hortonworks.com>

Re: Considering 0.12.2 release

2018-06-20 Thread Gian Merlino
I think we're hoping that the next major (0.13) will also be our first Apache release. If it ends up taking too long we might want to rethink that but hopefully it won't (see the recently started thread about the next step, migrating the Github repos). On Wed, Jun 20, 2018 at 10:42 PM Roman Levent