asterixdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Yingyi Bu <buyin...@gmail.com>
Subject Re: Choosing defaults for AsterixDB
Date Sat, 04 Feb 2017 02:02:52 GMT
>> I want to pick up this thread to verify if the AQL will still be
supported in the future?

AQL will still stay there.

However, "supported" might not be a 100% accurate term for an ASF open
source software.
Regardless of AQL or SQL++, if a user finds a bug or needs an improvement
in any place of the system, s/he can open an issue.
Then, if some committer/contributor is interested in fixing the bug, then
s/he submits a patch.
The process is volunteer or up to committers' interests.  At least, that's
my understanding of how ASF software works.
This is very different from a paid enterprise software -- a reported bug or
a wanted feature from customers must be responded (and/or fixed):-)

Thoughts?


>> It will be a hard work to switch to SQL++.
Why translating to SQL++ is harder than AQL?  I wonder if the current SQL++
language design and implementation misses some key pieces.

Best,
Yingyi


On Fri, Feb 3, 2017 at 5:37 PM, Jianfeng Jia <jianfeng.jia@gmail.com> wrote:

> Hi, I want to pick up this thread to verify if the AQL will still be
> supported in the future?
> Currently, Cloudberry automatically translates the JSON request to AQL
> statements. It will be a hard work to switch to SQL++.
>
> I’m not object to set the default option to SQL++. However, we will keep
> the support for AQL, right?  (especially in the RESTFull API).
>
> > On Jan 10, 2017, at 5:47 PM, Till Westmann <tillw@apache.org> wrote:
> >
> > Ok, since there’s a lot of agreement and no concerns, I’ll go ahead.
> >
> > Thanks,
> > Till
> >
> > On 10 Jan 2017, at 9:22, Yingyi Bu wrote:
> >
> >> +100!
> >>
> >> On Tue, Jan 10, 2017 at 9:17 AM, Mike Carey <dtabass@gmail.com> wrote:
> >>
> >>> +1 from me too for SQL++ and clean JSON.
> >>>
> >>>
> >>>
> >>> On 1/10/17 8:25 AM, Murtadha Hubail wrote:
> >>>
> >>>> +1 to SQL++ and clean JSON.
> >>>>
> >>>> Cheers,
> >>>> Murtadha
> >>>>
> >>>> On Jan 10, 2017, at 9:46 AM, Till Westmann <tillw@apache.org>
wrote:
> >>>>>
> >>>>> Hi,
> >>>>>
> >>>>> as you know AsterixDB supports 2 query languages (AQL and SQL++)
and
> many
> >>>>> output formats (ADM, clean JSON, lossless JSON, CSV). Our current
> >>>>> defaults
> >>>>> for these options (at least on the web interface) are AQL and ADM.
> >>>>>
> >>>>> I’d like to propose to change those defaults to be SQL++ and (clean)
> >>>>> JSON.
> >>>>> The reason for wanting them to change, is that I think that these
> choices
> >>>>> are more attractive to new users of the system and thus can help
to
> >>>>> increase
> >>>>> the adoption of AsterixDB. A user with some database experience
is
> much
> >>>>> more
> >>>>> likely to have previous SQL experience and to feel at home with
SQL++
> >>>>> than
> >>>>> having XQuery experience and feeling at home with AQL. Similarly,
> most
> >>>>> users
> >>>>> will want to use the data that they get out of AsterixDB in an
> >>>>> application
> >>>>> and it will be a lot easier to consume JSON than it is to consume
> ADM.
> >>>>>
> >>>>> I've prepared a (tiny) change to change the defaults [1] and I'm
> >>>>> wondering
> >>>>> if there are concerns that should keep us from making this change.
> >>>>>
> >>>>> Cheers,
> >>>>> Till
> >>>>>
> >>>>> [1] https://asterix-gerrit.ics.uci.edu/#/c/1409/
> >>>>>
> >>>>
> >>>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message