Chia-Ping Tsai created KAFKA-19300:
--
Summary: AsyncConsumer#unsubscribe always timeout due to
GroupAuthorizationException
Key: KAFKA-19300
URL: https://issues.apache.org/jira/browse/KAFKA-19300
Bruno Cadonna created KAFKA-19124:
-
Summary: Calling unsubscribe() on the consumer leads always to a
timeout
Key: KAFKA-19124
URL: https://issues.apache.org/jira/browse/KAFKA-19124
Project: Kafka
mer#unsubscribe swallow TopicAuthorizationException
> --
>
> Key: KAFKA-17648
> URL: https://issues.apache.org/jira/browse/KAFKA-17648
> Project: Kafka
> Issue Type: Task
[
https://issues.apache.org/jira/browse/KAFKA-17648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
PoAn Yang resolved KAFKA-17648.
---
Resolution: Duplicate
> AsyncKafkaConsumer#unsubscribe swallow TopicAuthorizationExcept
PoAn Yang created KAFKA-17648:
-
Summary: AsyncKafkaConsumer#unsubscribe swallow
TopicAuthorizationException
Key: KAFKA-17648
URL: https://issues.apache.org/jira/browse/KAFKA-17648
Project: Kafka
[
https://issues.apache.org/jira/browse/KAFKA-17581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lianet Magrans resolved KAFKA-17581.
Resolution: Fixed
> AsyncKafkaConsumer can't unsubscribe invali
PoAn Yang created KAFKA-17581:
-
Summary: AsyncKafkaConsumer can't unsubscribe invalid topics
Key: KAFKA-17581
URL: https://issues.apache.org/jira/browse/KAFKA-17581
Project: Kafka
Issue
in AsyncKafkaConsumer#unsubscribe
>
>
> Key: KAFKA-17377
> URL: https://issues.apache.org/jira/browse/KAFKA-17377
> Project: Kafka
> Issue Type: Improvement
>
PoAn Yang created KAFKA-17377:
-
Summary: Consider using defaultApiTimeoutMs in
AsyncKafkaConsumer#unsubscribe
Key: KAFKA-17377
URL: https://issues.apache.org/jira/browse/KAFKA-17377
Project: Kafka
[
https://issues.apache.org/jira/browse/KAFKA-17017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chia-Ping Tsai resolved KAFKA-17017.
Fix Version/s: 3.9.0
Resolution: Fixed
> AsyncConsumer#unsubscribe does not cl
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
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
give 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 notificatio
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, cu
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
wrote:
> Hi all,
>
e this depends on KAFKA-3491, which has no "fix
version".
> Re-enable committing offsets in consumer's unsubscribe() when auto commit is
> enabled
>
>
>
[
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 unsubscrib
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
To
uest at:
https://github.com/apache/kafka/pull/1944
> Consumer should not commit offsets in unsubscribe()
> ---
>
> Key: KAFKA-4234
> URL: https://issues.apache.org/jira/browse/KAFKA-4234
>
request 1944
[https://github.com/apache/kafka/pull/1944]
> Consumer should not commit offsets in unsubscribe()
> ---
>
> Key: KAFKA-4234
> URL: https://issues.apache.org/jira/browse/KAFKA-4234
>
Vahid Hashemian created KAFKA-4242:
--
Summary: Re-enable committing offsets in consumer's unsubscribe()
when auto commit is enabled
Key: KAFKA-4242
URL: https://issues.apache.org/jira/browse/KAFKA
[
https://issues.apache.org/jira/browse/KAFKA-4234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Gustafson updated KAFKA-4234:
---
Status: Patch Available (was: Open)
> Consumer should not commit offsets in unsubscr
pull request:
https://github.com/apache/kafka/pull/1944
KAFKA-4234: Temporarily disable committing offsets in consumer's
`unsubscribe()`
Temporarily disable the offset commit (when auto commit is enabled) in the
new consumer's `unsubscribe()` method towards a workaround
e to somehow preserve the offset(s) before the
last {{poll}} so that if issues occurred after the {{poll}} we are able to
reset (or {{rewind}} as suggested in the other thread) without having to
perform an {{unsubscribe}}. But as you suggested, we can think more about this
during the next release c
[
https://issues.apache.org/jira/browse/KAFKA-4234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vahid Hashemian reassigned KAFKA-4234:
--
Assignee: Vahid Hashemian
> Consumer should not commit offsets in unsubscr
us how to address the problem at the moment, I
think it would make sense to let the current workaround of calling
unsubscribe() continue to work as it has in previous releases. Otherwise users
have no way to abort if an exception occurs, which kind of limits the
usefulness of autocommit. In
s on
[KAFKA-3491|https://issues.apache.org/jira/browse/KAFKA-3491] and it seems
there is no consensus on which way to go. Has it been decided that calling
{{unsubscribe}} before {{close}} should be the workaround? If so, are we ok
with the issues that not committing offsets in {{unsubscribe}} will b
Jason Gustafson created KAFKA-4234:
--
Summary: Consumer should not commit offsets in unsubscribe()
Key: KAFKA-4234
URL: https://issues.apache.org/jira/browse/KAFKA-4234
Project: Kafka
Issue
you?
> Consumer should not commit offsets in unsubscribe()
> ---
>
> Key: KAFKA-4234
> URL: https://issues.apache.org/jira/browse/KAFKA-4234
> Project: Kafka
> Issue Type:
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 feature
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 t
anks!
> unsubscribe() call leaves KafkaConsumer in invalid state for manual
> topic-partition assignment
> --
>
> Key: KAFKA-2686
> URL: https://issues.apache
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 enabl
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
uest at:
https://github.com/apache/kafka/pull/352
> unsubscribe() call leaves KafkaConsumer in invalid state for manual
> topic-partition assignment
> --
>
>
://github.com/apache/kafka/pull/352]
> unsubscribe() call leaves KafkaConsumer in invalid state for manual
> topic-partition assignment
> --
>
> Key: KAFKA-2686
>
thor: Guozhang Wang
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 KafkaConsumer
[
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
uest 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 s
://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 synch
a look at the patch later today.
> subscribe(topic)/unsubscribe(topic) should either take a callback to allow
> user to handle exceptions or it should
patch 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 callba
same page.
> subscribe(topic)/unsubscribe(topic) should either take a callback to allow
> user to handle exceptions or it should be synchronous.
> -
>
>
a look at it later today.
> subscribe(topic)/unsubscribe(topic) should either take a callback to allow
> user to handle exceptions or it should
[
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 al
atch 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 s
[
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(to
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 s
hot 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)/uns
ions 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
e 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
too!
> subscribe(topic)/unsubscribe(topic) should either take a callback to allow
> user to handle exceptions or it should be synchronous.
> -
>
>
king 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 s
[
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 tak
nd, I can 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
[
https://issues.apache.org/jira/browse/KAFKA-2388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dong Lin updated KAFKA-2388:
Assignee: Jiangjie Qin (was: Dong Lin)
> subscribe(topic)/unsubscribe(topic) should either take a callb
d the unsubscribe APIs anymore.
The RebalanceCallback would look like:
{code}
interface RebalanceCallback {
void onAssignment(List partitions);
void onRevocation(List partitions);
// handle non-existing topics, etc.
void onError(Exception e);
}
{code}
was:
According to the mailing
x27;t need the unsubscribe APIs anymore.
The RebalanceCallback would look like:
{code}
interface RebalanceCallback {
void onAssignment(List partitions);
void onRevocation(List partitions);
// handle non-existing topics, etc.
void onError(Exception e);
}
{code}
was:
According to the ma
}
void subscribe(List topics, RebalanceCallback callback);
void assign(List partitions);
List subscriptions();
List assignments();
{code}
We don't need the unsubscribe APIs anymore.
The RebalanceCallback would look like:
{code}
interface RebalanceCallback {
void onAssignment(List partitions);
subscribe(List topic, RebalanceCallback callback);
void assign(List partitions);
List subscriptions();
List assignments();
We don't need unsubscribe anymore.
The RebalanceCallback will have one more following method:
void onError(Exception e);
was:
Currently subscribe/unsubscribe at topic lev
[
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 al
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
Try dev-unsubscr...@kafka.apache.org
Thanks,
Jun
On Mon, Dec 3, 2012 at 8:03 PM, Marv Lush wrote:
> 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
>
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
79 matches
Mail list logo
