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.
>
+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,
+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,
+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
+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 (
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
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
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
