;
> > On 2019/12/20 19:49:37, Gian Merlino wrote:
> > > Hey Druids,
> > >
> > > It is official: Druid has graduated to a top level project!
> > >
> > > Now, we need to conduct various post-graduation tasks. The first is to
> > > raise an
level project!
> >
> > Now, we need to conduct various post-graduation tasks. The first is to
> > raise an infra ticket to migrate the appropriate resources. I started it
> > off here: https://issues.apache.org/jira/browse/INFRA-19609. Please,
> take a
> > look to se
Huzzah!
Thank you for all the hard work Gian.
On 2019/12/20 19:49:37, Gian Merlino wrote:
> Hey Druids,
>
> It is official: Druid has graduated to a top level project!
>
> Now, we need to conduct various post-graduation tasks. The first is to
> raise an infra
Hey Druids,
It is official: Druid has graduated to a top level project!
Now, we need to conduct various post-graduation tasks. The first is to
raise an infra ticket to migrate the appropriate resources. I started it
off here: https://issues.apache.org/jira/browse/INFRA-19609. Please, take a
look
By the way, a link to the vote thread:
https://lists.apache.org/thread.html/2385d5545fa5bd13baf45bd7258fafa7694334d9d14267489d21d99b%40%3Cdev.druid.apache.org%3E
On Sat, Dec 7, 2019 at 1:48 PM Gian Merlino wrote:
> This vote passed with 8 PPMC +1s:
>
> David Lim
> Fangjin Yang
> Gian Merlino
>
This vote passed with 8 PPMC +1s:
David Lim
Fangjin Yang
Gian Merlino
Jihoon Son
Jonathan Wei
Julian Hyde
Kurt Young
Slim Bouguerra
Xavier Léauté
In addition, the following nonbinding +1s were received:
Benedict Jin
Clint Wylie
Fokko Driesprong
Furkan Kamaci
I will refer this to the Incubator
t; > > > > > şunu
> > > > > > > > > yazdı:
> > > > > > > > >
> > > > > > > > > > +1
> > > > > > > > > >
> > > > > > > > > > O
gt; >
> > > > > > > > > +1
> > > > > > > > >
> > > > > > > > > On Wed, Dec 4, 2019 at 1:47 PM Fangjin Yang <
> > fang...@imply.io>
> > > > > wrote:
> > > > > > > > >
> > >
; > > > > > >
> > > > > > > > On Wed, Dec 4, 2019 at 1:47 PM Fangjin Yang <
> fang...@imply.io>
> > > > wrote:
> > > > > > > >
> > > > > > > > > +1
> > > > > > &g
On Wed, Dec 4, 2019 at 12:36 PM Julian Hyde <
> jh...@apache.org>
> > > > > wrote:
> > > > > > > >
> > > > > > > > > +1
> > &
; > > On Wed, Dec 4, 2019 at 12:36 PM Julian Hyde
> > > > wrote:
> > > > > > >
> > > > > > > > +1
> > > > > > > >
> > > > > > > >
> > > > > > &g
gt;
> > > > > > On Wed, Dec 4, 2019 at 12:36 PM Julian Hyde
> > > wrote:
> > > > > >
> > > > > > > +1
> > > > > > >
> > > > > > >
> > > > > > > > On Dec 4, 2019, at 12:19 PM
> > > On Dec 4, 2019, at 12:19 PM, Gian Merlino
> > wrote:
> > > > > > >
> > > > > > > Earlier this year, Druid voted to graduate to a top level
> > project.
> > > > The
> > > > > > vote
>
;
> > > > > +1
> > > > >
> > > > >
> > > > > > On Dec 4, 2019, at 12:19 PM, Gian Merlino
> wrote:
> > > > > >
> > > > > > Earlier this year, Druid voted to graduate to a top level
> project.
> > Earlier this year, Druid voted to graduate to a top level project.
> > The
> > > > vote
> > > > > passed and a resolution was submitted to the Board, but needed to
> be
> > > > > shelved at the last minute. We are now ready
; >
> > >
> > > > On Dec 4, 2019, at 12:19 PM, Gian Merlino wrote:
> > > >
> > > > Earlier this year, Druid voted to graduate to a top level project.
> The
> > > vote
> > > > passed and a resolution was submitted to the Boa
raduate to a top level project. The
> > vote
> > > passed and a resolution was submitted to the Board, but needed to be
> > > shelved at the last minute. We are now ready to proceed to graduation
> > once
> > > again, and so I would like to call another vote.
&
Board, but needed to be
> > shelved at the last minute. We are now ready to proceed to graduation
> once
> > again, and so I would like to call another vote.
> >
> > For reference, our last vote thread:
> >
> https://lists.apache.org/thread.html/7517dd38fbeb28978b1188b
Earlier this year, Druid voted to graduate to a top level project. The vote
passed and a resolution was submitted to the Board, but needed to be
shelved at the last minute. We are now ready to proceed to graduation once
again, and so I would like to call another vote.
For reference, our last vote
Hi all,
The vote to proceed with graduation of Apache Druid passed with ten +1 PPMC
votes:
David Lim
Fangjin Yang
Gian Merlino
Himanshu Gupta
Jihoon Son
Jonathan Wei
Kurt Young
Lijin Bin
Nishant Bangarwa
Slim Bouguerra
In addition the following three non-binding +1 votes were received
ow
> > to the Incubator PMC, who would vote on sending it on to the Apache
> Board.
> >
> > Vote:
> > [ ] +1 - Recommend graduation of Apache Druid as a TLP
> > [ ] -1 - Do not recommend graduation of Apache Druid because...
> >
> > The VOTE is open for a minimum of 72 hou
to a top level
> project.
>
> If this vote passes, the next step would be to submit the resolution below
> to the Incubator PMC, who would vote on sending it on to the Apache Board.
>
> Vote:
> [ ] +1 - Recommend graduation of Apache Druid as a TLP
> [ ] -1 - Do not recommend g
e.org>
> > > > > > wrote:
> > > > > > > > >
> > > > > > > > > > Following our discussion on the dev mailing list (
> > > > > > > > > >
> > > > > > > > > >
> > > > > >
te:
> > > > > > > >
> > > > > > > > > Following our discussion on the dev mailing list (
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > &
gt;
> > >
> >
> https://lists.apache.org/thread.html/68fcc3d2fc66c7f559e2c9dd02478d17f195565fecdb07ed53bc965e@%3Cdev.druid.apache.org%3E
> > > > > > > > ),
> > > > > > > > I would like to call a vote for Apache Druid graduating to a
> > top
> &g
> https://lists.apache.org/thread.html/68fcc3d2fc66c7f559e2c9dd02478d17f195565fecdb07ed53bc965e@%3Cdev.druid.apache.org%3E
> > > > > > > ),
> > > > > > > I would like to call a vote for Apache Druid graduating to a
> top
> > > > level
> > &
;
> >
> https://lists.apache.org/thread.html/68fcc3d2fc66c7f559e2c9dd02478d17f195565fecdb07ed53bc965e@%3Cdev.druid.apache.org%3E
> > > > > > ),
> > > > > > I would like to call a vote for Apache Druid graduating to a top
> > > level
> > > &
id graduating to a top
> > level
> > > > > project.
> > > > >
> > > > > If this vote passes, the next step would be to submit the
> resolution
> > > > below
> > > >
id graduating to a top
> > level
> > > > > project.
> > > > >
> > > > > If this vote passes, the next step would be to submit the
> resolution
> > > > below
> > > >
ruid.apache.org%3E
> > > > ),
> > > > I would like to call a vote for Apache Druid graduating to a top
> level
> > > > project.
> > > >
> > > > If this vote passes, the next step would be to submit the resolution
> > > b
project.
> > >
> > > If this vote passes, the next step would be to submit the resolution
> > below
> > > to the Incubator PMC, who would vote on sending it on to the Apache
> > Board.
> > >
> > > Vote:
> > > [ ] +1 - Recom
ld vote on sending it on to the Apache
> Board.
> >
> > Vote:
> > [ ] +1 - Recommend graduation of Apache Druid as a TLP
> > [ ] -1 - Do not recommend graduation of Apache Druid because...
> >
> > The VOTE is open for a minimum of 72 hours.
> >
&
ruid graduating to a top level
> project.
>
> If this vote passes, the next step would be to submit the resolution below
> to the Incubator PMC, who would vote on sending it on to the Apache Board.
>
> Vote:
> [ ] +1 - Recommend graduation of Apache Druid as a TLP
> [ ] -1
be to submit the resolution below
to the Incubator PMC, who would vote on sending it on to the Apache Board.
Vote:
[ ] +1 - Recommend graduation of Apache Druid as a TLP
[ ] -1 - Do not recommend graduation of Apache Druid because...
The VOTE is open for a minimum of 72 hours.
Establish
Another update, I am going to draft another resolution containing
adjustments from the past week, based on folks who have said they're
interested in joining or leaving the PMC. For anyone that hadn't replied
over the past week, I'll keep status quo. I'll post a vote thread with the
new one.
On
An update, I'm just waiting for replies to some of the messages I sent to
committers privately asking if they are interested in joining the initial
PMC. As mentioned last week -- I'll add folks that express interest to a
proposed resolution, which I plan to post for a vote within a day or two.
On
+1 Congratulations!
Julian Hyde 于2019年7月3日周三 上午1:51写道：
> > On Jun 26, 2019, at 10:23 PM, Gian Merlino wrote:
> > Speaking for myself I would be happy to have any of you (Julian,
> > Jun, Taylor) if you're interested. It sounds like you might be, Julian,
> > which if so is great.
>
> Yes, I
> On Jun 26, 2019, at 10:23 PM, Gian Merlino wrote:
> Speaking for myself I would be happy to have any of you (Julian,
> Jun, Taylor) if you're interested. It sounds like you might be, Julian,
> which if so is great.
Yes, I would be happy to serve on the PMC, if that is what the community wants.
gt; >>
>> >> In this self-assessment, three things that come up as areas for
>> improvement
>> >> are better documenting our release process (RE50), publicly posting a
>> place
>> >> where security issues can be confidentially reported (QU30), and
>
curity issues can be confidentially reported (QU30), and
> posting a
> >> list of PMC members online (CS10), perhaps once we have a proper PMC.
> >>
> >> Could people please review the above documents? Assuming they look in
> order
> >> then I will start a forma
>>
>> On Fri, Jun 21, 2019 at 11:59 AM Gian Merlino wrote:
>>
>>> I've updated the status page:
>>> http://incubator.apache.org/projects/druid.html. I think it's pretty
>>> accurate now. I will start going through the other stuff on the
>> graduatio
've updated the status page:
> > http://incubator.apache.org/projects/druid.html. I think it's pretty
> > accurate now. I will start going through the other stuff on the
> graduation
> > list too. Is anyone interested in self-assessing us against the maturity
> > model? Li
documents? Assuming they look in order
then I will start a formal VOTE.
On Fri, Jun 21, 2019 at 11:59 AM Gian Merlino wrote:
> I've updated the status page:
> http://incubator.apache.org/projects/druid.html. I think it's pretty
> accurate now. I will start going through the other stuff on the g
I've updated the status page:
http://incubator.apache.org/projects/druid.html. I think it's pretty
accurate now. I will start going through the other stuff on the graduation
list too. Is anyone interested in self-assessing us against the maturity
model? Like Julian said it isn't required
t; > >>>
> > > >>>> +1
> > > >>>>
> > > >>>> On Thu, Jun 13, 2019 at 10:33 PM Charles Allen <
> cral...@apache.org>
> > > >>> wrote:
> > > >>>>
> > > >>>>
> >>>> +1
> > >>>>
> > >>>> On Thu, Jun 13, 2019 at 10:33 PM Charles Allen
> > >>> wrote:
> > >>>>
> > >>>>> +1
> > >>>>>
> > >>>>>
> > >>>>>
> >>>> +1
> >>>>
> >>>> On Thu, Jun 13, 2019 at 10:33 PM Charles Allen
> >>> wrote:
> >>>>
> >>>>> +1
> >>>>>
> >>>>>
> >>>>>
> >>>>> On Fri, Jun 7,
t; > > +1
> > > >
> > > >
> > > >
> > > > On Fri, Jun 7, 2019, 9:27 PM Gian Merlino wrote:
> > > >
> > > > > Hey Druids,
> > > > >
> > > > > Druid has been in the incubator for a while, and we have d
> > > > far (0.13.0, 0.14.0, 0.14.1, and 0.14.2) with a 5th on the way. There
> > has
> > > > been some discussion off-list recently about pushing for graduation
> and
> > > it
> > > > was pointed out that it is way past time to have a discussion about
gt; > > Druid has been in the incubator for a while, and we have done 4
> releases
> > so
> > > far (0.13.0, 0.14.0, 0.14.1, and 0.14.2) with a 5th on the way. There
> has
> > > been some discussion off-list recently about pushing for graduation and
> > it
&
.0, 0.14.1, and 0.14.2) with a 5th on the way. There has
> > been some discussion off-list recently about pushing for graduation and
> it
> > was pointed out that it is way past time to have a discussion about
> > graduation readiness on-list. So the topic of discussion for this th
+1
On Fri, Jun 7, 2019, 9:27 PM Gian Merlino wrote:
> Hey Druids,
>
> Druid has been in the incubator for a while, and we have done 4 releases so
> far (0.13.0, 0.14.0, 0.14.1, and 0.14.2) with a 5th on the way. There has
> been some discussion off-list recently about pushing
> Hey Druids,>
> > >
> > > Druid has been in the incubator for a while, and we have done 4
> releases
> > so>
> > > far (0.13.0, 0.14.0, 0.14.1, and 0.14.2) with a 5th on the way. There
> > has>
> > > been some discussion off-list
off-list recently about pushing for graduation and it>
> was pointed out that it is way past time to have a discussion about>
> graduation readiness on-list. So the topic of discussion for this thread>
> is: are we ready to graduate?>
>
> Here are some links I'
ruid has been in the incubator for a while, and we have done 4 releases
> > so far (0.13.0, 0.14.0, 0.14.1, and 0.14.2) with a 5th on the way. There
> > has been some discussion off-list recently about pushing for graduation
> and
> > it was pointed out that it is way past time
+1, let's graduate.
On Wed, Jun 12, 2019 at 1:52 PM Fangjin Yang wrote:
> +1 for graduation
>
> On Wed, Jun 12, 2019 at 1:43 PM Gian Merlino wrote:
>
> > In the last few days, website migration to https://druid.apache.org/ and
> > content update to comply with
> htt
wrote:
> Hey Druids,
>
> Druid has been in the incubator for a while, and we have done 4 releases
> so far (0.13.0, 0.14.0, 0.14.1, and 0.14.2) with a 5th on the way. There
> has been some discussion off-list recently about pushing for graduation and
> it was pointed out that i
Hey Druids,
Druid has been in the incubator for a while, and we have done 4 releases so
far (0.13.0, 0.14.0, 0.14.1, and 0.14.2) with a 5th on the way. There has
been some discussion off-list recently about pushing for graduation and it
was pointed out that it is way past time to have
gt; Rajiv.
>
> From: Gian Merlino
> Sent: Monday, April 22, 2019 7:04:25 PM
> To: dev@druid.apache.org; eyurma...@oath.com
> Subject: Re: Experimental feature 'graduation' in 0.14
>
> I think it's fine to release new query features that don't have
Has there been any thought given to integration with Presto?
Rajiv.
From: Gian Merlino
Sent: Monday, April 22, 2019 7:04:25 PM
To: dev@druid.apache.org; eyurma...@oath.com
Subject: Re: Experimental feature 'graduation' in 0.14
I think it's fine to release new
I haven't seen objection, so, I will do a PR to make this change soon.
On Mon, Apr 22, 2019 at 7:04 PM Gian Merlino wrote:
> I think it's fine to release new query features that don't have Druid SQL
> support, although I would certainly encourage people to add SQL support
> even if it's not
I think it's fine to release new query features that don't have Druid SQL
support, although I would certainly encourage people to add SQL support
even if it's not required. In the long run I wish that SQL could become the
primary query language for Druid, because in Druid's space (analytical
What does this mean for release of new query features without Druid SQL
support?
On Mon, Apr 22, 2019 at 2:07 PM Jihoon Son wrote:
> +1
> I'm mostly using only SQL.
>
> Jihoon
>
> On Mon, Apr 22, 2019 at 12:24 PM Jonathan Wei wrote:
>
> > +1, I think it has enough feature parity with the
+1
I'm mostly using only SQL.
Jihoon
On Mon, Apr 22, 2019 at 12:24 PM Jonathan Wei wrote:
> +1, I think it has enough feature parity with the native JSON queries, and
> it's stable enough to be moved out of experimental.
>
> On Thu, Apr 18, 2019 at 6:23 PM Fangjin Yang wrote:
>
> > Strong +1
+1, I think it has enough feature parity with the native JSON queries, and
it's stable enough to be moved out of experimental.
On Thu, Apr 18, 2019 at 6:23 PM Fangjin Yang wrote:
> Strong +1
>
> I think there's been enough production usage of Druid SQL, it matches what
> native JSON-over-http
Hi Mat,
Ah, right. IMO https://github.com/apache/incubator-druid/pull/6742 is a
decent workaround towards making #6176 less of a problem. It would prevent
incorrect results from happening (the broker will not start up its http
server & announce itself, and so it won't get picked up by clients, if
A remaining issue with SQL is
https://github.com/apache/incubator-druid/issues/6176
We've seen it happen several times in production on 0.12, where thankfully
SQL doesn't power anything critical. The current workarounds are:
1. Restart the broker. Obviously not a good solution.
2. Migrate to HTTP
I am ok with officially deprecating or sunsetting Tranquility. Sunsetting
may make more sense since a few of us are still committed to fixing
critical bugs with it, but I don't know of anyone that is actively working
on new features.
It was never part of the main Druid repo, so IMO all that
68 matches
Mail list logo
