[jira] [Commented] (KAFKA-2651) Remove deprecated config alteration from TopicCommand in 0.9.1.0

[ https://issues.apache.org/jira/browse/KAFKA-2651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16015313#comment-16015313 ] Manikumar commented on KAFKA-2651: -- [~ijuma] We have deprecated the alter config in 0.9.0

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

See Changes: [ismael] KAFKA-3267; Describe and Alter Configs Admin APIs (KIP-133) [wangguoz] KAFKA-5210: Application Reset Tool does not need to seek for internal -- [...

[jira] [Commented] (KAFKA-3514) Stream timestamp computation needs some further thoughts

[ https://issues.apache.org/jira/browse/KAFKA-3514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16015410#comment-16015410 ] Sinóros-Szabó Péter commented on KAFKA-3514: Considering the above ideas, I wo

[jira] [Comment Edited] (KAFKA-3514) Stream timestamp computation needs some further thoughts

[ https://issues.apache.org/jira/browse/KAFKA-3514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16015410#comment-16015410 ] Sinóros-Szabó Péter edited comment on KAFKA-3514 at 5/18/17 8:15 AM: ---

[GitHub] kafka pull request #3085: KAFKA-4830: Augment KStream.print() to allow users...

GitHub user jedichien opened a pull request: https://github.com/apache/kafka/pull/3085 KAFKA-4830: Augment KStream.print() to allow users pass in extra parameters in the printed string I extend `KStream#print()` to `KStream#print(KeyValueMapper)`. So I add the following methods

[jira] [Commented] (KAFKA-4830) Augment KStream.print() to allow users pass in extra parameters in the printed string

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

[jira] [Commented] (KAFKA-4830) Augment KStream.print() to allow users pass in extra parameters in the printed string

[ https://issues.apache.org/jira/browse/KAFKA-4830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16015486#comment-16015486 ] james chien commented on KAFKA-4830: [~mjsax] I just make a new PR. https://github.com

[GitHub] kafka pull request #3084: TRIVIAL: Remove redundant asMap utility in Consume...

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

[GitHub] kafka pull request #3080: KAFKA-4222: QueryableIntegrationTest.queryOnRebala...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3080 --- 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-4222) Transient failure in QueryableStateIntegrationTest.queryOnRebalance

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

[GitHub] kafka pull request #3071: KAFKA-5258: move all partition and replica state t...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3071 --- 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] [Updated] (KAFKA-5258) move all partition and replica state transition rules into their states

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

[jira] [Commented] (KAFKA-5258) move all partition and replica state transition rules into their states

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

[jira] [Resolved] (KAFKA-4222) Transient failure in QueryableStateIntegrationTest.queryOnRebalance

[ https://issues.apache.org/jira/browse/KAFKA-4222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-4222. Resolution: Fixed Assignee: Damian Guy (was: Eno Thereska) > Transient failure in QueryableSt

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

[ https://issues.apache.org/jira/browse/KAFKA-5154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy updated KAFKA-5154: -- Attachment: 5154_problem.log > Kafka Streams throws NPE during rebalance > -

[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&focusedCommentId=16015615#comment-16015615 ] Damian Guy commented on KAFKA-5154: --- [~Lukas Gemela] Thanks for attaching the full logs.

[GitHub] kafka pull request #3086: KAFKA-5171 : TC should not accept empty string tra...

GitHub user umesh9794 opened a pull request: https://github.com/apache/kafka/pull/3086 KAFKA-5171 : TC should not accept empty string transactional id This a rebase version of [PR#2973](https://github.com/apache/kafka/pull/2973). @guozhangwang , please review this updated

[jira] [Commented] (KAFKA-5171) TC should not accept empty string transactional id

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

[jira] [Assigned] (KAFKA-4291) TopicCommand --describe shows topics marked for deletion as under-replicated and unavailable (KIP-137)

[ https://issues.apache.org/jira/browse/KAFKA-4291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reassigned KAFKA-4291: -- Assignee: Ismael Juma (was: Mickael Maison) > TopicCommand --describe shows topics marked for

[jira] [Updated] (KAFKA-4291) TopicCommand --describe shows topics marked for deletion as under-replicated and unavailable (KIP-137)

[ https://issues.apache.org/jira/browse/KAFKA-4291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4291: --- Labels: kip (was: ) > TopicCommand --describe shows topics marked for deletion as under-replicated >

[jira] [Updated] (KAFKA-4291) TopicCommand --describe shows topics marked for deletion as under-replicated and unavailable (KIP-137)

[ https://issues.apache.org/jira/browse/KAFKA-4291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4291: --- Summary: TopicCommand --describe shows topics marked for deletion as under-replicated and unavailable

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

See

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

See Changes: [ismael] KAFKA-4222; QueryableIntegrationTest.queryOnRebalance transient failure [ismael] KAFKA-5258; Move all partition and replica state transition rules into

Re: [VOTE] KIP 130: Expose states of active tasks to KafkaStreams public API

Hi all, I've finally found time to update the KIP. The toString() is annotated as deprecated. I have also rebase the PR with the current trunk. So sorry to have been so long on this KIP. Thanks. 2017-04-24 18:56 GMT+02:00 Guozhang Wang : > Florian, could you also add the part of deprecating `Ka

[GitHub] kafka pull request #3087: MINOR: Small refactor of request quotas handling i...

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/3087 MINOR: Small refactor of request quotas handling in KafkaApis - Avoid unnecessary inner methods - Remove redundant parameter in `sendResponseExemptThrottle` - Go through `sendResponseExemptThro

[jira] [Commented] (KAFKA-5256) Non-checkpointed state stores should be deleted before restore

[ https://issues.apache.org/jira/browse/KAFKA-5256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16015805#comment-16015805 ] Damian Guy commented on KAFKA-5256: --- >From 0.11.0 onwards we will always have a checkpoi

[jira] [Assigned] (KAFKA-5266) Follow-up improvements for consumer offset reset tool (KIP-122)

[ https://issues.apache.org/jira/browse/KAFKA-5266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jorge Quilcate reassigned KAFKA-5266: - Assignee: Jorge Quilcate > Follow-up improvements for consumer offset reset tool (KIP-122

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

See Changes: [ismael] KAFKA-4222; QueryableIntegrationTest.queryOnRebalance transient failure [ismael] KAFKA-5258; Move all partition and replica state transition rules into

Re: [VOTE] KIP 130: Expose states of active tasks to KafkaStreams public API

+1 On Thu, May 18, 2017 at 6:54 AM, Florian Hussonnois wrote: > Hi all, > > I've finally found time to update the KIP. The toString() is annotated as > deprecated. I have also rebase the PR with the current trunk. > So sorry to have been so long on this KIP. > > Thanks. > > 2017-04-24 18:56 GMT+

[GitHub] kafka pull request #3088: 0.10.2

GitHub user dwshmilyss opened a pull request: https://github.com/apache/kafka/pull/3088 0.10.2 pull You can merge this pull request into a Git repository by running: $ git pull https://github.com/apache/kafka 0.10.2 Alternatively you can review and apply these changes as the

[jira] [Commented] (KAFKA-4830) Augment KStream.print() to allow users pass in extra parameters in the printed string

[ https://issues.apache.org/jira/browse/KAFKA-4830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16016046#comment-16016046 ] Matthias J. Sax commented on KAFKA-4830: Thanks for working on this [~james.c]. As

Re: [VOTE] KIP-137: Enhance TopicCommand --describe to show topics marked for deletion

I've made a small modification to the KIP. When running TopicCommand with --unavailable-partitions or --under-replicated-partitions the topic header is not displayed. In that case, the deletion marker will be added on the same line as the partition. https://cwiki.apache.org/confluence/display/KAF

[GitHub] kafka pull request #3089: KAFKA-5268: Fix bounce test transient failure by c...

GitHub user hachikuji opened a pull request: https://github.com/apache/kafka/pull/3089 KAFKA-5268: Fix bounce test transient failure by clearing partitions before writing Complete state to transaction log You can merge this pull request into a Git repository by running: $ git

[jira] [Commented] (KAFKA-5268) TransactionsBounceTest occasionally sees INVALID_TXN_STATE errors

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

[jira] [Commented] (KAFKA-3356) Remove ConsumerOffsetChecker, deprecated in 0.9, in 0.11

[ https://issues.apache.org/jira/browse/KAFKA-3356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16016095#comment-16016095 ] Mickael Maison commented on KAFKA-3356: --- I agree too, but I still think knowing the

[jira] [Created] (KAFKA-5278) kafka-console-consumer: `--value-deserializer` is not working but `--property value.deserializer` does

Yeva Byzek created KAFKA-5278: - Summary: kafka-console-consumer: `--value-deserializer` is not working but `--property value.deserializer` does Key: KAFKA-5278 URL: https://issues.apache.org/jira/browse/KAFKA-5278

[jira] [Updated] (KAFKA-5278) kafka-console-consumer: `--value-deserializer` is not working but `--property value.deserializer` does

[ https://issues.apache.org/jira/browse/KAFKA-5278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yeva Byzek updated KAFKA-5278: -- Description: kafka-console-consumer: {{--value-deserializer}} is not working but {{--property value.des

[jira] [Updated] (KAFKA-5278) kafka-console-consumer: `--value-deserializer` is not working but `--property value.deserializer` does

[ https://issues.apache.org/jira/browse/KAFKA-5278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yeva Byzek updated KAFKA-5278: -- Description: kafka-console-consumer: {{--value-deserializer}} is not working but {{--property value.des

Java Client Builder pattern for ProducerRecord - thoughts?

Hi all, The `ProducerRecord` type has many optional fields and the list has grown over different revisions of Kafka. Kafka supports `ProducerInterceptor`s, which often need to construct new `ProducerRecord`s, based on those passed in, copying most fields from the old to the new record, e.g.: `

[jira] [Updated] (KAFKA-5128) TransactionCoordinator - Check inter broker protocol and message format and raise errors if incompatible

[ https://issues.apache.org/jira/browse/KAFKA-5128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5128: Priority: Blocker (was: Major) > TransactionCoordinator - Check inter broker protocol and message f

[jira] [Assigned] (KAFKA-5128) TransactionCoordinator - Check inter broker protocol and message format and raise errors if incompatible

[ https://issues.apache.org/jira/browse/KAFKA-5128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta reassigned KAFKA-5128: --- Assignee: Damian Guy > TransactionCoordinator - Check inter broker protocol and message forma

[jira] [Created] (KAFKA-5279) TransactionCoordinator must expire transactionalIds

Apurva Mehta created KAFKA-5279: --- Summary: TransactionCoordinator must expire transactionalIds Key: KAFKA-5279 URL: https://issues.apache.org/jira/browse/KAFKA-5279 Project: Kafka Issue Type: B

[jira] [Updated] (KAFKA-5279) TransactionCoordinator must expire transactionalIds

[ https://issues.apache.org/jira/browse/KAFKA-5279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5279: Labels: exactly-once (was: ) > TransactionCoordinator must expire transactionalIds > --

[jira] [Updated] (KAFKA-5279) TransactionCoordinator must expire transactionalIds

[ https://issues.apache.org/jira/browse/KAFKA-5279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5279: Issue Type: Sub-task (was: Bug) Parent: KAFKA-4815 > TransactionCoordinator must expire tra

[jira] [Created] (KAFKA-5280) Protect concurrent access to the cached transaction status

Apurva Mehta created KAFKA-5280: --- Summary: Protect concurrent access to the cached transaction status Key: KAFKA-5280 URL: https://issues.apache.org/jira/browse/KAFKA-5280 Project: Kafka Issue

[jira] [Assigned] (KAFKA-4935) Consider disabling record level CRC checks for message format V2

[ https://issues.apache.org/jira/browse/KAFKA-4935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta reassigned KAFKA-4935: --- Assignee: Jason Gustafson > Consider disabling record level CRC checks for message format V2

[jira] [Commented] (KAFKA-4935) Consider disabling record level CRC checks for message format V2

[ https://issues.apache.org/jira/browse/KAFKA-4935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16016137#comment-16016137 ] Apurva Mehta commented on KAFKA-4935: - The current solution is to provide a light weig

[jira] [Updated] (KAFKA-4935) Consider disabling record level CRC checks for message format V2

[ https://issues.apache.org/jira/browse/KAFKA-4935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-4935: Labels: exactly-once (was: ) > Consider disabling record level CRC checks for message format V2 > -

[jira] [Updated] (KAFKA-4935) Consider disabling record level CRC checks for message format V2

[ https://issues.apache.org/jira/browse/KAFKA-4935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-4935: Priority: Blocker (was: Major) > Consider disabling record level CRC checks for message format V2 >

[jira] [Updated] (KAFKA-3487) KIP-146: Support per-connector/per-task classloaders in Connect

[ https://issues.apache.org/jira/browse/KAFKA-3487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-3487: - Resolution: Fixed Status: Resolved (was: Patch Available) Issue resolved

[GitHub] kafka pull request #3028: KAFKA-3487: Support classloading isolation in Conn...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3028 --- 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] [Updated] (KAFKA-5019) Exactly-once upgrade notes

[ https://issues.apache.org/jira/browse/KAFKA-5019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5019: Priority: Blocker (was: Critical) > Exactly-once upgrade notes > -- > >

[jira] [Commented] (KAFKA-3487) KIP-146: Support per-connector/per-task classloaders in Connect

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

[jira] [Updated] (KAFKA-5020) Update protocol documentation to mention message format v2

[ https://issues.apache.org/jira/browse/KAFKA-5020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5020: Priority: Blocker (was: Major) > Update protocol documentation to mention message format v2 > -

[GitHub] kafka pull request #3090: KAFKA-5150 reduce lz4 decompression overhead - Bac...

GitHub user xvrl opened a pull request: https://github.com/apache/kafka/pull/3090 KAFKA-5150 reduce lz4 decompression overhead - Backport to 0.10.2.x You can merge this pull request into a Git repository by running: $ git pull https://github.com/xvrl/kafka kafka-5150-0.10 Alt

[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&focusedCommentId=16016146#comment-16016146 ] ASF GitHub Bot commented on KAFKA-5150: --- GitHub user xvrl opened a pull request:

[jira] [Updated] (KAFKA-5021) Update Message Delivery Semantics section to take into account KIP-98

[ https://issues.apache.org/jira/browse/KAFKA-5021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5021: Priority: Blocker (was: Major) > Update Message Delivery Semantics section to take into account KIP

[jira] [Assigned] (KAFKA-5024) Old clients don't support message format V2

[ https://issues.apache.org/jira/browse/KAFKA-5024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta reassigned KAFKA-5024: --- Assignee: Apurva Mehta > Old clients don't support message format V2 > --

[jira] [Updated] (KAFKA-5026) DebuggingConsumerId and DebuggingMessageFormatter and message format v2

[ https://issues.apache.org/jira/browse/KAFKA-5026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5026: Labels: exactly-once tooling (was: ) > DebuggingConsumerId and DebuggingMessageFormatter and messag

[jira] [Updated] (KAFKA-5031) Additional validation in validateMessagesAndAssignOffsets

[ https://issues.apache.org/jira/browse/KAFKA-5031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-5031: - Labels: exactly-once (was: ) > Additional validation in validateMessagesAndAssignOffsets > --

[jira] [Updated] (KAFKA-5030) Suggested clean-ups from message format V2 review

[ https://issues.apache.org/jira/browse/KAFKA-5030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5030: Labels: exactly-once (was: ) > Suggested clean-ups from message format V2 review >

[jira] [Updated] (KAFKA-5032) Think through implications of max.message.size affecting record batches in message format V2

[ https://issues.apache.org/jira/browse/KAFKA-5032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5032: Labels: exactly-once (was: ) > Think through implications of max.message.size affecting record batc

[jira] [Commented] (KAFKA-5033) Reconsider default retries for idempotent producer

[ https://issues.apache.org/jira/browse/KAFKA-5033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16016152#comment-16016152 ] Apurva Mehta commented on KAFKA-5033: - A default of `MAX_INT` seems reasonable here.

[jira] [Updated] (KAFKA-5033) Reconsider default retries for idempotent producer

[ https://issues.apache.org/jira/browse/KAFKA-5033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5033: Priority: Blocker (was: Major) > Reconsider default retries for idempotent producer > -

[jira] [Updated] (KAFKA-5033) Reconsider default retries for idempotent producer

[ https://issues.apache.org/jira/browse/KAFKA-5033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-5033: - Labels: exactly-once (was: ) > Reconsider default retries for idempotent producer > -

[jira] [Updated] (KAFKA-5202) Handle topic deletion for ongoing transactions

[ https://issues.apache.org/jira/browse/KAFKA-5202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-5202: - Labels: exactly-once (was: ) > Handle topic deletion for ongoing transactions > -

[jira] [Updated] (KAFKA-5186) Avoid expensive initialization of producer state when upgrading

[ https://issues.apache.org/jira/browse/KAFKA-5186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5186: Labels: exactly-once (was: ) > Avoid expensive initialization of producer state when upgrading > --

[jira] [Updated] (KAFKA-5186) Avoid expensive initialization of producer state when upgrading

[ https://issues.apache.org/jira/browse/KAFKA-5186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5186: Priority: Blocker (was: Critical) > Avoid expensive initialization of producer state when upgrading

[jira] [Updated] (KAFKA-5202) Handle topic deletion for ongoing transactions

[ https://issues.apache.org/jira/browse/KAFKA-5202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5202: Priority: Blocker (was: Major) > Handle topic deletion for ongoing transactions > -

[jira] [Assigned] (KAFKA-5247) Consumer GroupCoordinator should continue to materialize committed offsets in offset order even for transactional offset commits

[ https://issues.apache.org/jira/browse/KAFKA-5247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta reassigned KAFKA-5247: --- Assignee: Apurva Mehta > Consumer GroupCoordinator should continue to materialize committed o

[jira] [Updated] (KAFKA-5247) Consumer GroupCoordinator should continue to materialize committed offsets in offset order even for transactional offset commits

[ https://issues.apache.org/jira/browse/KAFKA-5247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5247: Priority: Blocker (was: Major) > Consumer GroupCoordinator should continue to materialize committed

[jira] [Assigned] (KAFKA-5202) Handle topic deletion for ongoing transactions

[ https://issues.apache.org/jira/browse/KAFKA-5202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta reassigned KAFKA-5202: --- Assignee: Guozhang Wang > Handle topic deletion for ongoing transactions > --

[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 ] Apurva Mehta updated KAFKA-5093: Priority: Critical (was: Major) > Load only batch header when rebuilding producer ID map >

[jira] [Assigned] (KAFKA-5032) Think through implications of max.message.size affecting record batches in message format V2

[ https://issues.apache.org/jira/browse/KAFKA-5032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta reassigned KAFKA-5032: --- Assignee: Apurva Mehta > Think through implications of max.message.size affecting record batc

[jira] [Updated] (KAFKA-5259) TransactionalId authorization should imply ProducerId authorization

[ https://issues.apache.org/jira/browse/KAFKA-5259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5259: Priority: Blocker (was: Major) > TransactionalId authorization should imply ProducerId authorizatio

[jira] [Updated] (KAFKA-5260) Producer should not send AbortTxn unless transaction has actually begun

[ https://issues.apache.org/jira/browse/KAFKA-5260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-5260: - Labels: exactly-once (was: ) > Producer should not send AbortTxn unless transaction has actually

[jira] [Updated] (KAFKA-5259) TransactionalId authorization should imply ProducerId authorization

[ https://issues.apache.org/jira/browse/KAFKA-5259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5259: Labels: exactly-once (was: ) > TransactionalId authorization should imply ProducerId authorization

[jira] [Updated] (KAFKA-5260) Producer should not send AbortTxn unless transaction has actually begun

[ https://issues.apache.org/jira/browse/KAFKA-5260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5260: Priority: Critical (was: Major) > Producer should not send AbortTxn unless transaction has actually

[jira] [Updated] (KAFKA-5260) Producer should not send AbortTxn unless transaction has actually begun

[ https://issues.apache.org/jira/browse/KAFKA-5260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5260: Priority: Blocker (was: Critical) > Producer should not send AbortTxn unless transaction has actual

[jira] [Assigned] (KAFKA-5260) Producer should not send AbortTxn unless transaction has actually begun

[ https://issues.apache.org/jira/browse/KAFKA-5260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta reassigned KAFKA-5260: --- Assignee: Damian Guy > Producer should not send AbortTxn unless transaction has actually begu

[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 ] Apurva Mehta updated KAFKA-5270: Priority: Major (was: Blocker) > TransactionManager should send and `AddOffsetsToTxn` request only

[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 ] Apurva Mehta updated KAFKA-5270: Priority: Blocker (was: Major) > TransactionManager should send and `AddOffsetsToTxn` request only

[jira] [Updated] (KAFKA-5269) TransactionBounceTest occasionally fails due to partition errors

[ https://issues.apache.org/jira/browse/KAFKA-5269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5269: Labels: exactly-once (was: ) > TransactionBounceTest occasionally fails due to partition errors > -

[jira] [Updated] (KAFKA-5269) TransactionBounceTest occasionally fails due to partition errors

[ https://issues.apache.org/jira/browse/KAFKA-5269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5269: Priority: Blocker (was: Major) > TransactionBounceTest occasionally fails due to partition errors >

[jira] [Assigned] (KAFKA-5279) TransactionCoordinator must expire transactionalIds

[ https://issues.apache.org/jira/browse/KAFKA-5279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang reassigned KAFKA-5279: Assignee: Guozhang Wang > TransactionCoordinator must expire transactionalIds > ---

[jira] [Assigned] (KAFKA-5273) KafkaConsumer.committed() should get latest committed offsets from the server

[ https://issues.apache.org/jira/browse/KAFKA-5273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta reassigned KAFKA-5273: --- Assignee: Apurva Mehta > KafkaConsumer.committed() should get latest committed offsets from t

[jira] [Updated] (KAFKA-5273) KafkaConsumer.committed() should get latest committed offsets from the server

[ https://issues.apache.org/jira/browse/KAFKA-5273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5273: Priority: Blocker (was: Major) > KafkaConsumer.committed() should get latest committed offsets from

[jira] [Assigned] (KAFKA-5279) TransactionCoordinator must expire transactionalIds

[ https://issues.apache.org/jira/browse/KAFKA-5279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta reassigned KAFKA-5279: --- Assignee: Damian Guy (was: Guozhang Wang) > TransactionCoordinator must expire transactional

[jira] [Created] (KAFKA-5281) System tests for KIP-98 / transaction

Apurva Mehta created KAFKA-5281: --- Summary: System tests for KIP-98 / transaction Key: KAFKA-5281 URL: https://issues.apache.org/jira/browse/KAFKA-5281 Project: Kafka Issue Type: Bug

[jira] [Updated] (KAFKA-5281) System tests for KIP-98 / transactions

[ https://issues.apache.org/jira/browse/KAFKA-5281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5281: Priority: Blocker (was: Major) > System tests for KIP-98 / transactions > -

[jira] [Updated] (KAFKA-5281) System tests for KIP-98 / transactions

[ https://issues.apache.org/jira/browse/KAFKA-5281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5281: Summary: System tests for KIP-98 / transactions (was: System tests for KIP-98 / transaction) > Sys

[jira] [Updated] (KAFKA-5281) System tests for KIP-98 / transactions

[ https://issues.apache.org/jira/browse/KAFKA-5281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5281: Issue Type: Sub-task (was: Bug) Parent: KAFKA-4815 > System tests for KIP-98 / transactions

[jira] [Assigned] (KAFKA-4325) Improve processing of late records for window operations

[ https://issues.apache.org/jira/browse/KAFKA-4325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang reassigned KAFKA-4325: Assignee: (was: Guozhang Wang) > Improve processing of late records for window operatio

[jira] [Assigned] (KAFKA-3596) Kafka Streams: Window expiration needs to consider more than event time

[ https://issues.apache.org/jira/browse/KAFKA-3596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang reassigned KAFKA-3596: Assignee: (was: Guozhang Wang) > Kafka Streams: Window expiration needs to consider mor

[jira] [Commented] (KAFKA-4171) Kafka-connect prints outs keystone and truststore password in log2

[ https://issues.apache.org/jira/browse/KAFKA-4171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16016189#comment-16016189 ] Ewen Cheslack-Postava commented on KAFKA-4171: -- [~bharatviswa] I'm not aware

[jira] [Commented] (KAFKA-4278) Undocumented REST resources

[ https://issues.apache.org/jira/browse/KAFKA-4278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16016195#comment-16016195 ] Ewen Cheslack-Postava commented on KAFKA-4278: -- [~bharatviswa] Looks like you

[jira] [Resolved] (KAFKA-5268) TransactionsBounceTest occasionally sees INVALID_TXN_STATE errors

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

[GitHub] kafka pull request #3089: KAFKA-5268: Fix bounce test transient failure by c...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3089 --- 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-5268) TransactionsBounceTest occasionally sees INVALID_TXN_STATE errors

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

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

See Changes: [me] KAFKA-3487: Support classloading isolation in Connect (KIP-146) -- [...truncated 882.98 KB...] kafka.log.ProducerStateManagerTest > testNonTransactional

  1   2   >