kafka-connector sink task flush() interval

Hi, Recently, I am working on kafka connector implement. According to the connector sink task document, the connect platform invoke flush method periodically, But the doc does not metition the flush interval. I don't know the flush interval default value or Where we can set this interval??

[jira] [Commented] (KAFKA-3042) updateIsr should stop after failed several times due to zkVersion issue

[ https://issues.apache.org/jira/browse/KAFKA-3042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15233288#comment-15233288 ] Robert Christ commented on KAFKA-3042: -- Hello again, We have managed to reproduce the problem and

[GitHub] kafka pull request: Kafka-3338 [Kafka Streams] Add print and write...

GitHub user bbejeck opened a pull request: https://github.com/apache/kafka/pull/1209 Kafka-3338 [Kafka Streams] Add print and writeAsText to KStream/KTable Addresses comments from previous PR [#1187] Changed print and writeAsText method return signature to void

[GitHub] kafka pull request: KAFKA-3338 [Kafka Streams] : Add print and wri...

Github user bbejeck closed the pull request at: https://github.com/apache/kafka/pull/1187 --- 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

[jira] [Commented] (KAFKA-3338) Add print and writeAsText functions to the Streams DSL

[ https://issues.apache.org/jira/browse/KAFKA-3338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15233246#comment-15233246 ] ASF GitHub Bot commented on KAFKA-3338: --- Github user bbejeck closed the pull request at:

[jira] [Commented] (KAFKA-3525) max.reserved.broker.id off-by-one error

[ https://issues.apache.org/jira/browse/KAFKA-3525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15233241#comment-15233241 ] Manikumar Reddy commented on KAFKA-3525: Yes, by looking this function alone it is possible. But,

[GitHub] kafka pull request: HOTFIX: special handling first ever triggered ...

GitHub user guozhangwang opened a pull request: https://github.com/apache/kafka/pull/1208 HOTFIX: special handling first ever triggered punctuate You can merge this pull request into a Git repository by running: $ git pull https://github.com/guozhangwang/kafka KPunctuate

Re: KStream Close Processor

Hi Michael, When you call KafkaStreams.close(), it will first trigger a commitAll() function, which will 1) flush local state store if necessary; 2) flush messages buffered in producer; 3) commit offsets on consumer. Then it will close the producer / consumer clients and shutdown the tasks. So

[jira] [Updated] (KAFKA-3534) Deserialize on demand when default time extractor used

