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
10 matches
Mail list logo
