Great. I have updated the KIP.
Thanks,
David
On Thu, Sep 19, 2019 at 10:56 PM Colin McCabe wrote:
> Sounds good to me. It makes sense to add this functionality to the
> command line.
>
> best,
> Colin
>
> On Wed, Sep 18, 2019, at 11:26, David Jacot wrote:
> > Indeed, I have forgotten to add th
Sounds good to me. It makes sense to add this functionality to the command
line.
best,
Colin
On Wed, Sep 18, 2019, at 11:26, David Jacot wrote:
> Indeed, I have forgotten to add the action. There will be a new action «
> —delete-offsets ». Sorry!
>
> *Proposed API*
> kafka-consumer-groups.sh
Indeed, I have forgotten to add the action. There will be a new action «
—delete-offsets ». Sorry!
*Proposed API*
kafka-consumer-groups.sh --bootstrap-server
—delete-offsets --group --topic :
ex: --bootstrap-server localhost:9092 --group my-group --topic
topic1 --topic topic2:0,1,2
When partit
On Tue, Sep 17, 2019, at 09:07, David Jacot wrote:
> Hi all,
>
> We haven't included the changes in the command line tool to support the new
> API. Therefore,
> I would like to amend the current KIP to cover the changes in the
> `kafka-consumer-groups`
> command line tool. The change is rather sma
Hi all,
We haven't included the changes in the command line tool to support the new
API. Therefore,
I would like to amend the current KIP to cover the changes in the
`kafka-consumer-groups`
command line tool. The change is rather small and it does not need to add
any new arguments
to the command l
Hi David,
Sounds good.
best,
Colin
On Fri, Sep 13, 2019, at 04:45, David Jacot wrote:
> Hi all,
>
> I would like to do another modification to the proposal. In the proposal,
> the OffsetDeleteResponse
> doesn't have a top level error field so I would like to add one. Many
> errors concern the
Hi all,
I would like to do another modification to the proposal. In the proposal,
the OffsetDeleteResponse
doesn't have a top level error field so I would like to add one. Many
errors concern the whole
group (e.g. GROUP_ID_NOT_FOUND) so it would be great to have a way to
communicate them
back to t
Hi all,
While implementing the KIP, I have realized that a new error code and
exception is required to notify the caller that offsets of a topic can not
be deleted because the group is actively subscribed to the topic.
I would like to know if there are any concerns with these changes before
updat
+1 (non binding)
Thanks!
On Thu, Aug 15, 2019 at 11:53 PM Colin McCabe wrote:
>
> On Thu, Aug 15, 2019, at 11:47, Jason Gustafson wrote:
> > Hey Colin, I think deleting all offsets is equivalent to deleting the
> > group, which can be done with the `deleteConsumerGroups` api. I debated
> > whethe
On Thu, Aug 15, 2019, at 11:47, Jason Gustafson wrote:
> Hey Colin, I think deleting all offsets is equivalent to deleting the
> group, which can be done with the `deleteConsumerGroups` api. I debated
> whether there should be a way to delete partitions for all unsubscribed
> topics, but I decided
Hey Colin, I think deleting all offsets is equivalent to deleting the
group, which can be done with the `deleteConsumerGroups` api. I debated
whether there should be a way to delete partitions for all unsubscribed
topics, but I decided to start with a simple API.
I'm going to close this vote. The
Hi Jason,
Thanks for the KIP.
Is there ever a desire to delete all the offsets for a given group? Should the
protocol and tools support this?
+1 (binding)
best,
Colin
On Mon, Aug 12, 2019, at 10:57, Guozhang Wang wrote:
> +1 (binding).
>
> Thanks Jason!
>
> On Wed, Aug 7, 2019 at 11:18 AM
+1 (binding).
Thanks Jason!
On Wed, Aug 7, 2019 at 11:18 AM Jason Gustafson wrote:
> Hi All,
>
> I'd like to start a vote on KIP-496:
>
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-496%3A+Administrative+API+to+delete+consumer+offsets
> .
> +1
> from me of course.
>
> -Jason
>
--
-
13 matches
Mail list logo
