Chia-Ping Tsai created KAFKA-17017:
--
Summary: AsyncConsumer#unsubscribe does not clean the assigned
partitions
Key: KAFKA-17017
URL: https://issues.apache.org/jira/browse/KAFKA-17017
Project: Kafka
Lianet Magrans created KAFKA-16301:
--
Summary: Review fenced member unsubscribe/subscribe callbacks
interaction
Key: KAFKA-16301
URL: https://issues.apache.org/jira/browse/KAFKA-16301
Project: Kafka
Lianet Magrans created KAFKA-15954:
--
Summary: Review minimal effort approach on consumer last heartbeat
on unsubscribe
Key: KAFKA-15954
URL: https://issues.apache.org/jira/browse/KAFKA-15954
Project
Hey Girish,
You may need to confirm the unsubscription with a second email.
When I was switching subscription emails, I sent one to the unsubscribe
email and then I got a reply.
In the reply it asked me to send to a unique email address to confirm. Look
for one from dev-h...@kafka.apache.org
Dear Team
I am repeatedly sending email to dev-unsubscr...@kafka.apache.org to
unsubscribe this email address of mine from the email notifications
received from dev@kafka.apache.org.
Could one of you please help me with the correct process?
Regards
Girish
on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr...@kafka.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
guozhangwang merged pull request #402:
URL: https://github.com/apache/kafka-site/pull/402
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev
explicit instructions to unsubscribe
from each list.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr...@kafka.apache.org
For queries about
che.org>
>
> however, it doesn’t work.
>
> Can anyone please intrust me a different way to unsubscribe from this mail
> list?
>
> Thanks a lot!
>
Hi,
I have sent an email to
dev-unsubscr...@kafka.apache.org<mailto:dev-subscr...@kafka.apache.org>
however, it doesn’t work.
Can anyone please intrust me a different way to unsubscribe from this mail list?
Thanks a lot!
Hi Team HirinGuru,
if you want to unsubscribe, see the description on how to do that on
https://kafka.apache.org/contact
Best,
Bruno
On 22.01.21 07:41, Hiringuru wrote:
Hi,
Kindly unsubscribe our email from your daily notification. We don't want to
receive any further notification.
I
Hi,
Kindly unsubscribe our email from your daily notification. We don't want to
receive any further notification.
I would be highly appreciated if you can check and remove our email from your
list.
Thanks
Team HirinGuru
Hello Admin
Please also remove my email from the list.
Thanks
Raymond
-Original Message-
From: Biswajit Ghosh
Sent: Thursday, March 28, 2019 11:09 AM
To: dev@kafka.apache.org
Subject: Unsubscribe request
Hi Admin,
Can you please unsubscribe my email address (biswaji
Hello Biswajit,
It's self-service :) https://kafka.apache.org/contact
See you in a few months.
Guozhang
On Thu, Mar 28, 2019 at 8:09 AM Biswajit Ghosh
wrote:
> Hi Admin,
>
> Can you please unsubscribe my email address (biswaji...@aqbsolutions.com)
> from Kafka dev group, curr
Hi Admin,
Can you please unsubscribe my email address (biswaji...@aqbsolutions.com)
from Kafka dev group, currently I have no time to develop Kafka, I'll be
with you guys in a few months I hope.
Thanks.
--
Regards,
biswajitGhosh
Please look at instruction on https://kafka.apache.org/contact for
unsubscribing
On Mon, Sep 18, 2017 at 10:24 AM, Madhav Ancha (BLOOMBERG/ 919 3RD A) <
manc...@bloomberg.net> wrote:
> unsubscribe
>
>
unsubscribe
From: dev@kafka.apache.org At: 09/18/17 13:24:09
To: dev@kafka.apache.org
Subject: Re: KIP-203: Add toLowerCase support to
sasl.kerberos.principal.to.local rule
Makes sense.
Please fill out JIRA name, etc.
On Mon, Sep 18, 2017 at 9:30 AM, Manikumar <manikumar.re...@gmail.
KAFKA-3491, which has no "fix
version".
> Re-enable committing offsets in consumer's unsubscribe() when auto commit is
> enabled
>
>
> Key: KAFKA-4242
> URL:
[
https://issues.apache.org/jira/browse/KAFKA-4242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma updated KAFKA-4242:
---
Fix Version/s: (was: 0.10.2.0)
> Re-enable committing offsets in consumer's unsubscribe() w
us...@kafka.apache.org;users-unsubscr...@kafka.apache.org;
users_unsubscr...@kafka.apache.org;
dev@kafka.apache.org; dev-unsubscr...@kafka.apache.org;
dev_unsubscr...@kafka.apache.org
-Original Message-
From: Raj Tanneru [mailto:rtann...@fanatics.com]
Sent: Saturday, May 7, 2016 6:46 PM
Github user vahidhashemian closed the pull request at:
https://github.com/apache/kafka/pull/1363
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the
GitHub user vahidhashemian reopened a pull request:
https://github.com/apache/kafka/pull/1363
KAFKA-3664 (WIP): Commit offset of unsubscribed partitions of the new
consumer on a subscription change
When users are using group management, if they call consumer.subscribe() to
change
[
https://issues.apache.org/jira/browse/KAFKA-2686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15106501#comment-15106501
]
The Data Lorax commented on KAFKA-2686:
---
Sorry for the late response - but thanks!
> unsubscr
GitHub user hachikuji opened a pull request:
https://github.com/apache/kafka/pull/439
HOTFIX: unsubscribe does not clear user assignment properly
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/hachikuji/kafka unsubscribe-hotfix
Github user asfgit closed the pull request at:
https://github.com/apache/kafka/pull/439
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
<wangg...@gmail.com>
Date: 2015-10-22T19:05:50Z
v1
----
> unsubscribe() call leaves KafkaConsumer in invalid state for manual
> topic-partition assignment
> --
>
>
[
https://issues.apache.org/jira/browse/KAFKA-2686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guozhang Wang updated KAFKA-2686:
-
Reviewer: Jason Gustafson
> unsubscribe() call leaves KafkaConsumer in invalid state for man
[
https://issues.apache.org/jira/browse/KAFKA-2686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guozhang Wang reassigned KAFKA-2686:
Assignee: Guozhang Wang (was: Neha Narkhede)
> unsubscribe() call leaves KafkaConsu
://github.com/apache/kafka/pull/352]
> unsubscribe() call leaves KafkaConsumer in invalid state for manual
> topic-partition assignment
> --
>
> Key: KAFKA-2686
>
://github.com/apache/kafka/pull/352
> unsubscribe() call leaves KafkaConsumer in invalid state for manual
> topic-partition assignment
> --
>
> Key: KAFKA-2686
>
[
https://issues.apache.org/jira/browse/KAFKA-2686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
The Data Lorax updated KAFKA-2686:
--
Description:
The bellow code snippet demonstrated the problem.
Basically, the unsubscribe
The Data Lorax created KAFKA-2686:
-
Summary: unsubscribe() call leaves KafkaConsumer in invalid state
for manual topic-partition assignment
Key: KAFKA-2686
URL: https://issues.apache.org/jira/browse/KAFKA-2686
at:
https://github.com/apache/kafka/pull/139
subscribe(topic)/unsubscribe(topic) should either take a callback to allow
user to handle exceptions or it should be synchronous
://github.com/apache/kafka/pull/139]
subscribe(topic)/unsubscribe(topic) should either take a callback to allow
user to handle exceptions or it should be synchronous
to address your comments. I'm thinking
maybe we punt on onError for now so we can get this into trunk. We can always
add that in a separate patch after we've defined it a little better. What do
you think?
subscribe(topic)/unsubscribe(topic) should either take a callback to allow
user to handle
at the patch later today.
subscribe(topic)/unsubscribe(topic) should either take a callback to allow
user to handle exceptions or it should be synchronous
(topic)/unsubscribe(topic) should either take a callback to allow
user to handle exceptions or it should be synchronous.
-
Key: KAFKA-2388
at it later today.
subscribe(topic)/unsubscribe(topic) should either take a callback to allow
user to handle exceptions or it should be synchronous.
-
Key
for this. Want to check it out and see
if we're on the same page. I haven't added onError to that callback yet.
subscribe(topic)/unsubscribe(topic) should either take a callback to allow
user to handle exceptions or it should be synchronous
...@confluent.io
Date: 2015-08-14T20:16:25Z
KAFKA-2388 [WIP]; refactor KafkaConsumer subscribe API
subscribe(topic)/unsubscribe(topic) should either take a callback to allow
user to handle exceptions or it should be synchronous
[
https://issues.apache.org/jira/browse/KAFKA-2388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Gustafson reassigned KAFKA-2388:
--
Assignee: Jason Gustafson (was: Onur Karaman)
subscribe(topic)/unsubscribe(topic
[
https://issues.apache.org/jira/browse/KAFKA-2388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on KAFKA-2388 started by Jason Gustafson.
--
subscribe(topic)/unsubscribe(topic) should either take a callback to allow
to get started on this? If you don't have
time, I can help out.
subscribe(topic)/unsubscribe(topic) should either take a callback to allow
user to handle exceptions or it should be synchronous
from assignments. This is something that should
definitely happen.
2. Introduce an onError callback to subscribe(). This one is less clear to me.
Regardless of what we decide here, we definitely need documentation of
exceptions in KafkaConsumer.
subscribe(topic)/unsubscribe(topic) should either
at it. If I can't get a patch together pretty
quickly, I'll send it back to you. Perhaps instead of the generic onError, we
handle just the specific case of the topic not existing (for example:
onUnknownTopic())? Are there any other relevant error cases?
subscribe(topic)/unsubscribe(topic) should either
take a crack at this. No worries if you
were planning to do it.
subscribe(topic)/unsubscribe(topic) should either take a callback to allow
user to handle exceptions or it should be synchronous
[
https://issues.apache.org/jira/browse/KAFKA-2388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dong Lin updated KAFKA-2388:
Assignee: Onur Karaman (was: Jiangjie Qin)
subscribe(topic)/unsubscribe(topic) should either take
on it but I assigned it
to [~becket_qin] by mistake.
subscribe(topic)/unsubscribe(topic) should either take a callback to allow
user to handle exceptions or it should be synchronous
(topic)/unsubscribe(topic) should either take a callback to allow
user to handle exceptions or it should be synchronous.
-
Key: KAFKA-2388
}
void subscribe(ListString topics, RebalanceCallback callback);
void assign(ListTopicPartition partitions);
ListString subscriptions();
ListTopicPartition assignments();
{code}
We don't need the unsubscribe APIs anymore.
The RebalanceCallback would look like:
{code}
interface RebalanceCallback
subscribe(ListString topic, RebalanceCallback callback);
void assign(Listpartition partitions);
ListString subscriptions();
ListTopic assignments();
We don't need unsubscribe anymore.
The RebalanceCallback will have one more following method:
void onError(Exception e);
was:
Currently subscribe
();
ListTopicPartition assignments();
{code}
We don't need the unsubscribe APIs anymore.
The RebalanceCallback would look like:
{code}
interface RebalanceCallback {
void onAssignment(ListTopicPartition partitions);
void onRevocation(ListTopicPartition partitions);
// handle non-existing topics, etc
();
ListTopicPartition assignments();
{code}
We don't need the unsubscribe APIs anymore.
The RebalanceCallback would look like:
{code}
interface RebalanceCallback {
void onAssignment(ListTopicPartition partitions);
void onRevocation(ListTopicPartition partitions);
// handle non-existing topics, etc
Jiangjie Qin created KAFKA-2388:
---
Summary: subscribe(topic)/unsubscribe(topic) should either take a
callback to allow user to handle exceptions or it should be synchronous.
Key: KAFKA-2388
URL: https
[
https://issues.apache.org/jira/browse/KAFKA-2388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dong Lin reassigned KAFKA-2388:
---
Assignee: Dong Lin
subscribe(topic)/unsubscribe(topic) should either take a callback to allow
I've tried sending an email to:
kafka-dev-unsubscr...@incubator.apache.org
kafka-dev-unsubscr...@kafka.apache.org
No luck.
any ideas?
thanks,
/m
56 matches
Mail list logo
