[GitHub] kafka pull request #3334: MINOR: Fix ConsumerBounceTest to wait for consumer...

GitHub user rajinisivaram opened a pull request: https://github.com/apache/kafka/pull/3334 MINOR: Fix ConsumerBounceTest to wait for consumer close You can merge this pull request into a Git repository by running: $ git pull https://github.com/rajinisivaram/kafka MINOR-more-te

[GitHub] kafka pull request #3335: KAFKA-5434: Console consumer hangs if not existing...

GitHub user ppatierno opened a pull request: https://github.com/apache/kafka/pull/3335 KAFKA-5434: Console consumer hangs if not existing partition is specified Added checking partition exists before assign request You can merge this pull request into a Git repository by running:

[jira] [Commented] (KAFKA-5434) Console consumer hangs if not existing partition is specified

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

[jira] [Updated] (KAFKA-5434) Console consumer hangs if not existing partition is specified

[ https://issues.apache.org/jira/browse/KAFKA-5434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paolo Patierno updated KAFKA-5434: -- Status: Patch Available (was: Open) > Console consumer hangs if not existing partition is speci

[jira] [Updated] (KAFKA-5409) Providing a custom client-id to the ConsoleProducer tool

[ https://issues.apache.org/jira/browse/KAFKA-5409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paolo Patierno updated KAFKA-5409: -- Status: Patch Available (was: Open) > Providing a custom client-id to the ConsoleProducer tool

[jira] [Updated] (KAFKA-5410) Fix taskClass() method name in Connector and flush() signature in SinkTask

[ https://issues.apache.org/jira/browse/KAFKA-5410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paolo Patierno updated KAFKA-5410: -- Status: Patch Available (was: Open) > Fix taskClass() method name in Connector and flush() sign

[jira] [Assigned] (KAFKA-5354) MirrorMaker not preserving headers

[ https://issues.apache.org/jira/browse/KAFKA-5354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reassigned KAFKA-5354: -- Assignee: Michael Andre Pearce > MirrorMaker not preserving headers > -

[jira] [Updated] (KAFKA-5274) Review and improve AdminClient Javadoc for the first release (KIP-117)

[ https://issues.apache.org/jira/browse/KAFKA-5274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5274: --- Status: Patch Available (was: In Progress) > Review and improve AdminClient Javadoc for the first rel

[jira] [Assigned] (KAFKA-4208) Add Record Headers

[ https://issues.apache.org/jira/browse/KAFKA-4208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reassigned KAFKA-4208: -- Assignee: Michael Andre Pearce > Add Record Headers > -- > > Ke

[jira] [Assigned] (KAFKA-5142) KIP-145 - Expose Record Headers in Kafka Connect

[ https://issues.apache.org/jira/browse/KAFKA-5142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reassigned KAFKA-5142: -- Assignee: Michael Andre Pearce > KIP-145 - Expose Record Headers in Kafka Connect > ---

[jira] [Commented] (KAFKA-5421) Getting InvalidRecordException

[ https://issues.apache.org/jira/browse/KAFKA-5421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16049037#comment-16049037 ] Tom Bentley commented on KAFKA-5421: The root cause is probably bitrot on the disk sto

[jira] [Updated] (KAFKA-5354) MirrorMaker not preserving headers

[ https://issues.apache.org/jira/browse/KAFKA-5354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5354: --- Resolution: Fixed Status: Resolved (was: Patch Available) Issue resolved by pull request 3322

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

See Changes: [ismael] KAFKA-5354; MirrorMaker not preserving headers -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on ubu

[GitHub] kafka pull request #3322: KAFKA-5354: MirrorMaker not preserving headers

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

[jira] [Commented] (KAFKA-5354) MirrorMaker not preserving headers

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

[GitHub] kafka pull request #3336: MINOR: Fix typo at StreamsConfig javadoc

GitHub user ilayaperumalg opened a pull request: https://github.com/apache/kafka/pull/3336 MINOR: Fix typo at StreamsConfig javadoc You can merge this pull request into a Git repository by running: $ git pull https://github.com/ilayaperumalg/kafka fix-typo-StreamsConfig Alter

[GitHub] kafka pull request #3337: MINOR: Delegated the creation of new Thread to Kaf...

GitHub user Kamal15 opened a pull request: https://github.com/apache/kafka/pull/3337 MINOR: Delegated the creation of new Thread to KafkaThread class. You can merge this pull request into a Git repository by running: $ git pull https://github.com/Kamal15/kafka cleanup Alterna

[jira] [Created] (KAFKA-5445) Document exceptions thrown by AdminClient methods

Ismael Juma created KAFKA-5445: -- Summary: Document exceptions thrown by AdminClient methods Key: KAFKA-5445 URL: https://issues.apache.org/jira/browse/KAFKA-5445 Project: Kafka Issue Type: Impro

Re: [DISCUSS]: KIP-149: Enabling key access in ValueTransformer, ValueMapper, and ValueJoiner

Hi, I introduced ValueTransformerCommon just to combine common methods of ValueTransformer and ValueTransformerWithKey and avoid copy-paste. I am aware of this issue and I agree that this needs users to compile the code and therefore is not backwards compatible. When I saw this issue, I thought th

JIRA contributor list

Please could I be added to the JIRA contributor list so that I can assign issues to myself? Thanks, Tom

[jira] [Commented] (KAFKA-5432) producer and consumer SocketTimeoutException

[ https://issues.apache.org/jira/browse/KAFKA-5432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16049149#comment-16049149 ] Jian Lin commented on KAFKA-5432: - [~huxi_2b] look at the log consumer {code:java} 2017-0

Jenkins build is back to normal : kafka-trunk-jdk8 #1705

See

[jira] [Comment Edited] (KAFKA-5432) producer and consumer SocketTimeoutException

[ https://issues.apache.org/jira/browse/KAFKA-5432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16049149#comment-16049149 ] Jian Lin edited comment on KAFKA-5432 at 6/14/17 1:03 PM: -- [~huxi

[jira] [Commented] (KAFKA-5431) LogCleaner stopped due to org.apache.kafka.common.errors.CorruptRecordException

[ https://issues.apache.org/jira/browse/KAFKA-5431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16049156#comment-16049156 ] Carsten Rietz commented on KAFKA-5431: -- I still have no idea what exactly to do to tr

[jira] [Comment Edited] (KAFKA-5431) LogCleaner stopped due to org.apache.kafka.common.errors.CorruptRecordException

[ https://issues.apache.org/jira/browse/KAFKA-5431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16049156#comment-16049156 ] Carsten Rietz edited comment on KAFKA-5431 at 6/14/17 1:11 PM: -

[jira] [Updated] (KAFKA-5431) LogCleaner stopped due to org.apache.kafka.common.errors.CorruptRecordException

[ https://issues.apache.org/jira/browse/KAFKA-5431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5431: --- Fix Version/s: 0.11.0.1 > LogCleaner stopped due to > org.apache.kafka.common.errors.CorruptRecordExc

[jira] [Updated] (KAFKA-5431) LogCleaner stopped due to org.apache.kafka.common.errors.CorruptRecordException

[ https://issues.apache.org/jira/browse/KAFKA-5431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5431: --- Priority: Critical (was: Major) > LogCleaner stopped due to > org.apache.kafka.common.errors.Corrupt

[jira] [Updated] (KAFKA-5432) producer and consumer SocketTimeoutException

[ https://issues.apache.org/jira/browse/KAFKA-5432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian Lin updated KAFKA-5432: Description: Hey all, I met a strange problem. The program ran normally for a week, and I did not do any cha

[jira] [Commented] (KAFKA-5398) Joins on GlobalKTable don't work properly when combined with Avro and the Confluent Schema Registry

[ https://issues.apache.org/jira/browse/KAFKA-5398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16049190#comment-16049190 ] Benjamin Bargeton commented on KAFKA-5398: -- Actually I continued to dig into Kafk

[jira] [Created] (KAFKA-5446) Annoying braces showed on log.error using streams

Paolo Patierno created KAFKA-5446: - Summary: Annoying braces showed on log.error using streams Key: KAFKA-5446 URL: https://issues.apache.org/jira/browse/KAFKA-5446 Project: Kafka Issue Type

[GitHub] kafka pull request #3338: KAFKA-5446: Annoying braces showed on log.error us...

GitHub user ppatierno opened a pull request: https://github.com/apache/kafka/pull/3338 KAFKA-5446: Annoying braces showed on log.error using streams Fixed log.error usage with annoying braces You can merge this pull request into a Git repository by running: $ git pull https://g

[jira] [Commented] (KAFKA-5446) Annoying braces showed on log.error using streams

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

[jira] [Updated] (KAFKA-5446) Annoying braces showed on log.error using streams

[ https://issues.apache.org/jira/browse/KAFKA-5446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paolo Patierno updated KAFKA-5446: -- Status: Patch Available (was: Open) > Annoying braces showed on log.error using streams >

[jira] [Created] (KAFKA-5447) AdminClient metrics

Ismael Juma created KAFKA-5447: -- Summary: AdminClient metrics Key: KAFKA-5447 URL: https://issues.apache.org/jira/browse/KAFKA-5447 Project: Kafka Issue Type: Improvement Reporter: I

[jira] [Commented] (KAFKA-5447) AdminClient metrics

[ https://issues.apache.org/jira/browse/KAFKA-5447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16049216#comment-16049216 ] Ismael Juma commented on KAFKA-5447: cc [~cmccabe] > AdminClient metrics > --

[jira] [Updated] (KAFKA-5447) AdminClient metrics

[ https://issues.apache.org/jira/browse/KAFKA-5447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5447: --- Labels: needs-kip (was: ) > AdminClient metrics > --- > > Key: KAFKA-

[jira] [Commented] (KAFKA-5431) LogCleaner stopped due to org.apache.kafka.common.errors.CorruptRecordException

[ https://issues.apache.org/jira/browse/KAFKA-5431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16049229#comment-16049229 ] Jun Rao commented on KAFKA-5431: [~crietz], thanks for the info. I guess the preallocated

[jira] [Commented] (KAFKA-5413) Log cleaner fails due to large offset in segment file

[ https://issues.apache.org/jira/browse/KAFKA-5413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16049239#comment-16049239 ] Jun Rao commented on KAFKA-5413: [~Kelvinrutt], thanks for the patch. We normally contribu

[jira] [Updated] (KAFKA-5413) Log cleaner fails due to large offset in segment file

[ https://issues.apache.org/jira/browse/KAFKA-5413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5413: --- Priority: Critical (was: Major) > Log cleaner fails due to large offset in segment file > ---

[jira] [Updated] (KAFKA-5431) LogCleaner stopped due to org.apache.kafka.common.errors.CorruptRecordException

[ https://issues.apache.org/jira/browse/KAFKA-5431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5431: --- Priority: Major (was: Critical) > LogCleaner stopped due to > org.apache.kafka.common.errors.Corrupt

[GitHub] kafka-site pull request #61: Removed hyphens:auto.

GitHub user JNKHunter opened a pull request: https://github.com/apache/kafka-site/pull/61 Removed hyphens:auto. This rule creates misleading setting names on the configuration tables. For example with hyphens: auto we get ``` advertised.lis-teners ``` when the se

[jira] [Commented] (KAFKA-2111) Command Line Standardization - Add Help Arguments & List Required Fields

[ https://issues.apache.org/jira/browse/KAFKA-2111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16049265#comment-16049265 ] Tom Bentley commented on KAFKA-2111: I'm happy work work on this if [~johnma] is no lo

[GitHub] kafka pull request #3323: KAFKA-5354: MirrorMaker not preserving headers

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

[jira] [Commented] (KAFKA-5354) MirrorMaker not preserving headers

[ https://issues.apache.org/jira/browse/KAFKA-5354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16049277#comment-16049277 ] ASF GitHub Bot commented on KAFKA-5354: --- Github user michaelandrepearce closed the p

[GitHub] kafka pull request #3339: KAFKA-5275: AdminClient API consistency

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/3339 KAFKA-5275: AdminClient API consistency You can merge this pull request into a Git repository by running: $ git pull https://github.com/ijuma/kafka kafka-5275-admin-client-api-consistency Alte

[jira] [Commented] (KAFKA-5275) Review and potentially tweak AdminClient API for the initial release (KIP-117)

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

[jira] [Updated] (KAFKA-5275) Review and potentially tweak AdminClient API for the initial release (KIP-117)

[ https://issues.apache.org/jira/browse/KAFKA-5275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5275: --- Status: Patch Available (was: Open) > Review and potentially tweak AdminClient API for the initial re

[jira] [Updated] (KAFKA-5272) Improve validation for Describe/Alter Configs (KIP-133)

[ https://issues.apache.org/jira/browse/KAFKA-5272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5272: --- Fix Version/s: (was: 0.11.0.0) 0.11.0.1 > Improve validation for Describe/Alter

[jira] [Updated] (KAFKA-5276) Support derived and prefixed configs in DescribeConfigs (KIP-133)

[ https://issues.apache.org/jira/browse/KAFKA-5276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5276: --- Fix Version/s: (was: 0.11.0.0) 0.11.0.1 > Support derived and prefixed configs

[jira] [Updated] (KAFKA-5443) Consumer should use last offset from batch to set next fetch offset

[ https://issues.apache.org/jira/browse/KAFKA-5443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5443: --- Status: Patch Available (was: Open) > Consumer should use last offset from batch to set next fetch of

Re: [DISCUSS] KIP-167: Add a restoreAll method to StateRestoreCallback

Thanks Bill, A couple of questions: 1. why do we need both restore and restoreAll, why can't we just have one, that takes a collection (i.e., restore all)? Are there cases when people want to restore one at a time? In that case, they could still use restoreAll with just 1 record in the collec

[jira] [Updated] (KAFKA-5274) Review and improve AdminClient Javadoc for the first release (KIP-117)

[ https://issues.apache.org/jira/browse/KAFKA-5274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-5274: Resolution: Fixed Fix Version/s: 0.11.1.0 Status: Resolved (was: Patch Available)

[GitHub] kafka pull request #3316: KAFKA-5274: AdminClient Javadoc improvements

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

[jira] [Commented] (KAFKA-5274) Review and improve AdminClient Javadoc for the first release (KIP-117)

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

[GitHub] kafka pull request #3276: KAFKA-5361: Add more integration tests for Streams...

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

[jira] [Commented] (KAFKA-5361) Add EOS integration tests for Streams API

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

[GitHub] kafka pull request #3327: HOTFIX: Introduce max wait time for retry-and-back...

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

[jira] [Commented] (KAFKA-5441) Fix transaction marker grouping by producerId in TC

[ https://issues.apache.org/jira/browse/KAFKA-5441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16049349#comment-16049349 ] Guozhang Wang commented on KAFKA-5441: -- I see it is not a blocker for 0.11.0.0, but I

[jira] [Commented] (KAFKA-5445) Document exceptions thrown by AdminClient methods

[ https://issues.apache.org/jira/browse/KAFKA-5445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16049351#comment-16049351 ] Colin P. McCabe commented on KAFKA-5445: We should also add tests that these excep

[jira] [Commented] (KAFKA-5245) KStream builder should capture serdes

[ https://issues.apache.org/jira/browse/KAFKA-5245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16049353#comment-16049353 ] Matthias J. Sax commented on KAFKA-5245: That's a valid point you raise... Not sur

[jira] [Commented] (KAFKA-5398) Joins on GlobalKTable don't work properly when combined with Avro and the Confluent Schema Registry

[ https://issues.apache.org/jira/browse/KAFKA-5398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16049358#comment-16049358 ] Matthias J. Sax commented on KAFKA-5398: I guess, that is expected behavior. I wou

[GitHub] kafka pull request #3312: HOFIX: Introduce max wait time for retry-and-backo...

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

[jira] [Updated] (KAFKA-5443) Consumer should use last offset from batch to set next fetch offset

[ https://issues.apache.org/jira/browse/KAFKA-5443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5443: --- Resolution: Fixed Status: Resolved (was: Patch Available) Issue resolved by pull request 3331

[GitHub] kafka pull request #3331: KAFKA-5443: Consumer should use last offset from b...

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

[jira] [Commented] (KAFKA-5443) Consumer should use last offset from batch to set next fetch offset

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

[GitHub] kafka pull request #3340: MINOR: Add random aborts to system test transactio...

GitHub user hachikuji opened a pull request: https://github.com/apache/kafka/pull/3340 MINOR: Add random aborts to system test transactional copier service You can merge this pull request into a Git repository by running: $ git pull https://github.com/hachikuji/kafka add-rand

[jira] [Commented] (KAFKA-5445) Document exceptions thrown by AdminClient methods

[ https://issues.apache.org/jira/browse/KAFKA-5445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16049406#comment-16049406 ] Ismael Juma commented on KAFKA-5445: Sounds good. > Document exceptions thrown by Adm

[jira] [Created] (KAFKA-5448) TimestampConverter's "type" config conflicts with the basic Transformation "type" config

Ewen Cheslack-Postava created KAFKA-5448: Summary: TimestampConverter's "type" config conflicts with the basic Transformation "type" config Key: KAFKA-5448 URL: https://issues.apache.org/jira/browse/KAFKA-

[jira] [Commented] (KAFKA-5413) Log cleaner fails due to large offset in segment file

[ https://issues.apache.org/jira/browse/KAFKA-5413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16049440#comment-16049440 ] Kelvin Rutt commented on KAFKA-5413: [~junrao], no problem. It might be a couple of da

[jira] [Commented] (KAFKA-5448) TimestampConverter's "type" config conflicts with the basic Transformation "type" config

[ https://issues.apache.org/jira/browse/KAFKA-5448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16049471#comment-16049471 ] David Tucker commented on KAFKA-5448: - I'd suggest something like "target.type" or "ou

[GitHub] kafka pull request #1716: KAFKA-3123: Make abortAndPauseCleaning() a no-op w...

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

[jira] [Commented] (KAFKA-3123) Follower Broker cannot start if offsets are already out of range

[ https://issues.apache.org/jira/browse/KAFKA-3123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16049506#comment-16049506 ] ASF GitHub Bot commented on KAFKA-3123: --- Github user soumyajit-sahu closed the pull

[jira] [Commented] (KAFKA-5245) KStream builder should capture serdes

[ https://issues.apache.org/jira/browse/KAFKA-5245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16049511#comment-16049511 ] Guozhang Wang commented on KAFKA-5245: -- Here is my take on the serde issues: We cur

[jira] [Commented] (KAFKA-5245) KStream builder should capture serdes

[ https://issues.apache.org/jira/browse/KAFKA-5245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16049515#comment-16049515 ] Guozhang Wang commented on KAFKA-5245: -- Anyways [~evis] I have added you to the contr

[jira] [Commented] (KAFKA-5245) KStream builder should capture serdes

[ https://issues.apache.org/jira/browse/KAFKA-5245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16049523#comment-16049523 ] Evgeny Veretennikov commented on KAFKA-5245: [~guozhang], thanks for explanati

[jira] [Updated] (KAFKA-5245) KStream builder should capture serdes

[ https://issues.apache.org/jira/browse/KAFKA-5245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-5245: --- Labels: needs-kip (was: beginner newbie) > KStream builder should capture serdes > -

[jira] [Commented] (KAFKA-5245) KStream builder should capture serdes

[ https://issues.apache.org/jira/browse/KAFKA-5245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16049528#comment-16049528 ] Matthias J. Sax commented on KAFKA-5245: I just did this :) > KStream builder sho

[jira] [Created] (KAFKA-5449) Flaky test TransactionsTest.testReadCommittedConsumerShouldNotSeeUndecidedData

Matthias J. Sax created KAFKA-5449: -- Summary: Flaky test TransactionsTest.testReadCommittedConsumerShouldNotSeeUndecidedData Key: KAFKA-5449 URL: https://issues.apache.org/jira/browse/KAFKA-5449 Proj

[jira] [Assigned] (KAFKA-5449) Flaky test TransactionsTest.testReadCommittedConsumerShouldNotSeeUndecidedData

[ https://issues.apache.org/jira/browse/KAFKA-5449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta reassigned KAFKA-5449: --- Assignee: Apurva Mehta > Flaky test TransactionsTest.testReadCommittedConsumerShouldNotSeeUnd

Build failed in Jenkins: kafka-0.10.2-jdk7 #172

See Changes: [wangguoz] HOFIX: Introduce max wait time for retry-and-backoff while creating -- [...truncated 1.31 MB...] org.apache.kafka.streams.processor.internals.Recor

Re: [DISCUSS] KIP-167: Add a restoreAll method to StateRestoreCallback

Eno, Thanks for the comments. 1. As for having both restore and restoreAll, I kept the restore method for backward compatibility as that is what is used by current implementing classes. However as I think about it makes things cleaner to have a single restore method taking a collection. I'll wait

[jira] [Commented] (KAFKA-5440) Kafka Streams report state RUNNING even if all threads are dead

[ https://issues.apache.org/jira/browse/KAFKA-5440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16049574#comment-16049574 ] Guozhang Wang commented on KAFKA-5440: -- This is a good find, and maybe it is related

[jira] [Commented] (KAFKA-5430) new consumers getting data for revoked partitions

[ https://issues.apache.org/jira/browse/KAFKA-5430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16049582#comment-16049582 ] Vahid Hashemian commented on KAFKA-5430: I could simulate a network failure and ge

Re: [DISCUSS] KIP-167: Add a restoreAll method to StateRestoreCallback

Thanks Bill for the updated wiki. I have a couple of more comments: 1. Setting StateRestoreListener on the KafkaStreams granularity may not be sufficient, as in the listener callback we do not which store it is restoring right now: if the topic is a changelog topic then from the `TopicPartition` w

[GitHub] kafka-site issue #60: Update delivery semantics section for KIP-98

Github user hachikuji commented on the issue: https://github.com/apache/kafka-site/pull/60 @guozhangwang @ijuma @apurvam Pushed a couple changes based on the review. Please take another look. --- If your project is set up for it, you can reply to this email and have your reply appear

[jira] [Assigned] (KAFKA-5446) Annoying braces showed on log.error using streams

[ https://issues.apache.org/jira/browse/KAFKA-5446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang reassigned KAFKA-5446: Assignee: Paolo Patierno > Annoying braces showed on log.error using streams > ---

[jira] [Updated] (KAFKA-5446) Annoying braces showed on log.error using streams

[ https://issues.apache.org/jira/browse/KAFKA-5446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-5446: - Affects Version/s: 0.11.0.0 > Annoying braces showed on log.error using streams > ---

[GitHub] kafka pull request #3341: MINOR: Update `TransactionMarkerChannelManager` me...

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/3341 MINOR: Update `TransactionMarkerChannelManager` metric name Also remove broker-id tags as we generally use them to provide additional context. Finally, do a few clean-ups (could not resist

[GitHub] kafka-site issue #60: Update delivery semantics section for KIP-98

Github user guozhangwang commented on the issue: https://github.com/apache/kafka-site/pull/60 lgtm. --- 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 t

Re: [DISCUSS]: KIP-149: Enabling key access in ValueTransformer, ValueMapper, and ValueJoiner

I'm not particularly concerning that we should NEVER break compatibility; in fact if we think that is worthwhile (i.e. small impact with large benefit) I think we can break compatibility as long as we have not removed the compatibility annotations from Streams. All I was saying is that if we decide

[GitHub] kafka pull request #3342: KAFKA-5448: Change TimestampConverter configuratio...

GitHub user ewencp opened a pull request: https://github.com/apache/kafka/pull/3342 KAFKA-5448: Change TimestampConverter configuration name to avoid conflicting with reserved 'type' configuration used by all Transformations You can merge this pull request into a Git repository by

[jira] [Commented] (KAFKA-5448) TimestampConverter's "type" config conflicts with the basic Transformation "type" config

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

[GitHub] kafka pull request #3343: WIP: KAFKA-5449: fix bad state transition in trans...

GitHub user apurvam opened a pull request: https://github.com/apache/kafka/pull/3343 WIP: KAFKA-5449: fix bad state transition in transaction manager The `kafka.api.TransactionsTest.testReadCommittedConsumerShouldNotSeeUndecidedData` very rarely sees the following. I have

[jira] [Commented] (KAFKA-5449) Flaky test TransactionsTest.testReadCommittedConsumerShouldNotSeeUndecidedData

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

Re: [DISCUSS] KIP-150 - Kafka-Streams Cogroup

I'd suggest we do not block this KIP until the serde work has been sorted out: we cannot estimate yet how long it will take yet. Instead let's say make an agreement on where we want to specify the serdes: whether on the first co-group call or on the aggregate call. Also about the initializer speci

Re: [DISCUSS]: KIP-159: Introducing Rich functions to Streams

LGTM. Thanks! Guozhang On Tue, Jun 13, 2017 at 2:20 PM, Jeyhun Karimov wrote: > Thanks for the comment Matthias. After all the discussion (thanks to all > participants), I think this (single method that passes in a RecordContext > object) is the best alternative. > Just a side note: I think KA

[jira] [Created] (KAFKA-5450) Scripts to startup Connect in system tests have too short a timeout

Randall Hauch created KAFKA-5450: Summary: Scripts to startup Connect in system tests have too short a timeout Key: KAFKA-5450 URL: https://issues.apache.org/jira/browse/KAFKA-5450 Project: Kafka

Re: [DISCUSS] KIP-167: Add a restoreAll method to StateRestoreCallback

Guozhang, Thanks for the comments. 1. As for the granularity, I agree that having one global StateRestoreListener could be restrictive. But I think it's important to have a "setStateRestoreListener" on KafkaStreams as this allows users to define an anonymous instance that has access to local sc

[GitHub] kafka pull request #3344: KAFKA-5450 Increased timeout of Connect system tes...

GitHub user rhauch opened a pull request: https://github.com/apache/kafka/pull/3344 KAFKA-5450 Increased timeout of Connect system test utilities Increased the timeout from 30sec to 60sec. When running the system tests with packaged Kafka, Connect workers can take about 30seconds to

[jira] [Commented] (KAFKA-5450) Scripts to startup Connect in system tests have too short a timeout

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

  1   2   >