Mailing-List: contact dev-help@asterixdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@asterixdb.apache.org
MIME-Version: 1.0
In-Reply-To: <B9100404-B2B8-4287-A721-39676C7782BB@gmail.com>
References: <D3A14168-A0DB-4C07-A3B0-F834965F92F6@apache.org>
 <9B87BCFE-A957-42BB-80F1-E76EE26D67D6@apache.org> <1340feeb-6ac7-585f-304d-f117a3a3cc81@gmail.com>
 <CALjEsF4-JcT2R38eJ0tBfBF4nqwQ6ymJzVdAZOBT+_VgU1E_iQ@mail.gmail.com>
 <EF18BE9D-F71C-44B4-B5AB-52CF6D829260@apache.org> <B9100404-B2B8-4287-A721-39676C7782BB@gmail.com>
From: Yingyi Bu <buyingyi@gmail.com>
Date: Fri, 3 Feb 2017 18:02:52 -0800
Message-ID: <CALjEsF5hGr3TjfJ5-1nsQdE0mFe+T84Lhf8063mr831wUmBu5Q@mail.gmail.com>
Subject: Re: Choosing defaults for AsterixDB
To: dev@asterixdb.apache.org
Content-Type: multipart/alternative; boundary=f403045eadced05ec30547aacbe4
archived-at: Sat, 04 Feb 2017 02:03:02 -0000

--f403045eadced05ec30547aacbe4
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

>> 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=E2=80=99m not object to set the default option to SQL++. However, we wi=
ll 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=E2=80=99s a lot of agreement and no concerns, I=E2=80=
=99ll 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++) an=
d
> 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=E2=80=99d like to propose to change those defaults to be SQL++ an=
d (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/
> >>>>>
> >>>>
> >>>
>
>

--f403045eadced05ec30547aacbe4--