[
https://issues.apache.org/jira/browse/KAFKA-4821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-4821.
--
Resolution: Invalid
> 9244L
> -
>
> Key: KAFKA-4821
>
[
https://issues.apache.org/jira/browse/KAFKA-4865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-4865.
--
Resolution: Invalid
> 2X8BF
> -
>
> Key: KAFKA-4865
>
[
https://issues.apache.org/jira/browse/KAFKA-4847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-4847.
--
Resolution: Invalid
> 1Y30J
> -
>
> Key: KAFKA-4847
>
[
https://issues.apache.org/jira/browse/KAFKA-4889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-4889.
--
Resolution: Invalid
> 2G8lc
> -
>
> Key: KAFKA-4889
>
[
https://issues.apache.org/jira/browse/KAFKA-4951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-4951.
--
Resolution: Fixed
This scenario is handled in the Idempotent producer (KIP-98) released in Kafka
[
https://issues.apache.org/jira/browse/KAFKA-3087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-3087.
--
Resolution: Fixed
This doc issue was fixed in newer Kafka versions.
> Fix documentation
[
https://issues.apache.org/jira/browse/KAFKA-2283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-2283.
--
Resolution: Fixed
> scheduler exception on non-controller node when shutd
[
https://issues.apache.org/jira/browse/KAFKA-2220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-2220.
--
Resolution: Fixed
This got fixed in KAFKA-4743 / KIP-122.
> Improvement: Could we support rewind
[
https://issues.apache.org/jira/browse/KAFKA-1832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-1832.
--
Resolution: Fixed
Fixed in KAFKA-1041
> Async Producer will cause 'java.net.SocketException:
[
https://issues.apache.org/jira/browse/KAFKA-1821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-1821.
--
Resolution: Fixed
It is working in newer Kafka versions.
> Example shell scripts bro
+1 (non-binding)
On Fri, Aug 11, 2017 at 8:09 PM, Mickael Maison
wrote:
> +1 non-binding, thanks Vahid
>
> On Wed, Aug 9, 2017 at 9:31 PM, Jason Gustafson
> wrote:
> > Thanks for the KIP. +1
> >
> > On Thu, Jul 27, 2017 at 2:04 PM, Vahid S Hashemian <
> > vahidhashem...@us.ibm.com> wrote:
> >
>
+1 (non-binding)
On Fri, Aug 11, 2017 at 5:31 AM, Jun Rao wrote:
> Hi, Vahid,
>
> Thanks for the KIP. +1 from me.
>
> Jun
>
> On Wed, Aug 2, 2017 at 2:40 PM, Vahid S Hashemian <
> vahidhashem...@us.ibm.com
> > wrote:
>
> > Hi all,
> >
> > Thanks to everyone who participated in the discussion on
[
https://issues.apache.org/jira/browse/KAFKA-3389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-3389.
--
Resolution: Won't Fix
As mentioned in the previous comment, this may not be an issue. Pl reop
check here:
https://github.com/apache/kafka/blob/trunk/clients/src/main/java/org/apache/kafka/common/security/ssl/SslFactory.java#L84
On Thu, Aug 10, 2017 at 3:49 AM, M. Manna wrote:
> Hello,
>
> I have been trying to find the usage of this property within Kafka source.
> All I am trying to unde
Manikumar created KAFKA-5644:
Summary: Transient test failure:
ResetConsumerGroupOffsetTest.testResetOffsetsToZonedDateTime
Key: KAFKA-5644
URL: https://issues.apache.org/jira/browse/KAFKA-5644
Project
[
https://issues.apache.org/jira/browse/KAFKA-2651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16015313#comment-16015313
]
Manikumar commented on KAFKA-2651:
--
[~ijuma] We have deprecated the alter confi
+1 (non-binding)
Verified artifacts and quick start
On Mon, Apr 17, 2017 at 8:05 PM, Mathieu Fenniak <
mathieu.fenn...@replicon.com> wrote:
> +1 (non-binding)
>
> Upgraded KS & KC applications to 0.10.2.1 RC1, successfully ran
> application-level acceptance tests.
>
> Mathieu
>
>
> On Wed, Apr 1
[
https://issues.apache.org/jira/browse/KAFKA-1516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-1516.
--
Resolution: Fixed
Resolving this as support for passing custom message payloads is given in
KAFKA
Hi,
java producer waits for the metadata of the given topic to be available. We
will get
TimeoutException if we didn't get metadata within max.block.ms. As observed
by you, this
behavior is different from old producer. "retries" config is not
applicable to metadata fetch.
We can adjust max.block.
[
https://issues.apache.org/jira/browse/KAFKA-3990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-3990.
--
Resolution: Duplicate
> Kafka New Producer may raise an OutOfMemoryEr
[
https://issues.apache.org/jira/browse/KAFKA-3391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-3391.
--
Resolution: Not A Problem
Please reopen if the issue still exists.
> Kafka to ZK time
[
https://issues.apache.org/jira/browse/KAFKA-1436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-1436.
--
Resolution: Duplicate
> Idempotent Producer / Duplicate Detect
[
https://issues.apache.org/jira/browse/KAFKA-639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-639.
-
Resolution: Duplicate
> RESTful proxy
> -
>
> Ke
[
https://issues.apache.org/jira/browse/KAFKA-4807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-4807.
--
Resolution: Duplicate
> Kafka broker fail over bug in zookee
[
https://issues.apache.org/jira/browse/KAFKA-4864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar closed KAFKA-4864.
> Kafka Secure Migrator tool doesn't secure all t
[
https://issues.apache.org/jira/browse/KAFKA-4795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15894178#comment-15894178
]
Manikumar edited comment on KAFKA-4795 at 3/3/17 11:2
[
https://issues.apache.org/jira/browse/KAFKA-4795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15894178#comment-15894178
]
Manikumar commented on KAFKA-4795:
--
[~vahid] If we disable topic deletion the
[
https://issues.apache.org/jira/browse/KAFKA-4807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15894097#comment-15894097
]
Manikumar commented on KAFKA-4807:
--
This is related to KAFKA-
[
https://issues.apache.org/jira/browse/KAFKA-4788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15880385#comment-15880385
]
Manikumar edited comment on KAFKA-4788 at 2/23/17 1:0
[
https://issues.apache.org/jira/browse/KAFKA-4788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15880385#comment-15880385
]
Manikumar commented on KAFKA-4788:
--
[~ijuma] While using kafka-topics.sh, we are d
[
https://issues.apache.org/jira/browse/KAFKA-4788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15880281#comment-15880281
]
Manikumar commented on KAFKA-4788:
--
looks like KAFKA-4092 change introduced this i
.com
> > > > > > wrote:
> > > > >
> > > > > > Hi Jun,
> > > > > >
> > > > > > Sure sounds good to me.
> > > > > >
> > > > > > Thanks,
> > > > > >
> > &g
s a discussion how kafka-acls.sh would
> > work with this change, on the ticket, we designed a detailed solution to
> > make this tool generally usable with all sorts of combinations of
> > Authorizers and PrincipalBuilders and give more flexibility to the end
> > users.
>
Sorry, I am late to this discussion.
PrincipalBuilder is only used for SSL Protocol.
For SASL, we use "sasl.kerberos.principal.to.local.rules" config to map
SASL principal names to short names. To make it consistent,
Do we also need to pass the SASL full principal name to authorizer ?
We may need
[
https://issues.apache.org/jira/browse/KAFKA-4542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar Reddy reassigned KAFKA-4542:
--
Assignee: Manikumar Reddy
> Add authentication based on delegation to
Thank you all for your votes and feedback.
The vote has passed with 4 binding votes(Gwen, Jun, Grant, Harsha) and 2
non-binding votes(Roger, Dong Lin).
I have updated the relevant wiki pages.
Thanks
Manikumar
On Tue, Feb 14, 2017 at 12:02 AM, Dong Lin wrote:
> +1 (non-binding)
>
&g
[
https://issues.apache.org/jira/browse/KAFKA-3531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar Reddy resolved KAFKA-3531.
Resolution: Duplicate
Assignee: (was: Parth Brahmbhatt)
Resolving this as
Yes, owners and the renewers can always describe their own tokens. Updated
the KIP.
On Sat, Feb 11, 2017 at 3:12 AM, Jun Rao wrote:
> Hi, Mani,
>
> Thanks for the update. Just a minor comment below. Otherwise, +1 from me.
>
>
> >
> > >
> > > 116. Could you document the ACL rules associated with
e extend
the support to allow a user to acquire delegation tokens for other users,
then we can enable
CREATE/DELETE operations. Updated the KIP.
Thanks,
Manikumar
> On Wed, Feb 8, 2017 at 1:35 AM, Manikumar
> wrote:
>
> > Hi Jun,
> >
> >
> > > If a token expir
[
https://issues.apache.org/jira/browse/KAFKA-4076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar Reddy resolved KAFKA-4076.
Resolution: Invalid
Pl reopen the issue, if still exists.
> Kafka broker shuts down
[
https://issues.apache.org/jira/browse/KAFKA-4751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15859568#comment-15859568
]
Manikumar Reddy commented on KAFKA-4751:
It is a known issue. Related JIR
e same time, but only one will succeed. So, we will have to
> deal
> > > with failures in that case? Another way is to let just one broker (say,
> > the
> > > controller) deletes expired tokens.
> > >
> > > It would also be helpful for others to give fee
thread for impersonation related discussion.
Thanks,
Manikumar
On Wed, Feb 8, 2017 at 8:37 AM, Roger Hoover wrote:
> Hi Jun,
>
> How does it allow impersonation at the connection level? Looking at the
> KIP, the DelegationTokenRequest does not have an "Owner" field that can
Agree, we can run the token expiry check thread as part of controller
broker.
WIll update the KIP.
Thanks,
Manikumar
>
> On Sun, Feb 5, 2017 at 9:54 AM, Manikumar
> wrote:
>
> > Hi Jun,
> >
> > Please see the replies inline.
> >
> >
> >
+1 for ismael's suggestion. grouping of methods by the relevant resource
will simply the
API. In future, we will be adding delegation token related operations to
admin client.
I can imagine methods like adminClient.token().create(...),
adminClient.token().renew(...), etc..
Thanks,
Manikuma
uthentication time.
>
>
> 110. The diagrams in the wiki still show MD5 digest. Could you change it to
> SCRAM?
>
>
Updated the diagram.
Thanks,
Manikumar
>
>
> >
> > Thanks.
> > Manikumar
> >
> >
> > >
> > > On Fri, Dec
[
https://issues.apache.org/jira/browse/KAFKA-4541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15837319#comment-15837319
]
Manikumar Reddy commented on KAFKA-4541:
[~singhashish] Can you post your WI
update the terminology
tokenUID => tokenID.
> 107.3 How does each broker know about changes in tokens? Does each broker
> register a watcher for /tokenauth/tokens?
>
Yes, the changes are updated through zk notifications.
> 107.4 How is token deletion handled? Does every broker delet
Hi,
I would like to initiate the vote on KIP-48:
https://cwiki.apache.org/confluence/display/KAFKA/KIP-48+
Delegation+token+support+for+Kafka
Thanks,
Manikumar
Hi Devs,
If there are no more comments, I will start vote on this KIP later this
week.
Thanks
On Fri, Dec 16, 2016 at 12:28 PM, Manikumar
wrote:
> Hi,
>
>
>> Can you add a sample Jaas configuration using delegation tokens to the
>> KIP?
>>
>
> Will add sam
ve any suggestions/concerns on this KIP.
Thanks,
>
> On Thu, Dec 15, 2016 at 9:04 AM, Manikumar
> wrote:
>
> > @Gwen, @Rajini,
> >
> > As mentioned in the KIP, main motivation for this KIP is to reduce load
> on
> > Kerberos
> > server on large k
[
https://issues.apache.org/jira/browse/KAFKA-1696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15751936#comment-15751936
]
Manikumar Reddy commented on KAFKA-1696:
Thanks for creating sub-tasks. A
[
https://issues.apache.org/jira/browse/KAFKA-4541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15751744#comment-15751744
]
Manikumar Reddy commented on KAFKA-4541:
[~singhashish] Is this JIRA
[
https://issues.apache.org/jira/browse/KAFKA-4543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar Reddy reassigned KAFKA-4543:
--
Assignee: Manikumar Reddy
> Add capability to renew/expire delegation tok
s password for authentication and tokenID for retrial of tokenHmac at
server side.
Does above sound OK?
Thanks,
Manikumar
On Wed, Dec 14, 2016 at 10:33 PM, Harsha Chintalapani
wrote:
> @Gwen @Mani Not sure why we want to authenticate at every request. Even if
> the token exchange is chea
onnect, NiFi and friends can probably use this to share clients
> between multiple jobs, tasks, etc.
>
> What do you think?
>
> Gwen
>
> On Tue, Dec 13, 2016 at 12:43 AM, Manikumar
> wrote:
>
> > Ashish,
> >
> > Thank you for reviewing the KIP. Please see th
[
https://issues.apache.org/jira/browse/KAFKA-1696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15747403#comment-15747403
]
Manikumar Reddy commented on KAFKA-1696:
[~singhashish] Yes, Pl go ahead
allow users to renew a token for a specified amount of time? In
> current version of KIP, renew request does not take time as a param, not
> sure what is expiry time set to after renewal.
>
>
Yes, we need to specify renew period. I'll update the KIP.
Thanks,
Mankumar
[
https://issues.apache.org/jira/browse/KAFKA-1696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15742486#comment-15742486
]
Manikumar Reddy commented on KAFKA-1696:
.[~singhashish] Sorry for the late r
+Delegation+token+support+for+Kafka
Jun, Ashish, Gwen,
Pl review the updated KIP.
Thanks
Manikumar
On Thu, Sep 29, 2016 at 9:56 PM, Ashish Singh wrote:
> Harsha/ Gwen,
>
> How do we proceed here? I am willing to help out with here.
>
> On Fri, Sep 23, 2016 at 11:41 AM, Gwen
The default principal for Plaintext transport is "ANONYMOUS".
On Sun, Dec 11, 2016 at 12:58 AM, BigData dev
wrote:
> Hi,
>
> bin/kafka-acls.sh --topic kafka-testtopic --add -allow-host 9.30.15.19
> --operation Write --authorizer-properties
> zookeeper.connect=hostname.abc.com:2181
>
> Below mes
s for raising valid queries and helping me to improve the KIP
details.
I will discuss some of your notes (new consumer API, HTTP/2, multi-REST-proxy
etc) at
kafka-rest project issues page .
Thanks you all for participating in this discussion.
Thanks,
Manikumar
On Wed, Oct 26, 2016 at 11:
fka/0.10.1.0/k
> > > > > > afka_2.11-0.10.1.0.tgz
> > > > > > https://www.apache.org/dyn/closer.cgi?path=/kafka/0.10.1.0/k
> > > > > > afka_2.10-0.10.1.0.tgz
> > > > > >
> > > > > > Thanks to the 115 cont
+1 (non-binding)
verified quick start and artifacts.
On Sat, Oct 15, 2016 at 4:59 AM, Jason Gustafson wrote:
> Hello Kafka users, developers and client-developers,
>
> One more RC for 0.10.1.0. We're hoping this is the final one so that we
> can meet the release target date of Oct. 17 (Monday).
number
of distributions/builds.
Thanks,
Manikumar
On Sat, Oct 1, 2016 at 4:24 AM, Jay Kreps wrote:
> Hey guys,
>
> There's already a REST interface maintained as a separate project--it's
> open source and apache licensed and actively maintained (
> https://github.com/conf
[
https://issues.apache.org/jira/browse/KAFKA-4074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15528682#comment-15528682
]
Manikumar Reddy commented on KAFKA-4074:
[~hachikuji] Yes, resolving thi
[
https://issues.apache.org/jira/browse/KAFKA-4074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar Reddy resolved KAFKA-4074.
Resolution: Duplicate
> Deleting a topic can make it unavailable even
://cwiki.apache.org/confluence/display/KAFKA/KIP-
80%3A+Kafka+Rest+Server
Your comments and feedback are welcome.
Thanks,
Manikumar
[
https://issues.apache.org/jira/browse/KAFKA-4164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15495450#comment-15495450
]
Manikumar Reddy commented on KAFKA-4164:
This is a valid concern. Curre
[
https://issues.apache.org/jira/browse/KAFKA-4126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar Reddy updated KAFKA-4126:
---
Comment: was deleted
(was: Yes. Another issue related to producer excessive warn logging is
[
https://issues.apache.org/jira/browse/KAFKA-4126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15495420#comment-15495420
]
Manikumar Reddy commented on KAFKA-4126:
Yes. Another issue related to prod
[
https://issues.apache.org/jira/browse/KAFKA-4126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15495422#comment-15495422
]
Manikumar Reddy commented on KAFKA-4126:
Yes. Another issue related to prod
[
https://issues.apache.org/jira/browse/KAFKA-2700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar Reddy reassigned KAFKA-2700:
--
Assignee: Manikumar Reddy (was: Parth Brahmbhatt)
> delete topic should remove
[
https://issues.apache.org/jira/browse/KAFKA-4072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar Reddy reassigned KAFKA-4072:
--
Assignee: Manikumar Reddy
> improving memory usage in LogClea
[
https://issues.apache.org/jira/browse/KAFKA-2700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15492770#comment-15492770
]
Manikumar Reddy commented on KAFKA-2700:
[~parth.brahmbhatt]], are you workin
[
https://issues.apache.org/jira/browse/KAFKA-4126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15490118#comment-15490118
]
Manikumar Reddy commented on KAFKA-4126:
[~vahid] I think, I tried by disab
adding missing classifier parameter..
org.apache.kafka
kafka-streams
0.10.0.0
test-jar
test
On Tue, Sep 13, 2016 at 12:07 PM, Manikumar Reddy wrote:
> Hi,
>
> Kafka uses "test" as classifier (default is "tests" ) for test jars.
> We can add test paramete
Hi,
Kafka uses "test" as classifier (default is "tests" ) for test jars.
We can add test parameter to dependency tag to
resolve the error.
org.apache.kafka
kafka-streams
0.10.0.0
test-jar
test
Thanks
Ma
[
https://issues.apache.org/jira/browse/KAFKA-4074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15469613#comment-15469613
]
Manikumar Reddy commented on KAFKA-4074:
[~junrao] Yes, Both issues are same
[
https://issues.apache.org/jira/browse/KAFKA-4111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15469580#comment-15469580
]
Manikumar Reddy commented on KAFKA-4111:
Ok got it. Broker handles each prod
[
https://issues.apache.org/jira/browse/KAFKA-4111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15466584#comment-15466584
]
Manikumar Reddy commented on KAFKA-4111:
"compression.type"
[
https://issues.apache.org/jira/browse/KAFKA-4109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15466570#comment-15466570
]
Manikumar Reddy commented on KAFKA-4109:
Enable producer debug logs to get
[
https://issues.apache.org/jira/browse/KAFKA-4126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15466496#comment-15466496
]
Manikumar Reddy commented on KAFKA-4126:
Currently producer logs below
We don't need JIRA for minor PRs. Just prefix "MINOR:" to PR title.
On Tue, Sep 6, 2016 at 9:16 AM, Jaikiran Pai
wrote:
> Thanks Ismael, I'll raise a PR for this. As a process, is there a JIRA
> that's expected to be filed for this before I raise a PR or would this be
> OK without a JIRA?
>
> -J
[
https://issues.apache.org/jira/browse/KAFKA-4065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15436585#comment-15436585
]
Manikumar Reddy commented on KAFKA-4065:
Agree, currently new producer d
[
https://issues.apache.org/jira/browse/KAFKA-4074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar Reddy reassigned KAFKA-4074:
--
Assignee: Manikumar Reddy
> Deleting a topic can make it unavailable even
[
https://issues.apache.org/jira/browse/KAFKA-4065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15434215#comment-15434215
]
Manikumar Reddy commented on KAFKA-4065:
"compression.type" conf
[
https://issues.apache.org/jira/browse/KAFKA-3218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15432667#comment-15432667
]
Manikumar Reddy commented on KAFKA-3218:
[~ rajinisivaram]KAFKA-3680 f
[
https://issues.apache.org/jira/browse/KAFKA-4076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15432252#comment-15432252
]
Manikumar Reddy commented on KAFKA-4076:
You are storing kafka data logs to
[
https://issues.apache.org/jira/browse/KAFKA-3204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar Reddy resolved KAFKA-3204.
Resolution: Won't Fix
> ConsumerConnector blocked on Authenticated by SAS
+1 (non-binding)
This feature help us control memory footprint and allows consumer to
progress on fetching large messages.
On Fri, Aug 19, 2016 at 10:32 AM, Gwen Shapira wrote:
> +1 (binding)
>
> On Thu, Aug 18, 2016 at 1:47 PM, Andrey L. Neporada
> wrote:
> > Hi all!
> > I’ve modified KIP-74
[
https://issues.apache.org/jira/browse/KAFKA-4063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar Reddy resolved KAFKA-4063.
Resolution: Duplicate
> Add support for infinite endpoints for range queries in Ka
[
https://issues.apache.org/jira/browse/KAFKA-2199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar Reddy resolved KAFKA-2199.
Resolution: Fixed
> Make signing artifacts optional, setting maven repository possible f
During server/client startup, we are logging all the supplied configs. May
be we can just mask
the password related config values for both valid/invalid configs.
On Wed, Aug 17, 2016 at 5:14 PM, Jaikiran Pai
wrote:
> Any opinion about this proposed change?
>
> -Jaikiran
>
> On Tuesday 16 August
[
https://issues.apache.org/jira/browse/KAFKA-3980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15424315#comment-15424315
]
Manikumar Reddy edited comment on KAFKA-3980 at 8/17/16 11:2
[
https://issues.apache.org/jira/browse/KAFKA-3980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15424315#comment-15424315
]
Manikumar Reddy commented on KAFKA-3980:
as suspected, this may be relate
[
https://issues.apache.org/jira/browse/KAFKA-4035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar Reddy updated KAFKA-4035:
---
Resolution: Fixed
Fix Version/s: 0.10.1.0
Status: Resolved (was: Patch
[
https://issues.apache.org/jira/browse/KAFKA-3959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15419140#comment-15419140
]
Manikumar Reddy commented on KAFKA-3959:
Yes, min.insync.replicas applicabl
[
https://issues.apache.org/jira/browse/KAFKA-4012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar Reddy updated KAFKA-4012:
---
Status: Patch Available (was: Open)
> KerberosShortNamer should implement toStr
[
https://issues.apache.org/jira/browse/KAFKA-4035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar Reddy updated KAFKA-4035:
---
Affects Version/s: 0.9.0.0
0.10.0.0
0.10.0.1
901 - 1000 of 1828 matches
Mail list logo
