Re: [DISCUSS] KIP-32 - Add CreateTime and LogAppendTime to Kafka message

one more thing.. I wanted to clarify that I am not proposing stamping two time properties per message either. I think at this point we have a solution for "event time" (as described in Millwheel) at Li.. (it is in the event payload). So we just need a way to fix the log retention isssues and impr

Re: [DISCUSS] KIP-32 - Add CreateTime and LogAppendTime to Kafka message

This thread has gone rather long. So I might not be fully clear on everybody's positions. To make sure I understand the possible proposals. Here is a concrete and 'must have' scenario for LinkedIn. We want to bootstrap from say a Database dump (espresso) into a kafka topic. (Databus bootstrap)

[jira] [Commented] (KAFKA-1686) Implement SASL/Kerberos

[ https://issues.apache.org/jira/browse/KAFKA-1686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14973752#comment-14973752 ] Jun Rao commented on KAFKA-1686: [~sriharsha], I was thinking what happens when a user is

[jira] [Commented] (KAFKA-2644) Run relevant ducktape tests with SASL_PLAINTEXT and SASL_SSL

[ https://issues.apache.org/jira/browse/KAFKA-2644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14973742#comment-14973742 ] Jun Rao commented on KAFKA-2644: [~rsivaram], we can start with the ducktape tests that yo

[jira] [Commented] (KAFKA-1686) Implement SASL/Kerberos

[ https://issues.apache.org/jira/browse/KAFKA-1686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14973566#comment-14973566 ] Sriharsha Chintalapani commented on KAFKA-1686: --- [~junrao] once the connecti

[jira] [Commented] (KAFKA-1686) Implement SASL/Kerberos

[ https://issues.apache.org/jira/browse/KAFKA-1686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14973551#comment-14973551 ] Jun Rao commented on KAFKA-1686: [~sriharsha], you mentioned that if the Kerberos tickets

[DISCUSS] KIP-40 - Extend GroupMetadata request to return group and member status

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, b

[jira] [Commented] (KAFKA-2644) Run relevant ducktape tests with SASL_PLAINTEXT and SASL_SSL

[ https://issues.apache.org/jira/browse/KAFKA-2644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14973474#comment-14973474 ] Ewen Cheslack-Postava commented on KAFKA-2644: -- [~rsivaram] Having tests is b

[jira] [Commented] (KAFKA-2642) Run replication tests in ducktape with SSL for clients

[ https://issues.apache.org/jira/browse/KAFKA-2642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14973466#comment-14973466 ] Rajini Sivaram commented on KAFKA-2642: --- Will do this under KAFKA-2644 along with th

[jira] [Updated] (KAFKA-2680) Zookeeper SASL check prevents any SASL code being run with IBM JDK

[ 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 wit

[jira] [Commented] (KAFKA-2680) Zookeeper SASL check prevents any SASL code being run with IBM JDK

[ https://issues.apache.org/jira/browse/KAFKA-2680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14973437#comment-14973437 ] ASF GitHub Bot commented on KAFKA-2680: --- GitHub user rajinisivaram opened a pull req

[GitHub] kafka pull request: KAFKA-2680: Use IBM ConfigFile class to load j...

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 m

[jira] [Updated] (KAFKA-2460) Fix capitalization in SSL classes

[ 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 > - > >

[jira] [Commented] (KAFKA-2675) SASL/Kerberos follow-up

[ https://issues.apache.org/jira/browse/KAFKA-2675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14973366#comment-14973366 ] Ismael Juma commented on KAFKA-2675: [~harsha_ch], I had a look at implementing SASL_K

Re: Java high level consumer providing duplicate messages when auto commit is off

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.

[jira] [Commented] (KAFKA-2644) Run relevant ducktape tests with SASL_PLAINTEXT and SASL_SSL

[ https://issues.apache.org/jira/browse/KAFKA-2644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14973191#comment-14973191 ] Ismael Juma commented on KAFKA-2644: I'm OK with that, but let's see what Jun says. >

[jira] [Commented] (KAFKA-2644) Run relevant ducktape tests with SASL_PLAINTEXT and SASL_SSL

[ https://issues.apache.org/jira/browse/KAFKA-2644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14973164#comment-14973164 ] Rajini Sivaram commented on KAFKA-2644: --- [~junrao] [~ijuma] [~harsha_ch] [~ewencp]