[GitHub] kafka pull request #3184: KAFKA-5351: Reset pending state when returning an ...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3184 --- 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] [Updated] (KAFKA-5351) Broker clean bounce test puts the broker into a 'CONCURRENT_TRANSACTIONS' state permanently

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

[jira] [Commented] (KAFKA-5322) Resolve AddPartitions response error code inconsistency

[ https://issues.apache.org/jira/browse/KAFKA-5322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16032485#comment-16032485 ] Jason Gustafson commented on KAFKA-5322: [~guozhang] That sounds good to me. I'll go ahead and

[jira] [Resolved] (KAFKA-5321) MemoryRecords.filterTo can return corrupt data if output buffer is not large enough

[ https://issues.apache.org/jira/browse/KAFKA-5321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-5321. Resolution: Fixed We decided to fix this in KAFKA-5316. > MemoryRecords.filterTo can

[jira] [Commented] (KAFKA-1595) Remove deprecated and slower scala JSON parser from kafka.consumer.TopicCount

[ https://issues.apache.org/jira/browse/KAFKA-1595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16032478#comment-16032478 ] Guozhang Wang commented on KAFKA-1595: -- Sounds great. If [~ijuma] is fine with it feel free to fork

[jira] [Updated] (KAFKA-5322) Resolve AddPartitions response error code inconsistency

[ https://issues.apache.org/jira/browse/KAFKA-5322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriram Subramanian updated KAFKA-5322: -- Labels: exactly-once (was: ) > Resolve AddPartitions response error code inconsistency

[jira] [Work started] (KAFKA-5019) Exactly-once upgrade notes

[ https://issues.apache.org/jira/browse/KAFKA-5019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-5019 started by Jason Gustafson. -- > Exactly-once upgrade notes > -- > >

[jira] [Updated] (KAFKA-5357) StackOverFlow error in transaction coordinator

[ https://issues.apache.org/jira/browse/KAFKA-5357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5357: Attachment: KAFKA-5357.tar.gz > StackOverFlow error in transaction coordinator >

[jira] [Commented] (KAFKA-5357) StackOverFlow error in transaction coordinator

[ https://issues.apache.org/jira/browse/KAFKA-5357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16032470#comment-16032470 ] Apurva Mehta commented on KAFKA-5357: - The upshot of this ticket is that the commit of a transaction

[jira] [Created] (KAFKA-5358) Consumer perf tool should count rebalance time separately

Jason Gustafson created KAFKA-5358: -- Summary: Consumer perf tool should count rebalance time separately Key: KAFKA-5358 URL: https://issues.apache.org/jira/browse/KAFKA-5358 Project: Kafka

[jira] [Created] (KAFKA-5357) StackOverFlow error in transaction coordinator

Apurva Mehta created KAFKA-5357: --- Summary: StackOverFlow error in transaction coordinator Key: KAFKA-5357 URL: https://issues.apache.org/jira/browse/KAFKA-5357 Project: Kafka Issue Type: Bug

[jira] [Commented] (KAFKA-5340) Add additional test cases for batch splitting to ensure idempotent/transactional metadata is preserved

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

[jira] [Updated] (KAFKA-5340) Add additional test cases for batch splitting to ensure idempotent/transactional metadata is preserved

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

[GitHub] kafka pull request #3162: KAFKA-5340: Batch splitting should preserve magic ...

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

See Changes: [wangguoz] KAFKA-5350: Modify unstable annotations in Streams API [wangguoz] KAFKA-5226; Fixes issue where adding topics matching a regex -- [...truncated

[DISCUSS] KIP-166 Add a tool to make amounts of replicas and leaders on brokers balanced

Hi, We created KIP-166 to propose adding a tool to balance amounts of replicas and leaders on brokers. The KIP wiki can be found at https://cwiki.apache.org/confluence/display/KAFKA/KIP-166+-+Add+a+tool+to+make+amounts+of+replicas+and+leaders+on+brokers+balanced And the JIRA is KAFKA-5319

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

See Changes: [ismael] KAFKA-5291; AdminClient should not trigger auto creation of topics -- [...truncated 909.59 KB...] kafka.admin.ConfigCommandTest >

[jira] [Commented] (KAFKA-5226) NullPointerException (NPE) in SourceNodeRecordDeserializer.deserialize

[ https://issues.apache.org/jira/browse/KAFKA-5226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16032345#comment-16032345 ] Guozhang Wang commented on KAFKA-5226: -- [~ian.springer] The fix has just been merged into trunk and

[jira] [Commented] (KAFKA-5226) NullPointerException (NPE) in SourceNodeRecordDeserializer.deserialize

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

[jira] [Updated] (KAFKA-5226) NullPointerException (NPE) in SourceNodeRecordDeserializer.deserialize

[ https://issues.apache.org/jira/browse/KAFKA-5226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-5226: - Resolution: Fixed Fix Version/s: (was: 0.11.0.1) 0.11.0.0

[GitHub] kafka pull request #3157: KAFKA-5226: Fixes issue where adding topics matchi...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3157 --- 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 #3185: MINOR: Logging/debugging improvements for transact...

GitHub user hachikuji opened a pull request: https://github.com/apache/kafka/pull/3185 MINOR: Logging/debugging improvements for transactions You can merge this pull request into a Git repository by running: $ git pull https://github.com/hachikuji/kafka

[jira] [Commented] (KAFKA-5350) Modify Unstable annotations in Streams API

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

[GitHub] kafka pull request #3172: KAFKA-5350: Modify unstable annotations in Streams...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3172 --- 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-5350) Modify Unstable annotations in Streams API

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

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

See

[jira] [Comment Edited] (KAFKA-1595) Remove deprecated and slower scala JSON parser from kafka.consumer.TopicCount

[ https://issues.apache.org/jira/browse/KAFKA-1595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16032276#comment-16032276 ] Onur Karaman edited comment on KAFKA-1595 at 6/1/17 12:50 AM: -- I think

[jira] [Commented] (KAFKA-1595) Remove deprecated and slower scala JSON parser from kafka.consumer.TopicCount

[ https://issues.apache.org/jira/browse/KAFKA-1595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16032276#comment-16032276 ] Onur Karaman commented on KAFKA-1595: - I think [~ijuma]'s PR (https://github.com/apache/kafka/pull/83)

Jenkins build is back to normal : kafka-0.11.0-jdk7 #63

See

[jira] [Commented] (KAFKA-4592) Kafka Producer Metrics Invalid Value

[ https://issues.apache.org/jira/browse/KAFKA-4592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16032261#comment-16032261 ] Jun Rao commented on KAFKA-4592: [~huxi], sorry for the late response. If a metric is never updated,

[jira] [Commented] (KAFKA-5291) AdminClient should not trigger auto creation of topics

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

[jira] [Updated] (KAFKA-5291) AdminClient should not trigger auto creation of topics

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

[GitHub] kafka pull request #3098: KAFKA-5291: AdminClient should not trigger auto cr...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3098 --- 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] [Updated] (KAFKA-5270) TransactionManager should send and `AddOffsetsToTxn` request only once per group per transaction

[ https://issues.apache.org/jira/browse/KAFKA-5270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-5270: --- Fix Version/s: (was: 0.11.0.0) 0.11.1.0 > TransactionManager should

[jira] [Updated] (KAFKA-4487) Tests should be run in Jenkins with INFO or DEBUG level

[ https://issues.apache.org/jira/browse/KAFKA-4487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4487: --- Fix Version/s: (was: 0.11.0.0) 0.11.1.0 > Tests should be run in Jenkins with

[jira] [Updated] (KAFKA-4628) Support KTable/GlobalKTable Joins

[ https://issues.apache.org/jira/browse/KAFKA-4628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4628: --- Fix Version/s: (was: 0.11.0.0) 0.11.1.0 > Support KTable/GlobalKTable Joins >

[jira] [Updated] (KAFKA-5356) Producer with transactionalId should be able to send outside of a transaction

[ https://issues.apache.org/jira/browse/KAFKA-5356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5356: --- Fix Version/s: (was: 0.11.0.0) 0.11.1.0 > Producer with transactionalId should

[jira] [Updated] (KAFKA-5293) Do not apply exponential backoff if users have overridden reconnect.backoff.ms

[ https://issues.apache.org/jira/browse/KAFKA-5293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5293: --- Status: Patch Available (was: Open) > Do not apply exponential backoff if users have overridden

Build failed in Jenkins: kafka-0.11.0-jdk7 #62

See Changes: [wangguoz] MINOR: Improve streams config parameters [wangguoz] KAFKA-5218; New Short serializer, deserializer, serde -- [...truncated 905.87 KB...]

[jira] [Updated] (KAFKA-5353) baseTimestamp should always have a create timestamp

[ https://issues.apache.org/jira/browse/KAFKA-5353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5353: --- Summary: baseTimestamp should always have a create timestamp (was: Set baseTimestamp correctly if

[jira] [Updated] (KAFKA-5353) baseTimestamp should always have a create timestamp

[ https://issues.apache.org/jira/browse/KAFKA-5353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5353: --- Description: This makes the case where we build the records from scratch consistent with the case

[jira] [Commented] (KAFKA-5353) baseTimestamp should always have a create timestamp

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

[GitHub] kafka pull request #3177: KAFKA-5353: baseTimestamp should always have a cre...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3177 --- 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-5353) Set baseTimestamp correctly if log append time and no broker recompression

[ https://issues.apache.org/jira/browse/KAFKA-5353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-5353. Resolution: Fixed Issue resolved by pull request 3177 [https://github.com/apache/kafka/pull/3177]

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

See Changes: [jason] KAFKA-5093; Avoid loading full batch data when possible when iterating -- [...truncated 4.06 MB...] kafka.utils.UtilsTest > testCsvMap PASSED

[GitHub] kafka pull request #3182: MINOR: Use `waitUntil` to fix transient failures o...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3182 --- 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] [Updated] (KAFKA-5351) Broker clean bounce test puts the broker into a 'CONCURRENT_TRANSACTIONS' state permanently

[ https://issues.apache.org/jira/browse/KAFKA-5351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5351: Status: Patch Available (was: Open) > Broker clean bounce test puts the broker into a

[jira] [Updated] (KAFKA-5218) New Short serializer, deserializer, serde

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

[jira] [Commented] (KAFKA-5218) New Short serializer, deserializer, serde

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

[GitHub] kafka pull request #3017: KAFKA-5218: New Short serializer, deserializer, se...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3017 --- 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-5351) Broker clean bounce test puts the broker into a 'CONCURRENT_TRANSACTIONS' state permanently

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

[jira] [Updated] (KAFKA-5355) Broker returns messages beyond "latest stable offset" to transactional consumer in read_committed mode

[ https://issues.apache.org/jira/browse/KAFKA-5355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-5355: --- Issue Type: Sub-task (was: Bug) Parent: KAFKA-4815 > Broker returns messages beyond

[GitHub] kafka pull request #3184: KAFKA-5351: Reset pending state when returning an ...

GitHub user apurvam opened a pull request: https://github.com/apache/kafka/pull/3184 KAFKA-5351: Reset pending state when returning an error in appendTransactionToLog Without this patch, future client retries would get the `CONCURRENT_TRANSACTIONS` error code indefinitely, since

[GitHub] kafka pull request #2855: Minor improve streams config parameters

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2855 --- 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-4566) Can't Symlink to Kafka bins

[ https://issues.apache.org/jira/browse/KAFKA-4566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16032048#comment-16032048 ] Jim Jagielski commented on KAFKA-4566: -- Since this is a shell, we can check which OS we are on, and

[jira] [Assigned] (KAFKA-5355) Broker returns messages beyond "latest stable offset" to transactional consumer in read_committed mode

[ https://issues.apache.org/jira/browse/KAFKA-5355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson reassigned KAFKA-5355: -- Assignee: Jason Gustafson > Broker returns messages beyond "latest stable offset" to

[jira] [Created] (KAFKA-5356) Producer with transactionalId should be able to send outside of a transaction

Jason Gustafson created KAFKA-5356: -- Summary: Producer with transactionalId should be able to send outside of a transaction Key: KAFKA-5356 URL: https://issues.apache.org/jira/browse/KAFKA-5356

[jira] [Updated] (KAFKA-5355) Broker returns messages beyond "latest stable offset" to transactional consumer in read_committed mode

[ https://issues.apache.org/jira/browse/KAFKA-5355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5355: Summary: Broker returns messages beyond "latest stable offset" to transactional consumer in

[jira] [Created] (KAFKA-5355) Broker returns messages beyond "latest stable offset" to transactional consumer

Matthias J. Sax created KAFKA-5355: -- Summary: Broker returns messages beyond "latest stable offset" to transactional consumer Key: KAFKA-5355 URL: https://issues.apache.org/jira/browse/KAFKA-5355

[jira] [Updated] (KAFKA-5355) Broker returns messages beyond "latest stable offset" to transactional consumer

[ https://issues.apache.org/jira/browse/KAFKA-5355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-5355: --- Fix Version/s: 0.11.0.0 > Broker returns messages beyond "latest stable offset" to

[jira] [Commented] (KAFKA-5093) Load only batch header when rebuilding producer ID map

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

[GitHub] kafka pull request #3160: KAFKA-5093: Avoid loading full batch data when pos...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3160 --- 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] [Updated] (KAFKA-5093) Load only batch header when rebuilding producer ID map

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

[jira] [Commented] (KAFKA-5283) Update clients and server code to make sure that epoch and sequence numbers wrap around

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

[jira] [Updated] (KAFKA-5283) Update clients and server code to make sure that epoch and sequence numbers wrap around

[ https://issues.apache.org/jira/browse/KAFKA-5283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-5283: --- Status: Patch Available (was: Open) > Update clients and server code to make sure that epoch

[GitHub] kafka pull request #3183: KAFKA-5283: Handle producer epoch/sequence overflo...

GitHub user hachikuji opened a pull request: https://github.com/apache/kafka/pull/3183 KAFKA-5283: Handle producer epoch/sequence overflow by wrapping around You can merge this pull request into a Git repository by running: $ git pull https://github.com/hachikuji/kafka

[jira] [Commented] (KAFKA-2526) Console Producer / Consumer's serde config is not working

[ https://issues.apache.org/jira/browse/KAFKA-2526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16031849#comment-16031849 ] Guozhang Wang commented on KAFKA-2526: -- [~huxi_2b] are you picking this up? > Console Producer /

[jira] [Updated] (KAFKA-5112) Trunk compatibility tests should test against 0.10.2

[ https://issues.apache.org/jira/browse/KAFKA-5112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5112: --- Status: Patch Available (was: Open) > Trunk compatibility tests should test against 0.10.2 >

[jira] [Updated] (KAFKA-5112) Trunk compatibility tests should test against 0.10.2

[ https://issues.apache.org/jira/browse/KAFKA-5112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5112: --- Priority: Blocker (was: Major) > Trunk compatibility tests should test against 0.10.2 >

[jira] [Updated] (KAFKA-5112) Trunk compatibility tests should test against 0.10.2

[ https://issues.apache.org/jira/browse/KAFKA-5112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5112: --- Fix Version/s: 0.11.0.0 > Trunk compatibility tests should test against 0.10.2 >

[jira] [Commented] (KAFKA-5351) Broker clean bounce test puts the broker into a 'CONCURRENT_TRANSACTIONS' state permanently

[ https://issues.apache.org/jira/browse/KAFKA-5351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16031764#comment-16031764 ] Apurva Mehta commented on KAFKA-5351: - [~guozhang] here are all the logs from a pertinent failure:

[jira] [Updated] (KAFKA-5351) Broker clean bounce test puts the broker into a 'CONCURRENT_TRANSACTIONS' state permanently

[ https://issues.apache.org/jira/browse/KAFKA-5351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5351: Attachment: kafka-5351.logs.tar.gz > Broker clean bounce test puts the broker into a

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

Hello all, I have spent some more time on this and the best alternative I have come up with is: KGroupedStream has a single cogroup call that takes an initializer and an aggregator. CogroupedKStream has a cogroup call that takes additional groupedStream aggregator pairs. CogroupedKStream has

[jira] [Assigned] (KAFKA-5283) Update clients and server code to make sure that epoch and sequence numbers wrap around

[ https://issues.apache.org/jira/browse/KAFKA-5283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson reassigned KAFKA-5283: -- Assignee: Jason Gustafson > Update clients and server code to make sure that epoch and

[jira] [Updated] (KAFKA-5340) Add additional test cases for batch splitting to ensure idempotent/transactional metadata is preserved

[ https://issues.apache.org/jira/browse/KAFKA-5340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5340: Labels: exactly-once (was: ) Priority: Blocker (was: Major) > Add additional test cases for

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

See

[jira] [Assigned] (KAFKA-3623) Make KStreamTestDriver extending from ExternalResource

[ https://issues.apache.org/jira/browse/KAFKA-3623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mariam John reassigned KAFKA-3623: -- Assignee: Mariam John > Make KStreamTestDriver extending from ExternalResource >

[GitHub] kafka pull request #3182: MINOR: Use `waitUntil` to fix transient failures o...

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/3182 MINOR: Use `waitUntil` to fix transient failures of ControllerFailoverTest Without it, it's possible that the assertion is checked before the exception is thrown in the callback. You can merge

Re: Kafka Connect Parquet Support?

Hi Clayton, It seems like an interesting improvement. Given that Parquet is columnar, you would expect some space savings. I guess the big question is, would each batch of records become a single parquet file? And how does this integrate with the existing logic, which might assume that each

[jira] [Resolved] (KAFKA-5159) Update Kafka documentation to mention AdminClient

[ https://issues.apache.org/jira/browse/KAFKA-5159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin P. McCabe resolved KAFKA-5159. Resolution: Duplicate > Update Kafka documentation to mention AdminClient >

[jira] [Commented] (KAFKA-4064) Add support for infinite endpoints for range queries in Kafka Streams KV stores

[ https://issues.apache.org/jira/browse/KAFKA-4064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16031608#comment-16031608 ] Xavier Léauté commented on KAFKA-4064: -- [~ijuma] [~guozhang] we haven't done the KIP for this. > Add

[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=16031603#comment-16031603 ] Jun Rao commented on KAFKA-5354: [~michael.andre.pearce], could you confirm if this is indeed an issue? >

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

Jun Rao created KAFKA-5354: -- Summary: MirrorMaker not preserving headers Key: KAFKA-5354 URL: https://issues.apache.org/jira/browse/KAFKA-5354 Project: Kafka Issue Type: Bug Affects Versions:

[jira] [Commented] (KAFKA-4064) Add support for infinite endpoints for range queries in Kafka Streams KV stores

[ https://issues.apache.org/jira/browse/KAFKA-4064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16031598#comment-16031598 ] Guozhang Wang commented on KAFKA-4064: -- [~ijuma] I will update the fix version. > Add support for

[jira] [Updated] (KAFKA-4064) Add support for infinite endpoints for range queries in Kafka Streams KV stores

[ https://issues.apache.org/jira/browse/KAFKA-4064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-4064: - Fix Version/s: (was: 0.11.0.0) 0.11.1.0 > Add support for infinite

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

See -- [...truncated 904.32 KB...] kafka.integration.PrimitiveApiTest > testMultiProduce PASSED kafka.integration.PrimitiveApiTest > testDefaultEncoderProducerAndFetch STARTED

[jira] [Assigned] (KAFKA-5319) Add a tool to make cluster replica and leader balance

[ https://issues.apache.org/jira/browse/KAFKA-5319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang reassigned KAFKA-5319: Assignee: Ma Tianchi > Add a tool to make cluster replica and leader balance >

[jira] [Commented] (KAFKA-5154) Kafka Streams throws NPE during rebalance

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

[GitHub] kafka pull request #3181: KAFKA-5154: Consumer fetches from revoked partitio...

GitHub user dguy opened a pull request: https://github.com/apache/kafka/pull/3181 KAFKA-5154: Consumer fetches from revoked partitions when SyncGroup fails with disconnection [WIP] Scenario is as follows: 1. Consumer subscribes to topic t1 and begins consuming 2. heartbeat

Re: Request a permission to KIP

Tianchi, You should be able to create new wiki pages now. Guozhang On Tue, May 30, 2017 at 8:31 PM, Ma Tianchi wrote: > Hi, > I want to get a permission to add a KIP.My wiki username is marktcma. > Tahnks. -- -- Guozhang

[jira] [Commented] (KAFKA-5150) LZ4 decompression is 4-5x slower than Snappy on small batches / messages

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

[GitHub] kafka pull request #3180: MINOR: reuse decompression buffers in log cleaner

GitHub user xvrl opened a pull request: https://github.com/apache/kafka/pull/3180 MINOR: reuse decompression buffers in log cleaner follow-up to KAFKA-5150, reuse decompression buffers in the log cleaner thread. @ijuma @hachikuji You can merge this pull request into a

[jira] [Resolved] (KAFKA-5265) Move ACLs, Config, NodeVersions classes into org.apache.kafka.common

[ https://issues.apache.org/jira/browse/KAFKA-5265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-5265. Resolution: Fixed Issue resolved by pull request 3120 [https://github.com/apache/kafka/pull/3120]

[GitHub] kafka pull request #3120: Kafka 5265

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3120 --- 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-5352) Support automatic restart of failed tasks

[ https://issues.apache.org/jira/browse/KAFKA-5352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16031472#comment-16031472 ] Randall Hauch commented on KAFKA-5352: -- Potentially related to KAFKA-3819, and it's possible a single

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

See

[jira] [Updated] (KAFKA-5339) Transactions system test with hard broker bounces fails sporadically

[ https://issues.apache.org/jira/browse/KAFKA-5339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5339: Priority: Major (was: Blocker) > Transactions system test with hard broker bounces fails

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

See Changes: [ismael] MINOR: Use new consumer in ProducerCompressionTest -- [...truncated 903.56 KB...] kafka.integration.PrimitiveApiTest > testMultiProduce PASSED

[GitHub] kafka pull request #3178: MINOR: Use new consumer in ProducerCompressionTest

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3178 --- 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 #3179: MINOR: update stream docs for kip-134

GitHub user dguy opened a pull request: https://github.com/apache/kafka/pull/3179 MINOR: update stream docs for kip-134 Add a section in the streams docs about the broker config introduced in KIP-134 You can merge this pull request into a Git repository by running: $ git pull

  1   2   >