asterixdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Till Westmann" <>
Subject Re: New Asterix REST API design
Date Fri, 15 Apr 2016 21:48:06 GMT
Hi Wail,

I’m not completely sure that I understand how to implement the idea. 
If we
do this only in the API, it might be tricky to get the boundaries 
records right (e.g. if we do indentation on the server). However, if we 
to push this into the query engine, we need to understand enough of the
query/statements to put the limit clause in.
Both approaches don't look great to me.

What did you have in mind?


On 15 Apr 2016, at 13:19, Wail Alkowaileet wrote:

> Hi Ildar,
> I think if there's something I would love to have is getting partial 
> result
> instead of all result at once. This can be beneficial for result
> pagination. When I use AsterixDB UI, 50% of the time my tab crashes (I
> forget to limit the result).
> Thanks...
> On Fri, Apr 15, 2016 at 1:23 AM, Ildar Absalyamov <
>> wrote:
>> Hi Devs,
>> Recently there have been a number of conversations about the future 
>> of our
>> REST (aka HTTP) API. I summarized these discussions in an outline of 
>> the
>> new API design:
>> <
>>> .
>> The need to refactor existing API came from different directions (and 
>> from
>> different people), and is explained in motivation section. Thus I 
>> believe
>> it’s about the time to take an effort and improve existing API, so 
>> that it
>> will not drag us down in the future. However during the transition 
>> step I
>> believe it would be better to keep exiting API endpoints, so that we 
>> would
>> not break people’s current experimental setup.
>> It would be good to know feedback from the folks, who have been
>> contributing to that part of the systems recently.
>> Best regards,
>> Ildar
> -- 
> *Regards,*
> Wail Alkowaileet

View raw message