[ https://issues.apache.org/jira/browse/KAFKA-3534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-3534: - Labels: performance (was: ) > Deserialize on demand when default time extractor used >

[jira] [Updated] (KAFKA-3534) Deserialize on demand when default time extractor used

[ https://issues.apache.org/jira/browse/KAFKA-3534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-3534: - Fix Version/s: 0.10.1.0 > Deserialize on demand when default time extractor used >

Re: [VOTE] KIP-4 Metadata Schema (Round 2)

+1 On Fri, Apr 8, 2016 at 2:41 PM, Grant Henke wrote: > I would like to re-initiate the voting process for the "KIP-4 Metadata > Schema changes". This is not a vote for all of KIP-4, but specifically for > the metadata changes. I have included the exact changes below for

[GitHub] kafka pull request: MINOR: Make VerifiableProducer in system tests...

GitHub user ewencp opened a pull request: https://github.com/apache/kafka/pull/1207 MINOR: Make VerifiableProducer in system tests lookup security configuration dynamically instead of at construction. You can merge this pull request into a Git repository by running: $ git

Re: [DISCUSS] KIP-35 - Retrieve protocol version

Magnus, A while back, we had another proposal for the broker to just send the correlation id and an empty payload if it receives an unsupported version of the request. I didn't see that in the rejected section. It seems simpler than the current proposal where the client has to issue an

Re: [DISCUSS] KIP-43: Kafka SASL enhancements

Hi, Magnus, You brought up a few things in your proposal. I am trying to itemize them below so that we can discuss them individually. 1. You are proposing moving the SASL authentication logic into the application and modeling it just as regular requests such as produce/fetch. The issue is that

[jira] [Commented] (KAFKA-3205) Error in I/O with host (java.io.EOFException) raised in producer

[ https://issues.apache.org/jira/browse/KAFKA-3205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15233021#comment-15233021 ] ASF GitHub Bot commented on KAFKA-3205: --- Github user bondj closed the pull request at:

[GitHub] kafka pull request: KAFKA-3205 Support passive close by broker

Github user bondj closed the pull request at: https://github.com/apache/kafka/pull/1166 --- 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

Build failed in Jenkins: kafka-trunk-jdk8 #515

See Changes: [me] KAFKA-3521: validate null keys in Streams DSL implementations -- [...truncated 884 lines...] kafka.server.LogOffsetTest > testGetOffsetsBeforeNow PASSED

Re: [VOTE] KIP-4 Metadata Schema (Round 2)

+1 (non-binding) On Fri, Apr 8, 2016 at 10:41 PM, Grant Henke wrote: > I would like to re-initiate the voting process for the "KIP-4 Metadata > Schema changes". This is not a vote for all of KIP-4, but specifically for > the metadata changes. I have included the exact

[VOTE] KIP-4 Metadata Schema (Round 2)

I would like to re-initiate the voting process for the "KIP-4 Metadata Schema changes". This is not a vote for all of KIP-4, but specifically for the metadata changes. I have included the exact changes below for clarity: > > Metadata Request (version 1) > > > > MetadataRequest => [topics] > >

[jira] [Commented] (KAFKA-3042) updateIsr should stop after failed several times due to zkVersion issue

[ https://issues.apache.org/jira/browse/KAFKA-3042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15233011#comment-15233011 ] Robert Christ commented on KAFKA-3042: -- Thanks Flavio and Jun for looking at this. We had bumped our

Build failed in Jenkins: kafka-trunk-jdk7 #1186

See Changes: [me] KAFKA-3528: handle wakeups while rebalancing more gracefully [me] KAFKA-3521: validate null keys in Streams DSL implementations -- [...truncated 5347 lines...]

Build failed in Jenkins: kafka-trunk-jdk8 #514

See Changes: [me] KAFKA-3528: handle wakeups while rebalancing more gracefully -- [...truncated 1629 lines...] kafka.log.LogTest > testTruncateTo PASSED kafka.log.LogTest >

[GitHub] kafka pull request: KAFKA-3521: validate null keys in Streams DSL ...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1197 --- 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

[jira] [Resolved] (KAFKA-3521) Better handling NPEs in Streams DSL implementation

[ https://issues.apache.org/jira/browse/KAFKA-3521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava resolved KAFKA-3521. -- Resolution: Fixed Fix Version/s: (was: 0.10.0.0)

[jira] [Commented] (KAFKA-3521) Better handling NPEs in Streams DSL implementation

[ https://issues.apache.org/jira/browse/KAFKA-3521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15232873#comment-15232873 ] ASF GitHub Bot commented on KAFKA-3521: --- Github user asfgit closed the pull request at:

[jira] [Commented] (KAFKA-3470) Consumer group coordinator should take commit requests as effective as heartbeats

[ https://issues.apache.org/jira/browse/KAFKA-3470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15232835#comment-15232835 ] ASF GitHub Bot commented on KAFKA-3470: --- GitHub user hachikuji opened a pull request:

[GitHub] kafka pull request: KAFKA-3470: treat commits as member heartbeats

GitHub user hachikuji opened a pull request: https://github.com/apache/kafka/pull/1206 KAFKA-3470: treat commits as member heartbeats You can merge this pull request into a Git repository by running: $ git pull https://github.com/hachikuji/kafka KAFKA-3470 Alternatively you

[jira] [Commented] (KAFKA-3528) AbstractCoordinator wakeup during rebalance can cause spurious rebalances

[ https://issues.apache.org/jira/browse/KAFKA-3528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15232821#comment-15232821 ] ASF GitHub Bot commented on KAFKA-3528: --- Github user asfgit closed the pull request at:

[jira] [Updated] (KAFKA-3528) AbstractCoordinator wakeup during rebalance can cause spurious rebalances

[ https://issues.apache.org/jira/browse/KAFKA-3528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-3528: - Resolution: Fixed Fix Version/s: 0.10.1.0 Status: Resolved

[GitHub] kafka pull request: KAFKA-3528: handle wakeups while rebalancing m...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1201 --- 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

Re: [VOTE] KIP-4 Metadata Schema

Hi Jun, I am looking at the changes required for the below request: 5. You will return no error and 4,5,6 as replicas. The response also > includes a list of live brokers. So the client can figure out 5 is not live > directly w/o relying on the error code. The challenge here is that I need to

[jira] [Commented] (KAFKA-3533) Kafka Consumer Config validation should be AND not OR

[ https://issues.apache.org/jira/browse/KAFKA-3533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15232801#comment-15232801 ] ASF GitHub Bot commented on KAFKA-3533: --- Github user rnpridgeon closed the pull request at:

[GitHub] kafka pull request: KAFKA-3533: Incorrect logic

Github user rnpridgeon closed the pull request at: https://github.com/apache/kafka/pull/1205 --- 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

[jira] [Assigned] (KAFKA-3530) Making the broker-list option consistent across all tools

[ https://issues.apache.org/jira/browse/KAFKA-3530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liquan Pei reassigned KAFKA-3530: - Assignee: Liquan Pei > Making the broker-list option consistent across all tools >

[jira] [Created] (KAFKA-3534) Deserialize on demand when default time extractor used

Michael Coon created KAFKA-3534: --- Summary: Deserialize on demand when default time extractor used Key: KAFKA-3534 URL: https://issues.apache.org/jira/browse/KAFKA-3534 Project: Kafka Issue

KStream Close Processor

All,    I'm seeing my processor's "close" method being called AFTER my downstream producer has been closed. I had assumed that on close I would be able to flush whatever I had been buffering up to send to kafka topic. In other words, we've seen significant performance differences in building

[jira] [Resolved] (KAFKA-3533) Kafka Consumer Config validation should be AND not OR

[ https://issues.apache.org/jira/browse/KAFKA-3533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryan P resolved KAFKA-3533. --- Resolution: Invalid Misinterpreted the intended purpose of this check. > Kafka Consumer Config validation

[jira] [Commented] (KAFKA-3525) max.reserved.broker.id off-by-one error

[ https://issues.apache.org/jira/browse/KAFKA-3525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15232703#comment-15232703 ] Alan Braithwaite commented on KAFKA-3525: - Please correct me if I'm wrong, but this looks like a

Build failed in Jenkins: kafka-trunk-jdk7 #1185

See Changes: [me] MINOR: improve logging of consumer system tests -- [...truncated 5347 lines...] org.apache.kafka.streams.kstream.internals.KTableMapValuesTest > testNotSendingOldValue

[jira] [Commented] (KAFKA-3533) Kafka Consumer Config validation should be AND not OR

[ https://issues.apache.org/jira/browse/KAFKA-3533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15232691#comment-15232691 ] ASF GitHub Bot commented on KAFKA-3533: --- GitHub user rnpridgeon opened a pull request:

[GitHub] kafka pull request: KAFKA-3533: Incorrect logic

GitHub user rnpridgeon opened a pull request: https://github.com/apache/kafka/pull/1205 KAFKA-3533: Incorrect logic Incorrect logic in Config Validation for KafkaConsumer.

Re: [VOTE] KIP-4 Metadata Schema

Guozhang, I agree there is a gap. Thats what I was trying to say in the last email. But I also, don't see a great/safe way to fix it by changing what topics are included in the metadata. Perhaps instead, I can add a special error code to the CreateTopic request to tell the user the topic they

[jira] [Commented] (KAFKA-1554) Corrupt index found on clean startup

[ https://issues.apache.org/jira/browse/KAFKA-1554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15232678#comment-15232678 ] Paul Baclace commented on KAFKA-1554: - So it is fixed in 0.9.0 with KAFKA-2012; I can confirm seeing

Build failed in Jenkins: kafka-trunk-jdk8 #513

See Changes: [wangguoz] KAFKA-725: Return OffsetOutOfRange error from ReplicaManager when [me] MINOR: improve logging of consumer system tests -- [...truncated 1636 lines...] kafka.log.LogTest

[jira] [Commented] (KAFKA-3470) Consumer group coordinator should take commit requests as effective as heartbeats

[ https://issues.apache.org/jira/browse/KAFKA-3470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15232663#comment-15232663 ] Jason Gustafson commented on KAFKA-3470: I think this makes sense. In some situations that I've

[jira] [Assigned] (KAFKA-3470) Consumer group coordinator should take commit requests as effective as heartbeats

[ https://issues.apache.org/jira/browse/KAFKA-3470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson reassigned KAFKA-3470: -- Assignee: Jason Gustafson > Consumer group coordinator should take commit requests as

[jira] [Commented] (KAFKA-3042) updateIsr should stop after failed several times due to zkVersion issue

[ https://issues.apache.org/jira/browse/KAFKA-3042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15232645#comment-15232645 ] Jun Rao commented on KAFKA-3042: [~delbaeth], [~wushujames], a few things. 1. Supposedly after step 5),

[jira] [Created] (KAFKA-3533) Kafka Consumer Config validation should be AND not OR

Ryan P created KAFKA-3533: - Summary: Kafka Consumer Config validation should be AND not OR Key: KAFKA-3533 URL: https://issues.apache.org/jira/browse/KAFKA-3533 Project: Kafka Issue Type: Bug

Re: [DISCUSS] KIP-43: Kafka SASL enhancements

I think we do need at least some capability to dynamically select mechanisms: Storm currently supports Kerberos. For various reasons they will need to support delegation tokens. In order to allow any Storm version to work with any Kafka versions, a new Storm will need to know whether it should

[jira] [Assigned] (KAFKA-3492) support quota based on authenticated user name

[ https://issues.apache.org/jira/browse/KAFKA-3492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram reassigned KAFKA-3492: - Assignee: Rajini Sivaram > support quota based on authenticated user name >

[jira] [Commented] (KAFKA-3492) support quota based on authenticated user name

[ https://issues.apache.org/jira/browse/KAFKA-3492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15232612#comment-15232612 ] Rajini Sivaram commented on KAFKA-3492: --- [~aauradkar] Thank you. > support quota based on

[jira] [Commented] (KAFKA-3408) consumer rebalance fail

[ https://issues.apache.org/jira/browse/KAFKA-3408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15232587#comment-15232587 ] Amey commented on KAFKA-3408: - How can I be a contributor and start working on this issue? > consumer

Re: [VOTE] KIP-4 Metadata Schema

I feel that "a delete and then create action may fail with a topic exists exception...which the user could retry until succeeded" has some flaw, since we cannot distinguish the case 1) the topic not marked for deleted, but deletion is not complete, from 2) the topic is being created, but creation

Build failed in Jenkins: kafka-trunk-jdk7 #1184

See Changes: [me] KAFKA-3505: Fix punctuate generated record metadata [wangguoz] KAFKA-3512: Added foreach operator [wangguoz] KAFKA-725: Return OffsetOutOfRange error from ReplicaManager when

[jira] [Commented] (KAFKA-3042) updateIsr should stop after failed several times due to zkVersion issue

[ https://issues.apache.org/jira/browse/KAFKA-3042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15232535#comment-15232535 ] Flavio Junqueira commented on KAFKA-3042: - Here is what I've been able to find out so far based on

[jira] [Created] (KAFKA-3532) add principal.builder.class that can extract user from a field

Jun Rao created KAFKA-3532: -- Summary: add principal.builder.class that can extract user from a field Key: KAFKA-3532 URL: https://issues.apache.org/jira/browse/KAFKA-3532 Project: Kafka Issue

[jira] [Commented] (KAFKA-725) Broker Exception: Attempt to read with a maximum offset less than start offset

[ https://issues.apache.org/jira/browse/KAFKA-725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15232514#comment-15232514 ] Guozhang Wang commented on KAFKA-725: - Usually client code should gracefully handle

[jira] [Created] (KAFKA-3531) support subnet in ACL tool

Jun Rao created KAFKA-3531: -- Summary: support subnet in ACL tool Key: KAFKA-3531 URL: https://issues.apache.org/jira/browse/KAFKA-3531 Project: Kafka Issue Type: Wish Affects Versions: 0.9.0.1

Re: [DISCUSS] KIP-50 - Enhance Authorizer interface to be aware of supported Principal Types

Yes, if we have Java interface, then we won’t need Scala interface. Thanks Bosco On 4/8/16, 9:04 AM, "Ashish Singh" wrote: >Thanks for the input Don. One of the possible paths for Option 2 is to >completely drop Scala interface, would that be Ok with you folks? > >On

[GitHub] kafka pull request: MINOR: improve logging of consumer system test...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1199 --- 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

[jira] [Created] (KAFKA-3530) Making the broker-list option consistent across all tools

Jun Rao created KAFKA-3530: -- Summary: Making the broker-list option consistent across all tools Key: KAFKA-3530 URL: https://issues.apache.org/jira/browse/KAFKA-3530 Project: Kafka Issue Type: Bug

[jira] [Assigned] (KAFKA-3525) max.reserved.broker.id off-by-one error

[ https://issues.apache.org/jira/browse/KAFKA-3525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar Reddy reassigned KAFKA-3525: -- Assignee: Manikumar Reddy > max.reserved.broker.id off-by-one error >

[jira] [Resolved] (KAFKA-725) Broker Exception: Attempt to read with a maximum offset less than start offset

[ https://issues.apache.org/jira/browse/KAFKA-725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-725. - Resolution: Fixed Fix Version/s: 0.10.0.0 Issue resolved by pull request 1178

[jira] [Commented] (KAFKA-3519) Refactor Transformer templates to return the same strong-typed value.

[ https://issues.apache.org/jira/browse/KAFKA-3519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15232454#comment-15232454 ] ASF GitHub Bot commented on KAFKA-3519: --- GitHub user guozhangwang opened a pull request:

[GitHub] kafka pull request: KAFKA-3519: Refactor Transformer's transform /...

GitHub user guozhangwang opened a pull request: https://github.com/apache/kafka/pull/1204 KAFKA-3519: Refactor Transformer's transform / punctuate to return nullable values You can merge this pull request into a Git repository by running: $ git pull

[jira] [Commented] (KAFKA-3512) Add a foreach() operator in Kafka Streams DSL

[ https://issues.apache.org/jira/browse/KAFKA-3512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15232417#comment-15232417 ] ASF GitHub Bot commented on KAFKA-3512: --- Github user asfgit closed the pull request at:

[jira] [Resolved] (KAFKA-3512) Add a foreach() operator in Kafka Streams DSL

[ https://issues.apache.org/jira/browse/KAFKA-3512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-3512. -- Resolution: Fixed Issue resolved by pull request 1193

[GitHub] kafka pull request: KAFKA-3512: Added foreach operator

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1193 --- 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

Re: [DISCUSS] KIP-50 - Enhance Authorizer interface to be aware of supported Principal Types

Thanks for the input Don. One of the possible paths for Option 2 is to completely drop Scala interface, would that be Ok with you folks? On Thursday, April 7, 2016, Don Bosco Durai wrote: > Ranger team would prefer option #2. Right now, we have to access some of > the nested

[jira] [Commented] (KAFKA-3505) Set curRecord in punctuate() functions

[ https://issues.apache.org/jira/browse/KAFKA-3505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15232388#comment-15232388 ] ASF GitHub Bot commented on KAFKA-3505: --- Github user asfgit closed the pull request at:

[jira] [Resolved] (KAFKA-3505) Set curRecord in punctuate() functions

[ https://issues.apache.org/jira/browse/KAFKA-3505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava resolved KAFKA-3505. -- Resolution: Fixed Fix Version/s: (was: 0.10.0.0)

[GitHub] kafka pull request: KAFKA-3505: Fix punctuate generated record met...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1190 --- 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

[jira] [Resolved] (KAFKA-3372) Trailing space in Kafka ConsumerConfig

[ https://issues.apache.org/jira/browse/KAFKA-3372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar Reddy resolved KAFKA-3372. Resolution: Fixed Assignee: Manikumar Reddy (was: Neha Narkhede) Fix

[jira] [Commented] (KAFKA-3492) support quota based on authenticated user name

[ https://issues.apache.org/jira/browse/KAFKA-3492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15232324#comment-15232324 ] Rajini Sivaram commented on KAFKA-3492: --- [~aauradkar] Are you planning to work on this? If not, I

Re: [DISCUSS] KIP-43: Kafka SASL enhancements

Gwen, Kafka 0.9.0.x expect the first token from the client (immediately following connection for SASL_PLAINTEXT, immediately following TLS handsshake for SASL_SSL) to be a GSSAPI token. This is passed directly to the SASL GSSAPI engine. Hence a client which may connect to SASL-enabled Kafka

[jira] [Resolved] (KAFKA-3516) Metrics settings in server.properties cause ClassCastException

[ https://issues.apache.org/jira/browse/KAFKA-3516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar Reddy resolved KAFKA-3516. Resolution: Not A Problem Fix Version/s: 0.10.0.0

[jira] [Commented] (KAFKA-3488) commitAsync() fails if metadata update creates new SASL/SSL connection

[ https://issues.apache.org/jira/browse/KAFKA-3488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15232311#comment-15232311 ] Rajini Sivaram commented on KAFKA-3488: --- [~guozhang] Since requests from the consumer tend to be

[jira] [Assigned] (KAFKA-3516) Metrics settings in server.properties cause ClassCastException

[ https://issues.apache.org/jira/browse/KAFKA-3516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar Reddy reassigned KAFKA-3516: -- Assignee: Manikumar Reddy > Metrics settings in server.properties cause

[jira] [Commented] (KAFKA-725) Broker Exception: Attempt to read with a maximum offset less than start offset

[ https://issues.apache.org/jira/browse/KAFKA-725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15231850#comment-15231850 ] Mudit Kumar commented on KAFKA-725: --- Hi, We are seeing below exception in our kafka logs on one of the

[jira] [Updated] (KAFKA-3502) Build is killed during kafka streams tests due to `pure virtual method called` error

[ https://issues.apache.org/jira/browse/KAFKA-3502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3502: --- Issue Type: Sub-task (was: Bug) Parent: KAFKA-2054 > Build is killed during kafka streams

[jira] [Updated] (KAFKA-3502) Build is killed during kafka streams tests due to `pure virtual method called` error

[ https://issues.apache.org/jira/browse/KAFKA-3502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3502: --- Summary: Build is killed during kafka streams tests due to `pure virtual method called` error (was:

[jira] [Resolved] (KAFKA-2994) Transient Failure due to BindException: Address already in use

[ https://issues.apache.org/jira/browse/KAFKA-2994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-2994. Resolution: Duplicate Duplicate of KAFKA-3453. > Transient Failure due to BindException: Address

[jira] [Resolved] (KAFKA-3001) Transient Failure in kafka.api.SaslPlaintextConsumerTest

[ https://issues.apache.org/jira/browse/KAFKA-3001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-3001. Resolution: Duplicate Looks like a duplicate of KAFKA-2910. > Transient Failure in

Re: [VOTE] KIP-33 - Add a time based log index

Great job Jiangjie. A few comments: 1. "if an offset index entry is inserted, it will also insert a time index entry" what is the motivation for co-inserting offset index and timestamp index? Is it just for simplicity or are there any other considerations? 2. "Search message by timestamp": you