Offsets in Kafka producer start with -1 for new topic

I created a new Kafka topic with 1 partition and then sent 10 messages using the KafkaProducer API using the async callback. What I saw was that the offsets in the RecordMetadata for the first record was -1. Shouldn't it be 0 as offsets start with 0? Is it a bug or works as expected? Thanks, Ja

Re: [DISCUSS] KIP-190: Handle client-ids consistently between clients and brokers

Can the Discussion Thread link be filled out ? Cheers On Wed, Sep 27, 2017 at 2:03 AM, Mickael Maison wrote: > I don't know the history either, I quickly scanned the KIP-55 threads > and couldn't see it being discussed. > > Anyway, your suggestion sounds good to me, are you planning to do that

[jira] [Resolved] (KAFKA-6017) Cannot get broker ids from Kafka using kafka-connect

[ https://issues.apache.org/jira/browse/KAFKA-6017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jorge Machado resolved KAFKA-6017. -- Resolution: Not A Problem On my side this was a missed configuration on kafka + cdh that broke t

[jira] [Resolved] (KAFKA-601) ConsumerConnector.shutdown() hangs if autocommit is enabled, and no zk available

[ https://issues.apache.org/jira/browse/KAFKA-601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-601. - Resolution: Auto Closed Closing inactive issue. The old consumer is no longer supported. > ConsumerConnect

[jira] [Resolved] (KAFKA-536) Kafka async appender/producer looses most messages

[ https://issues.apache.org/jira/browse/KAFKA-536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-536. - Resolution: Auto Closed Closing inactive issue. > Kafka async appender/producer looses most messages > --

[jira] [Resolved] (KAFKA-519) Allow commiting the state of single KafkaStream

[ https://issues.apache.org/jira/browse/KAFKA-519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-519. - Resolution: Auto Closed Closing inactive issue. The old consumer is no longer supported. > Allow commitin

[jira] [Resolved] (KAFKA-602) A ConsumerConnector that never receives messages does not shutdown cleanly

[ https://issues.apache.org/jira/browse/KAFKA-602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-602. - Resolution: Auto Closed Closing inactive issue. The old consumer is no longer supported. > A ConsumerConne

[jira] [Resolved] (KAFKA-623) It should be possible to re-create KafkaStreams after an exception, without recreating ConsumerConnector

[ https://issues.apache.org/jira/browse/KAFKA-623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-623. - Resolution: Auto Closed Closing inactive issue. The old consumer is no longer supported. > It should be po

[jira] [Resolved] (KAFKA-635) Producer error when trying to send not displayed unless in DEBUG logging level

[ https://issues.apache.org/jira/browse/KAFKA-635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-635. - Resolution: Auto Closed Closing inactive issue. The old producer is no longer supported. > Producer error

[jira] [Resolved] (KAFKA-810) KafkaStream toString method blocks indefinitely

[ https://issues.apache.org/jira/browse/KAFKA-810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-810. - Resolution: Auto Closed Closing inactive issue. The old consumer is no longer supported. > KafkaStream toS

[jira] [Resolved] (KAFKA-845) Re-implement shallow iteration on 0.8.1

[ https://issues.apache.org/jira/browse/KAFKA-845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-845. - Resolution: Auto Closed Closing inactive issue. > Re-implement shallow iteration on 0.8.1 >

[jira] [Resolved] (KAFKA-853) Allow OffsetFetchRequest to initialize offsets

[ https://issues.apache.org/jira/browse/KAFKA-853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-853. - Resolution: Won't Fix Closing inactive issue as per above comment. > Allow OffsetFetchRequest to initializ

[jira] [Resolved] (KAFKA-242) Subsequent calls of ConsumerConnector.createMessageStreams cause Consumer offset to be incorrect

[ https://issues.apache.org/jira/browse/KAFKA-242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-242. - Resolution: Auto Closed Closing inactive issue. The old consumer is no longer supported. > Subsequent call

[jira] [Resolved] (KAFKA-243) Improve consumer connector documentation to include blocking semantics of kafka message streams

[ https://issues.apache.org/jira/browse/KAFKA-243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-243. - Resolution: Auto Closed Closing inactive issue. The old consumer is no longer supported, please upgrade to

[jira] [Resolved] (KAFKA-250) Provide consumer iterator callback handler

[ https://issues.apache.org/jira/browse/KAFKA-250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-250. - Resolution: Auto Closed Closing inactive issue. The old consumer is no longer supported > Provide consumer

[jira] [Resolved] (KAFKA-232) ConsumerConnector has no access to "getOffsetsBefore"

[ https://issues.apache.org/jira/browse/KAFKA-232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-232. - Resolution: Won't Fix Closing inactive issue. The old consumer is no longer supported. This jira requireme