bookkeeper-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sijie Guo <guosi...@gmail.com>
Subject Re: HTTP / REST API?
Date Tue, 07 Nov 2017 19:24:06 GMT
On Tue, Nov 7, 2017 at 7:22 AM, Enrico Olivelli <eolivelli@gmail.com> wrote:

>
>
> 2017-11-07 16:16 GMT+01:00 Ivan Kelly <ivank@apache.org>:
>
>> > We have an issue to document this feature.  At the same time, you can
>> > checkout this BP for details -
>> > https://cwiki.apache.org/confluence/display/BOOKKEEPER/BP-
>> 17%3A+Define+BookKeeper+public+http+endpoints
>> BP-17 only defines endpoints for metadata operations though, nothing
>> for adding entries ledger, or even creating a ledger.
>>
>> Perhaps we could add these to allow simple non-java clients to be written.
>>
>
> I think that reading data would be simple to be implemented, both in the
> HTTP API and even for a non java language (because we are using protobuf).
>
> Writing is difficult, because the java client writer is really the core of
> BookKeeper, it deals with fencing, ensemble changes....
> It would be simple to write a client which pushes data to bookies but all
> the LAC+fencing protocols (+ metadata management) are hard to re-implement.
>

I don't think we need to reimplement all this details in http api. what
people probably need here, is streaming the entries to a ledger, all the
fencing are delegated to http endpoint.

The only difference is -- the user should be aware of ledger being closed
if a http server is down.


>
> Maybe the best option would be to add an HTTP API or some kind of proxy
>
> I will be happy to see such API
>
> Enrico
>
>
>>
>> -Ivan
>>
>
>

Mime
View raw message