This Vote now closed. There is the majority who are not in favor of
including the REST server.
Thanks everyone for participating.
Vote tally:
+1 Votes:
Harsha Chintalapani
Parth Brahbhatt
Ken Jackson
Suresh Srinivas
Jungtaek Lim
Ali Akthar
Haohui Mai
Shekhar Tippu
Oops. Sorry, didn't notice the 72h voting period has passed. You can
disregard.
Gwen
On Sat, Oct 29, 2016 at 4:29 PM, Gwen Shapira wrote:
> -1
>
> Kafka's development model is a good fit for critical path and
> well-established APIs. It doesn't work as well for add-ons that need to
> rapidly ev
-1
Kafka's development model is a good fit for critical path and
well-established APIs. It doesn't work as well for add-ons that need to
rapidly evolve. Merging communities with different development pace and
models rarely ends well - I think the REST Proxy will benefit from being a
separate proje
-1
I think a good set of HTTP APIs can simplify client implementations and
allow for easier integration with Kafka as well as simpler ops/admin
tools. Elasticsearch is a great example. However, I think it's too early
to put this into the core. The existing Kafka REST proxies (that I know
of) ar
-1.
I would personally like Kafka core to be limited to the core aspects. I
consider REST server like this more a tooling thing than a core aspect
of Kafka and would like it to be outside of Kafka.
-Jaikiran
On Wednesday 26 October 2016 02:46 AM, Harsha Chintalapani wrote:
Hi All,
-1
>From my experience, nothing good comes from merges similar to this one, as
it has huge implications in terms of codebase maintenance, CD pipeline
duration and stability as well as isolated testability. I don't see any
particular worth benefit on having the REST server in the core repository
as
-1 for http kafka client in core
Although a read only management interface, perhaps via http, sounds kinda
useful for things like health checks as mentioned.
On Wed, Oct 26, 2016 at 2:00 PM, Zakee wrote:
> -1
>
> Thanks.
> > On Oct 25, 2016, at 2:16 PM, Harsha Chintalapani
> wrote:
> >
> > Hi
-1
Thanks.
> On Oct 25, 2016, at 2:16 PM, Harsha Chintalapani wrote:
>
> Hi All,
> We are proposing to have a REST Server as part of Apache Kafka
> to provide producer/consumer/admin APIs. We Strongly believe having
> REST server functionality with Apache Kafka will help a lot of user
: Re: [VOTE] Add REST Server to Apache Kafka
+1
Thanks
+1
Thanks
-1
On Wed, Oct 26, 2016 at 9:23 AM, Shekar Tippur wrote:
> +1
>
> Thanks
-1
First, I think there was no technical discussion of the KIP details in the
DISCUSS until now, just a binary yes/no. Real discussion just started with
the excellent ten technical points from Ewen a few hours ago.
Generally,I don't see how a standard REST makes sense for format-agnostic
realtime s
Harsha -- Thanks for clarifying but I had noticed that and still gave those
suggestions.
Calling a VOTE thread on a discussion when there are varied viewpoints is
never something this community has resorted to. The optics of it force
binary decision making when in reality there are several tradeof
Perhaps in the future we can use a [POLL] or similar? This confused a lot
of folks because they thought a VOTE was being called on KIP-80 when it
wasn't. (Even if we say shame on them for not reading the body in full, the
title caught me as well.)
-Ewen
On Tue, Oct 25, 2016 at 7:11 PM, Harsha Chi
Neha,
As I stated in my earlier email, this is an interest check
vote thread and, not a KIP vote thread, to gather input from users mailing
list if there is any interest for REST server to be part of Kafka. Also,
this has been noted in the discuss thread that we should make an interest
vot
Neha,
As I stated in my earlier email . This is an interest check
vote thread and , not a KIP vote thread, to gather input from users mailing
list if there is any interest for REST server to be part of Kafka. Also,
this has been noted in the discuss thread that we should make a interest
vo
-1
Let me make an observation and then state my reasons.
First, I am a little surprised to see this vote thread as I think it is a
bit premature. As a community, we've consistently invested in good
communication. If there are differing opinions on a DISCUSS thread, we
generally gather the communi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
- -1
Kafka offers a protocol clients can implement, and REST server is only
one of many clients. If we include REST, we need to include any other
client, too, which seems not to be reasonable to me.
- -Matthias
On 10/25/16 5:29 PM, Haohui Mai wrot
+1
In my personal experience Kafka REST server is one of essential parts on
building a reliable real-time pipeline. It's okay to keep the code
reasonably separated from the core, but would appreciate to see some
official supports for the REST servers from the Kafka community.
Regards,
Haohui
On
-1
I think it's good to avoid adding non-essential items to the Apache Kafka
project so that it can continue evolving at a fast pace. Since a REST
server can be naturally implemented as an external project, I believe the
disadvantages of including it outweigh the advantages.
Ismael
On Tue, Oct 2
Sorry a typo. -1 instead.
Thanks,
Jun
On Tue, Oct 25, 2016 at 4:24 PM, Jun Rao wrote:
> +1
>
> Thanks,
>
> Jun
>
> On Tue, Oct 25, 2016 at 2:16 PM, Harsha Chintalapani
> wrote:
>
>> Hi All,
>>We are proposing to have a REST Server as part of Apache Kafka
>> to provide producer/co
+1
Thanks,
Jun
On Tue, Oct 25, 2016 at 2:16 PM, Harsha Chintalapani
wrote:
> Hi All,
>We are proposing to have a REST Server as part of Apache Kafka
> to provide producer/consumer/admin APIs. We Strongly believe having
> REST server functionality with Apache Kafka will help a lot
+ 1
On Tue, Oct 25, 2016 at 10:16 PM, Harsha Chintalapani
wrote:
> Hi All,
>We are proposing to have a REST Server as part of Apache Kafka
> to provide producer/consumer/admin APIs. We Strongly believe having
> REST server functionality with Apache Kafka will help a lot of users.
>
;> > of
> >> > > > Apache Kafka under ASF governance model. This would be great for
> >> the
> >> > > > community instead of duplicated and splintered efforts that may
> >> spring
> >> > > up.
> >> > > >
-1
As an end-user, while I like the idea in theory, in practice I don't think
it's a good idea just yet.
Certainly, it'd be useful, enabling things like
https://github.com/Landoop/kafka-topics-ui to work without needing anything
outside of Kafka core.
But there are already enough things in the e
ctober 25, 2016 2:20 PM
> Subject: [VOTE] Add REST Server to Apache Kafka
> To: mailto:dev@kafka.apache.org>>, <
> us...@kafka.apache.org<mailto:us...@kafka.apache.org>>
>
>
> Hi All,
>We are proposing to have a REST Server as part of Apache Kafka
kef>
_
From: Harsha Chintalapani mailto:ka...@harsha.io>>
Sent: Tuesday, October 25, 2016 2:20 PM
Subject: [VOTE] Add REST Server to Apache Kafka
To: mailto:dev@kafka.apache.org>>,
mailto:us...@kafka.apache.org>>
Hi All,
We are proposing to have a REST Server as
+1.
On Tue, Oct 25, 2016 at 2:58 PM, Jay Kreps wrote:
> -1
>
> I think the REST server for Kafka that already exists is quite good and
> getting contributions. Moving this into the core project doesn't solve a
> problem that I see.
>
> -Jay
>
> On Tue, Oct 25, 2016 at 2:16 PM, Harsha Chintalapan
-1
I think the REST server for Kafka that already exists is quite good and
getting contributions. Moving this into the core project doesn't solve a
problem that I see.
-Jay
On Tue, Oct 25, 2016 at 2:16 PM, Harsha Chintalapani
wrote:
> Hi All,
>We are proposing to have a REST Server
Hi All,
We are proposing to have a REST Server as part of Apache Kafka
to provide producer/consumer/admin APIs. We Strongly believe having
REST server functionality with Apache Kafka will help a lot of users.
Here is the KIP that Mani Kumar wrote
https://cwiki.apache.org/confluence/disp
30 matches
Mail list logo
