[jira] [Commented] (KAFKA-4767) KafkaProducer is not joining its IO thread properly

[ https://issues.apache.org/jira/browse/KAFKA-4767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15869382#comment-15869382 ] huxi commented on KAFKA-4767: - I think I might get the point of what you mean. What you really concerns is

Kafka exception

Hi,all! Our program uses the high level consumer api(the version is 0.8.x). Sometimes the program will throw an exception in the 42th row in kafka.utils.IteratorTemplate class，the content is "throw new IllegalStateException("Expected item but none found.")". I think it is a race condition

[jira] [Updated] (KAFKA-4769) Add Float serializer, deserializer, serde

[ https://issues.apache.org/jira/browse/KAFKA-4769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Noll updated KAFKA-4769: Status: Patch Available (was: Open) > Add Float serializer, deserializer, serde >

[jira] [Commented] (KAFKA-4769) Add Float serializer, deserializer, serde

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

[GitHub] kafka pull request #2554: KAFKA-4769: Add Float serializer, deserializer, se...

GitHub user miguno opened a pull request: https://github.com/apache/kafka/pull/2554 KAFKA-4769: Add Float serializer, deserializer, serde You can merge this pull request into a Git repository by running: $ git pull https://github.com/miguno/kafka KAFKA-4769 Alternatively you

Re: [VOTE] KIP-98: Exactly Once Delivery and Transactional Messaging

Hi Jun, Answers inline: 210. Pid snapshots: Is the number of pid snapshot configurable or hardcoded > with 2? When do we decide to roll a new snapshot? Based on time, byte, or > offset? Is that configurable too? > These are good questions. We haven't fleshed out the policy by which the

Re: [DISCUSS] KIP-82 - Add Record Headers

We have proposed a few significant changes to the message format in KIP-98 which now seems likely to pass (perhaps with some iterations on implementation details). It would be good to try and coordinate the changes in both of the proposals to make sure they are consistent and compatible. I think

[jira] [Created] (KAFKA-4769) Add Float serializer, deserializer, serde

Michael Noll created KAFKA-4769: --- Summary: Add Float serializer, deserializer, serde Key: KAFKA-4769 URL: https://issues.apache.org/jira/browse/KAFKA-4769 Project: Kafka Issue Type:

[jira] [Comment Edited] (KAFKA-4767) KafkaProducer is not joining its IO thread properly

[ https://issues.apache.org/jira/browse/KAFKA-4767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15869240#comment-15869240 ] Buğra Gedik edited comment on KAFKA-4767 at 2/16/17 5:26 AM: - IMO: * An

[jira] [Commented] (KAFKA-4767) KafkaProducer is not joining its IO thread properly

[ https://issues.apache.org/jira/browse/KAFKA-4767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15869240#comment-15869240 ] Buğra Gedik commented on KAFKA-4767: IMO: * An interrupt means immediate exit from whatever you are

[jira] [Commented] (KAFKA-4720) Add KStream.peek(ForeachAction<K,V>)

[ https://issues.apache.org/jira/browse/KAFKA-4720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15869239#comment-15869239 ] Guozhang Wang commented on KAFKA-4720: -- [~stevenschlansker] I have added you to contributor list, you

[jira] [Updated] (KAFKA-4767) KafkaProducer is not joining its IO thread properly

[ https://issues.apache.org/jira/browse/KAFKA-4767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Buğra Gedik updated KAFKA-4767: --- Description: The {{KafkaProducer}} is not properly joining the thread it creates. The code is like

[jira] [Assigned] (KAFKA-4720) Add KStream.peek(ForeachAction<K,V>)

[ https://issues.apache.org/jira/browse/KAFKA-4720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang reassigned KAFKA-4720: Assignee: Steven Schlansker > Add KStream.peek(ForeachAction) >

[jira] [Commented] (KAFKA-4720) Add KStream.peek(ForeachAction<K,V>)

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

[jira] [Resolved] (KAFKA-4720) Add KStream.peek(ForeachAction<K,V>)

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

[GitHub] kafka pull request #2493: KAFKA-4720: add a KStream#peek(ForeachAction<K, V>...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2493 --- 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-4766) Document lz4 and lz4hc in confluence

[ https://issues.apache.org/jira/browse/KAFKA-4766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15869092#comment-15869092 ] Lee Dongjin commented on KAFKA-4766: I just updated the wiki page. Is this exactly corresponds to your

[jira] [Commented] (KAFKA-4766) Document lz4 and lz4hc in confluence

[ https://issues.apache.org/jira/browse/KAFKA-4766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15869089#comment-15869089 ] Lee Dongjin commented on KAFKA-4766: Yes, it seems like LZ4 compression is omitted at the wiki page.

Re: [DISCUSS] KIP-120: Cleanup Kafka Streams builder API

On Wed, Feb 15, 2017 at 5:04 PM, Matthias J. Sax wrote: > - We also removed method #topologyBuilder() from KStreamBuilder because > we think #transform() should provide all functionality you need to > mix-an-match Processor API and DSL. If there is any further concern >

Jenkins build is back to normal : kafka-trunk-jdk7 #1940

See

Re: [kafka-clients] [VOTE] 0.10.2.0 RC2

Hi, Ewen, Thanks for running the release. +1. Verified quickstart on 2.10 binary. Jun On Tue, Feb 14, 2017 at 10:39 AM, Ewen Cheslack-Postava wrote: > Hello Kafka users, developers and client-developers, > > This is the third candidate for release of Apache Kafka 0.10.2.0.

[jira] [Commented] (KAFKA-2729) Cached zkVersion not equal to that in zookeeper, broker not recovering.

[ https://issues.apache.org/jira/browse/KAFKA-2729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15868971#comment-15868971 ] Elias Levy commented on KAFKA-2729: --- Hit this again during testing with 0.10.0.1 on a 10 node broker

Re: [DISCUSS] KIP-120: Cleanup Kafka Streams builder API

One current benefit of having those classes extensible is the ability to write simple wrappers around KStreamBuilder to add functionality that currently doesn't exist. In my case, I extend KStreamBuilder mainly to provide syntactic sugar and make it easier to work with. For instance, I overload

[jira] [Commented] (KAFKA-4767) KafkaProducer is not joining its IO thread properly

[ https://issues.apache.org/jira/browse/KAFKA-4767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15868943#comment-15868943 ] huxi commented on KAFKA-4767: - Seems that KafkaProducer already initiates a close to the IO thread by setting

[GitHub] kafka pull request #2553: MINOR: fix indention in tags

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

[GitHub] kafka pull request #2553: MINOR: fix indention in tags

GitHub user mjsax opened a pull request: https://github.com/apache/kafka/pull/2553 MINOR: fix indention in tags You can merge this pull request into a Git repository by running: $ git pull https://github.com/mjsax/kafka hotfixDocs2 Alternatively you can review and apply

[GitHub] kafka pull request #2547: MINOR: add session windows doc to streams.html

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2547 --- 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-98: Exactly Once Delivery and Transactional Messaging

Hi, Jason, Thanks for the updated doc. Looks good to me overall. Just a few more minor comments. 210. Pid snapshots: Is the number of pid snapshot configurable or hardcoded with 2? When do we decide to roll a new snapshot? Based on time, byte, or offset? Is that configurable too? 211. I am

[GitHub] kafka pull request #2542: MINOR: Stream metrics documentation

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

+1 (non-binding). Verified source and Scala 2.11 binary artifacts, quick start on source artifact and Scala 2.11 binary artifacts. Thanks for managing the release! Ismael On Tue, Feb 14, 2017 at 6:39 PM, Ewen Cheslack-Postava wrote: > Hello Kafka users, developers and

Re: [DISCUSS] KIP-120: Cleanup Kafka Streams builder API

Hi, according to the feedback, I updated the KIP, and limited its scope to some extend: - Instead of changing the creation of KafkaStreams instances, we keep the current pattern (we might do a follow up KIP on this though). - We also added a new method #describe() that returns a

[jira] [Comment Edited] (KAFKA-4340) Change the default value of log.message.timestamp.difference.max.ms to the same as log.retention.ms

[ https://issues.apache.org/jira/browse/KAFKA-4340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15868777#comment-15868777 ] Jiangjie Qin edited comment on KAFKA-4340 at 2/15/17 11:05 PM: --- [~junrao]

[jira] [Commented] (KAFKA-4340) Change the default value of log.message.timestamp.difference.max.ms to the same as log.retention.ms

[ https://issues.apache.org/jira/browse/KAFKA-4340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15868777#comment-15868777 ] Jiangjie Qin commented on KAFKA-4340: - [~junrao] [~ijuma] [~cmccabe] I created

Re: KIP-121 [VOTE]: Add KStream peek method

KIP is accepted, discussion now moves to PR. Thanks Eno On Wed, Feb 15, 2017 at 12:28 PM, Steven Schlansker < sschlans...@opentable.com> wrote: > Oops, sorry, a number of votes were sent only to -dev and not to > -user and so I missed those in the email I just sent. The actual count is > more

[GitHub] kafka pull request #2492: HOTFIX: fixed section incompatible Steams API chan...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2492 --- 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: KIP-121 [VOTE]: Add KStream peek method

+1 (binding) from me. For the record, there were 4 binding +1s (Gwen, Guozhang, Jay and myself). Ismael On Wed, Feb 15, 2017 at 8:24 PM, Steven Schlansker < sschlans...@opentable.com> wrote: > From reading the bylaws it's not entirely clear who closes the vote or how > they > decide when to do

Re: KIP-121 [VOTE]: Add KStream peek method

Oops, sorry, a number of votes were sent only to -dev and not to -user and so I missed those in the email I just sent. The actual count is more like +8 > On Feb 15, 2017, at 12:24 PM, Steven Schlansker > wrote: > > From reading the bylaws it's not entirely clear

Re: KIP-121 [VOTE]: Add KStream peek method

From reading the bylaws it's not entirely clear who closes the vote or how they decide when to do so. Given a week has passed and assuming Jay's and Matthias's votes are binding, we have a result of +4 votes with no other votes cast. I'll update the KIP with the result shortly :) > On Feb 14,

[jira] [Commented] (KAFKA-4340) Change the default value of log.message.timestamp.difference.max.ms to the same as log.retention.ms

[ https://issues.apache.org/jira/browse/KAFKA-4340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15868449#comment-15868449 ] Ismael Juma commented on KAFKA-4340: [~becket_qin], do you think you'll be able to look into this

[jira] [Commented] (KAFKA-4340) Change the default value of log.message.timestamp.difference.max.ms to the same as log.retention.ms

[ https://issues.apache.org/jira/browse/KAFKA-4340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15868437#comment-15868437 ] Colin P. McCabe commented on KAFKA-4340: ClientCompatibilityTestNewBroker, TestUpgrade,

[jira] [Commented] (KAFKA-4340) Change the default value of log.message.timestamp.difference.max.ms to the same as log.retention.ms

[ https://issues.apache.org/jira/browse/KAFKA-4340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15868433#comment-15868433 ] Jun Rao commented on KAFKA-4340: [~becket_qin], after committing the patch in this jira. One of our system

Re: [VOTE] KIP-98: Exactly Once Delivery and Transactional Messaging

Thanks everyone who has voted so far! Jun brought up a good point offline that the BeginTxnRequest was not strictly needed since there is no state to recover until a partition has been added to the transaction. Instead we can start the transaction implicitly upon receiving the first

Reg: Kafka HDFS Connector with (HDFS SSL enabled)

Hi, Does Kafka HDFS Connect work with HDFS (SSL). As I see only properties in security is hdfs.authentication.kerberos, connect.hdfs.keytab,hdfs.namenode.principal as these properties are all related to HDFS Kerberos. As from the configuration and code I see we pass only Kerberos parameters, not

[jira] [Commented] (KAFKA-3893) Kafka Broker ID disappears from /brokers/ids

[ https://issues.apache.org/jira/browse/KAFKA-3893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15868331#comment-15868331 ] Armin Braun commented on KAFKA-3893: I think this is a duplicate of

Re: [VOTE] KIP-111 Kafka should preserve the Principal generated by the PrincipalBuilder while processing the request received on socket channel, on the broker.

@Jun thanks for the comments.Please see the replies inline. Currently kafka-acl.sh just creates an ACL path in ZK with the principal name string. > Yes, the kafka-acl.sh calls the addAcl() on the inbuilt SimpleAclAuthorizer which in turn creates an ACL in ZK with the Principal name string.

[jira] [Comment Edited] (KAFKA-4765) org.apache.kafka.clients.producer.KafkaProducerTest#testConstructorFailureCloseResource and Similar Tests are Failing on some Systems (127.0.53.53 Collision Warnin

[ https://issues.apache.org/jira/browse/KAFKA-4765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15867408#comment-15867408 ] Armin Braun edited comment on KAFKA-4765 at 2/15/17 6:15 PM: - -I could add a

[jira] [Updated] (KAFKA-4765) org.apache.kafka.clients.producer.KafkaProducerTest#testConstructorFailureCloseResource and Similar Tests are Failing on some Systems (127.0.53.53 Collision Warning)

[ https://issues.apache.org/jira/browse/KAFKA-4765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Armin Braun updated KAFKA-4765: --- Status: Patch Available (was: Open) >

Re: [DISCUSS] KIP-84: Support SASL/SCRAM mechanisms

Yes. Thank you, Ismael. On Wed, Feb 8, 2017 at 2:30 AM, Ismael Juma wrote: > Hi Roger, > > Sorry for the delay. SCRAM is specified by: > > https://tools.ietf.org/html/rfc5802 > > The following quote is relevant: > > A SCRAM mechanism name is a string "SCRAM-" followed by the

[jira] [Commented] (KAFKA-4765) org.apache.kafka.clients.producer.KafkaProducerTest#testConstructorFailureCloseResource and Similar Tests are Failing on some Systems (127.0.53.53 Collision Warning)

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

[GitHub] kafka pull request #2552: KAFKA-4765: Fixed Intentionally Broken Hosts Resol...

GitHub user original-brownbear opened a pull request: https://github.com/apache/kafka/pull/2552 KAFKA-4765: Fixed Intentionally Broken Hosts Resolving to 127.0.53.53 Fixes https://issues.apache.org/jira/browse/KAFKA-4765 by simply using artificially broken hosts that are not

Re: Cannot start up Kafka Server within Java

kafka publishes a "test" artifact: http://search.maven.org/#search|ga|1|a%3A%22kafka_2.12%22 if you introduce a test-scoped dep. on it, which in maven would look like: org.apache.kafka kafka_2.12 0.10.1.1 test

Re: [VOTE] 0.10.2.0 RC2

Heroku tested this with our usual round of performance benchmarks, and there seem to be no notable regressions in this RC that we can see (for a sample on earlier regressions we found using these benchmarks during the 0.10.0.0 release,

Re: [VOTE] KIP-111 Kafka should preserve the Principal generated by the PrincipalBuilder while processing the request received on socket channel, on the broker.

@jun: "Currently kafka-acl.sh just creates an ACL path in ZK with the principal name string" - yes, but not directly. all it actually does it spin-up the Authorizer and call Authorizer.addAcl() on it. the vanilla Authorizer goes to ZK. but generally speaking, users can plug in their own

Re: [DISCUSS] KIP-82 - Add Record Headers

I've trimmed the inline contents as this mail is getting too big for the apache mailing list software to deliver :-( 1. the important thing for interoperability is for different "interested parties" (plugins, infra layers/wrappers, user-code) to be able to stick pieces of metadata onto msgs

Re: Cannot start up Kafka Server within Java

Hi Stefan, The mailing list suppressed your attachment, so, it's hard to offer any advice without the error. I'd suggest trying to post the error in a GitHub Gist, or some similar format. I dug up this mailing list archive about starting a Kafka server in-process that might help:

Cannot start up Kafka Server within Java

Dear Kafka dev team! I’m implementing a data stream processor with Apache Kafka for my bachelor’s thesis and right now I’m struggling with trying to get the Kafka Server started with Java. A short summary of what I’m doing currently: 1. Start ZooKeeper (manually via terminal). 2.

[jira] [Commented] (KAFKA-4768) Single-request latency for streams can be very high

[ https://issues.apache.org/jira/browse/KAFKA-4768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15867928#comment-15867928 ] Eno Thereska commented on KAFKA-4768: - This is actually not a real problem since it's because of

[jira] [Resolved] (KAFKA-4768) Single-request latency for streams can be very high

[ https://issues.apache.org/jira/browse/KAFKA-4768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska resolved KAFKA-4768. - Resolution: Not A Problem > Single-request latency for streams can be very high >

[jira] [Created] (KAFKA-4768) Single-request latency for streams can be very high

Eno Thereska created KAFKA-4768: --- Summary: Single-request latency for streams can be very high Key: KAFKA-4768 URL: https://issues.apache.org/jira/browse/KAFKA-4768 Project: Kafka Issue Type:

Re: [VOTE] KIP-82 Add Record Headers

+1 on introducing the concept of headers, neutral on specific implementation. On 14/02/2017 22:34, Jay Kreps wrote: Couple of things I think we still need to work out: 1. I think we agree about the key, but I think we haven't talked about the value yet. I think if our goal is an open

Re: [VOTE] KIP-111 Kafka should preserve the Principal generated by the PrincipalBuilder while processing the request received on socket channel, on the broker.

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

[GitHub] kafka pull request #2551: KAFKA-4752: Fixed bandwidth calculation

GitHub user enothereska opened a pull request: https://github.com/apache/kafka/pull/2551 KAFKA-4752: Fixed bandwidth calculation You can merge this pull request into a Git repository by running: $ git pull https://github.com/enothereska/kafka KAFKA-4752-join-bw Alternatively

[jira] [Commented] (KAFKA-4752) Streams Simple Benchmark MB/sec calculation is not correct for Join operations

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

Re: [DISCUSS] KIP-116 - Add State Store Checkpoint Interval Configuration

Ok. lets close this KIP off then as it isn't needed at the moment. We can revive later if needed. On Tue, 14 Feb 2017 at 04:16 Eno Thereska wrote: > Even if users commit on every record, the expensive part will not be the > checkpointing proposed in this KIP, but the

[jira] [Work started] (KAFKA-4752) Streams Simple Benchmark MB/sec calculation is not correct for Join operations

[ https://issues.apache.org/jira/browse/KAFKA-4752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-4752 started by Eno Thereska. --- > Streams Simple Benchmark MB/sec calculation is not correct for Join operations >

[jira] [Updated] (KAFKA-4767) KafkaProducer is not joining its IO thread properly

[ https://issues.apache.org/jira/browse/KAFKA-4767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Buğra Gedik updated KAFKA-4767: --- Summary: KafkaProducer is not joining its IO thread properly (was: KafkaProducer is not joining the

[jira] [Created] (KAFKA-4767) KafkaProducer is not joining the thread properly

Buğra Gedik created KAFKA-4767: -- Summary: KafkaProducer is not joining the thread properly Key: KAFKA-4767 URL: https://issues.apache.org/jira/browse/KAFKA-4767 Project: Kafka Issue Type: Bug

[jira] [Updated] (KAFKA-4767) KafkaProducer is not joining the thread properly

[ https://issues.apache.org/jira/browse/KAFKA-4767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Buğra Gedik updated KAFKA-4767: --- Description: The {{KafkaProducer}} is not properly joining the thread it creates. The code is like

[jira] [Created] (KAFKA-4766) Document lz4 and lz4hc in confluence

Daniel Pinyol created KAFKA-4766: Summary: Document lz4 and lz4hc in confluence Key: KAFKA-4766 URL: https://issues.apache.org/jira/browse/KAFKA-4766 Project: Kafka Issue Type: Sub-task

[jira] [Commented] (KAFKA-4277) creating ephemeral node already exist

[ https://issues.apache.org/jira/browse/KAFKA-4277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15867671#comment-15867671 ] Steven Aerts commented on KAFKA-4277: - Reproduced on our side with Scala 2.11 kafka_2.11-0.10.1.1,

Re: Correct prefetching of data to KTable-like structure on application startup

Hi Matthias, yes, that's exactly what I was looking for. I wasn't aware of the possibility to get the starting offset of a partition. My bad, thanks a lot. Cheers,  Jan -- Původní zpráva -- Od: Matthias J. Sax Komu: dev@kafka.apache.org Datum: 15. 2. 2017

[jira] [Comment Edited] (KAFKA-4762) Consumer throwing RecordTooLargeException even when messages are not that large

[ https://issues.apache.org/jira/browse/KAFKA-4762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15864954#comment-15864954 ] huxi edited comment on KAFKA-4762 at 2/15/17 9:17 AM: -- Logs show that you are using

[jira] [Updated] (KAFKA-4765) org.apache.kafka.clients.producer.KafkaProducerTest#testConstructorFailureCloseResource and Similar Tests are Failing on some Systems (127.0.53.53 Collision Warning)

[ https://issues.apache.org/jira/browse/KAFKA-4765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Armin Braun updated KAFKA-4765: --- Priority: Major (was: Critical) >