Or possibly how to retire it and then re-do similarity joins using the
join infrastructure ideas discussed a year or so ago, perhaps. (We
should think about whether or not the time it would take to do SQL+++
might be better used to not use that approach anymore - it was an
interesting experime
Let's discuss how to move AQL+ to SQL++ after Taewoo comes back.
On Thu, Sep 7, 2017 at 12:10 PM, Taewoo Kim wrote:
> For similarity join, we use AQL+ that is based on AQL. I think deprecating
> (not removing) AQL is OK. Ultimately, AQL+ should be converted to SQL++ :-)
>
> Best,
> Taewoo
>
> On
For similarity join, we use AQL+ that is based on AQL. I think deprecating
(not removing) AQL is OK. Ultimately, AQL+ should be converted to SQL++ :-)
Best,
Taewoo
On Thu, Sep 7, 2017 at 9:04 PM, Steven Jacobs wrote:
> I’ll give the BADest +1 I can :)
> Steven
>
> On Thu, Sep 7, 2017 at 8:50 PM
I think this seals it :)
> On Sep 7, 2017, at 11:49, Gerald Sangudi wrote:
>
> :-)
>
> On Sep 7, 2017 11:44 AM, "Michael Carey" wrote:
>
> As AsterixDB evolves, and additional features are added - e.g., DISTINCT
> aggregate support, or properly implemented query-bodied functions,
> supporting
I’ll give the BADest +1 I can :)
Steven
On Thu, Sep 7, 2017 at 8:50 PM Gerald Sangudi wrote:
> :-)
>
> On Sep 7, 2017 11:44 AM, "Michael Carey" wrote:
>
> As AsterixDB evolves, and additional features are added - e.g., DISTINCT
> aggregate support, or properly implemented query-bodied functions
+1!
Best,
Xikui
> On Sep 7, 2017, at 11:49, Gerald Sangudi wrote:
>
> :-)
>
> On Sep 7, 2017 11:44 AM, "Michael Carey" wrote:
>
> As AsterixDB evolves, and additional features are added - e.g., DISTINCT
> aggregate support, or properly implemented query-bodied functions,
> supporting two que
:-)
On Sep 7, 2017 11:44 AM, "Michael Carey" wrote:
As AsterixDB evolves, and additional features are added - e.g., DISTINCT
aggregate support, or properly implemented query-bodied functions,
supporting two query languages is hugely expensive: Updating two grammars,
parsers, rules, tests, ... I
+1!
Best,
Yingyi
On Thu, Sep 7, 2017 at 11:44 AM, Michael Carey wrote:
> As AsterixDB evolves, and additional features are added - e.g., DISTINCT
> aggregate support, or properly implemented query-bodied functions,
> supporting two query languages is hugely expensive: Updating two grammars,
>
As AsterixDB evolves, and additional features are added - e.g., DISTINCT
aggregate support, or properly implemented query-bodied functions,
supporting two query languages is hugely expensive: Updating two
grammars, parsers, rules, tests, ... IMO it is time to let go of AQL as
an externally sup
