asterixdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Till Westmann" <ti...@apache.org>
Subject Re: Choosing defaults for AsterixDB
Date Sat, 04 Feb 2017 03:21:01 GMT
It currently doesn’t, but it also requires some more work.

If we want to use it for AQL, we should simply be able to create a 
second
instance of it with the AQL compilation provider.

Cheers,
Till

On 3 Feb 2017, at 18:57, Taewoo Kim wrote:

> Regarding this, I have a question.
>
> Does the new revised HTTP API - Query Service (/query/service) support 
> AQL?
> I am asking this since inside the code, it gets the SQLPP compilation
> provider.
>
> public class CCApplicationEntryPoint implements 
> ICCApplicationEntryPoint {
>
>
>     protected IServlet createServLet(HttpServer server, Lets key, 
> String...
> paths) {
>
>         switch (key) {
>
>             case QUERY_SERVICE:
>
>                 return new QueryServiceServlet(server.ctx(), paths,
> ccExtensionManager.getSqlppCompilationProvider(),
>
>                         ccExtensionManager.getQueryTranslatorFactory(),
> componentProvider);
>
> Best,
> Taewoo
>
> On Fri, Feb 3, 2017 at 6:34 PM, Jianfeng Jia <jianfeng.jia@gmail.com> 
> wrote:
>
>> @Yingyi, I’m not saying learning SQL++ is difficult.
>> Currently, we have a class called AQLGenerator that can translate the
>> Cloudberry request syntax to AQL.  It took us several weeks finishing 
>> it.
>> I guess it will take similar time to write a SQLPPGenerator to 
>> achieve the
>> same goal.
>>
>> As long as the RESTFul API can accept AQL, we don’t need to spend 
>> time to
>> implement a new generator.
>>
>>> On Feb 3, 2017, at 6:02 PM, Yingyi Bu <buyingyi@gmail.com> wrote:
>>>
>>>>> 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.
>>
>>

Mime
View raw message