[
https://issues.apache.org/jira/browse/KAFKA-2644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14973164#comment-14973164
]
Rajini Sivaram commented on KAFKA-2644:
---
[~junrao] [~ijuma] [~harsha_ch] [~ewencp] I had made the
[
https://issues.apache.org/jira/browse/KAFKA-2644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14973474#comment-14973474
]
Ewen Cheslack-Postava commented on KAFKA-2644:
--
[~rsivaram] Having tests is better than not
[
https://issues.apache.org/jira/browse/KAFKA-2642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14973466#comment-14973466
]
Rajini Sivaram commented on KAFKA-2642:
---
Will do this under KAFKA-2644 along with the SASL tests.
>
Hi Kafka Devs,
Currently, the new consumer provides no way to view a group's status except
by inspecting coordinator and consumer logs. This includes listing the
members of the group and their partition assignments. For the old consumer,
tools could read this information directly from Zookeeper,
[
https://issues.apache.org/jira/browse/KAFKA-1686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14973551#comment-14973551
]
Jun Rao commented on KAFKA-1686:
[~sriharsha], you mentioned that if the Kerberos tickets can't be
[
https://issues.apache.org/jira/browse/KAFKA-1686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14973566#comment-14973566
]
Sriharsha Chintalapani commented on KAFKA-1686:
---
[~junrao] once the connection is
[
https://issues.apache.org/jira/browse/KAFKA-2644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14973742#comment-14973742
]
Jun Rao commented on KAFKA-2644:
[~rsivaram], we can start with the ducktape tests that you have with
[
https://issues.apache.org/jira/browse/KAFKA-1686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14973752#comment-14973752
]
Jun Rao commented on KAFKA-1686:
[~sriharsha], I was thinking what happens when a user is removed from KDC
I was reflecting on this more and I think there is a change or two that
should be considered for kafka.
First off, auto-commit is a very resilient mode. Drops in zookeeper
sessions due to garbage collection, network, rebalance or other
interference are handled gracefully within the kafka client.
[
https://issues.apache.org/jira/browse/KAFKA-2680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14973437#comment-14973437
]
ASF GitHub Bot commented on KAFKA-2680:
---
GitHub user rajinisivaram opened a pull request:
GitHub user rajinisivaram opened a pull request:
https://github.com/apache/kafka/pull/357
KAFKA-2680: Use IBM ConfigFile class to load jaas config if IBM JDK
Use IBM ConfigFile class with IBM JDK since JavaLoginConfig provided by SUN
provider is not included with IBM JDK.
You can
[
https://issues.apache.org/jira/browse/KAFKA-2680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajini Sivaram updated KAFKA-2680:
--
Status: Patch Available (was: Open)
> Zookeeper SASL check prevents any SASL code being run
[
https://issues.apache.org/jira/browse/KAFKA-2675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14973366#comment-14973366
]
Ismael Juma commented on KAFKA-2675:
[~harsha_ch], I had a look at implementing SASL_KAFA_SERVER_REALM
[
https://issues.apache.org/jira/browse/KAFKA-2460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma updated KAFKA-2460:
---
Fix Version/s: 0.9.0.0
> Fix capitalization in SSL classes
> -
>
>
14 matches
Mail list logo