asterixdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ian Maxon <ima...@uci.edu>
Subject Re: New Asterix REST API design
Date Fri, 15 Apr 2016 21:11:11 GMT
It seems to me like this new API would be a superset of the N1QL API,
right?

On Fri, Apr 15, 2016 at 1:19 PM, Wail Alkowaileet <wael.y.k@gmail.com>
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 <
> ildar.absalyamov@gmail.com> 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:
> >
> https://cwiki.apache.org/confluence/display/ASTERIXDB/New+HTTP+API+Design
> > <
> https://cwiki.apache.org/confluence/display/ASTERIXDB/New+HTTP+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
>

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