Build failed in Jenkins: Kafka » kafka-trunk-jdk11 #427

See Changes: [github] MINOR: Upgrade ducktape to version 0.8.1 (#9933) -- [...truncated 3.57 MB...] OutputVerifierTest >

Build failed in Jenkins: Kafka » kafka-trunk-jdk8 #397

See Changes: [github] MINOR: Upgrade ducktape to version 0.8.1 (#9933) -- [...truncated 3.46 MB...] MockProcessorContextStateStoreTest > builder =

Jenkins build is back to normal : Kafka » kafka-trunk-jdk15 #445

See

Build failed in Jenkins: Kafka » kafka-2.6-jdk8 #74

See Changes: [github] MINOR: Upgrade ducktape to version 0.7.11 (#9932) -- [...truncated 2.03 MB...] org.apache.kafka.streams.TestTopicsTest > testEmptyTopic

Build failed in Jenkins: Kafka » kafka-trunk-jdk8 #396

See Changes: [github] MINOR: fix record time in test shouldWipeOutStandbyStateDirectoryIfCheckpointIsMissing (#9948) -- [...truncated 3.55 MB...]

Build failed in Jenkins: Kafka » kafka-trunk-jdk8 #395

See Changes: [github] MINOR: Restore interrupt status when closing (#9863) -- [...truncated 2.12 MB...] TopologyTestDriverAtLeastOnceTest >

Build failed in Jenkins: Kafka » kafka-2.6-jdk8 #73

See Changes: [Matthias J. Sax] MINOR: fix record time in test shouldWipeOutStandbyStateDirectoryIfCheckpointIsMissing (#9948) -- Started by an SCM change

Build failed in Jenkins: Kafka » kafka-trunk-jdk15 #443

See Changes: [github] MINOR: Restore interrupt status when closing (#9863) -- [...truncated 3.01 MB...] TestTopicsTest >

Build failed in Jenkins: Kafka » kafka-trunk-jdk11 #424

See Changes: [github] MINOR: Restore interrupt status when closing (#9863) -- [...truncated 3.05 MB...] OutputVerifierTest >

Re: [DISCUSS] KIP-691: Transactional Producer Exception Handling

Thanks Boyang, yes I think I was confused about the different handling of two abortTxn calls, and now I get it was not intentional. I think I do not have more concerns. On Fri, Jan 22, 2021 at 1:12 PM Boyang Chen wrote: > Thanks for the clarification Guozhang, I got your point that we want to >

Build failed in Jenkins: Kafka » kafka-trunk-jdk8 #394

See Changes: [github] KAFKA-10357: Extract setup of repartition topics from Streams partition assignor (#9848) -- [...truncated 6.92 MB...]

Build failed in Jenkins: Kafka » kafka-trunk-jdk15 #442

See Changes: [github] KAFKA-10357: Extract setup of repartition topics from Streams partition assignor (#9848) -- [...truncated 3.52 MB...] TestTopicsTest

Re: [DISCUSS] KIP-691: Transactional Producer Exception Handling

Thanks for the clarification Guozhang, I got your point that we want to have a consistent handling of fatal exceptions being thrown from the abortTxn. I modified the current template to move the fatal exception try-catch outside of the processing loop to make sure we could get a chance to close

Build failed in Jenkins: Kafka » kafka-trunk-jdk11 #423

See Changes: [github] KAFKA-10357: Extract setup of repartition topics from Streams partition assignor (#9848) -- [...truncated 3.53 MB...]

Re: [DISCUSS] KIP-691: Transactional Producer Exception Handling

My understanding is that abortTransaction would only throw when the producer is in fatal state. For CommitFailed, the producer should still be in the abortable error state, so that abortTransaction call would not throw. On Fri, Jan 22, 2021 at 11:02 AM Guozhang Wang wrote: > Or are you going to

Re: [DISCUSS] KIP-691: Transactional Producer Exception Handling

Or are you going to maintain some internal state such that, the `abortTransaction` in the catch block would never throw again? On Fri, Jan 22, 2021 at 11:01 AM Guozhang Wang wrote: > Hi Boyang/Jason, > > I've also thought about this (i.e. using CommitFailed for all non-fatal), > but what I'm

Re: [DISCUSS] KIP-691: Transactional Producer Exception Handling

Hi Boyang/Jason, I've also thought about this (i.e. using CommitFailed for all non-fatal), but what I'm pondering is that, in the catch (CommitFailed) block, what would happen if the `producer.abortTransaction();` throws again? should that be captured as a fatal and cause the client to close

Re: [DISCUSS] Apache Kafka 2.8.0 release

Sure thing, Leah! -John On Thu, Jan 21, 2021, at 07:54, Leah Thomas wrote: > Hi John, > > KIP-659 was just accepted as well, can it be added to the release plan? >

Re: [DISCUSS] KIP-691: Transactional Producer Exception Handling

Hey Guozhang, Jason and I were discussing the new API offline and decided to take another approach. Firstly, the reason not to invent a new API with returned boolean flag is for compatibility consideration, since old EOS code would not know that a given transaction commit was failed internally as

Re: [DISCUSS] KIP-676: Respect the logging hierarchy

Thanks for updating the wording in KIP-676. I guess the best path forward depends on what we think needs to change. If we think KIP-676 and the changes already made in AK 2.8 are not quite right, then maybe we should address this either by fixing the changes (and maybe updating KIP-676 as needed)

relaxed naming policy for non-java clients and connectors

Hi, Everyone, To help build the eco-system for Apache Kafka, Apache Kafka PMC has passed a relaxed policy on naming non-java clients and connectors for Kafka. Details can be found at https://kafka.apache.org/trademark Thanks, Jun

[GitHub] [kafka-site] junrao merged pull request #323: adding trademark disclaimer page

junrao merged pull request #323: URL: https://github.com/apache/kafka-site/pull/323 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to

[GitHub] [kafka-site] scott-confluent commented on pull request #323: adding trademark disclaimer page

scott-confluent commented on pull request #323: URL: https://github.com/apache/kafka-site/pull/323#issuecomment-765540142 Without the menu open... ![Screen Shot 2021-01-22 at 11 22 08

How to build KAFKA 2.7 on z/OS platform

How can I build Kafka from ksource afka-2.7.0-src.tar) on z/OS v2.3 platform where gradle is NOT available? Can I use javac and compile the source code, and pack them with jar manually ? which sequence is recommended? Is a MAKE file available to rebuild the jar libs using make ? Thanks for any

[GitHub] [kafka-site] miguno opened a new pull request #324: KAFKA-8930: MirrorMaker v2 documentation

miguno opened a new pull request #324: URL: https://github.com/apache/kafka-site/pull/324 This adds a new user-facing documentation "Geo-replication (Cross-Cluster Data Mirroring)" section to the Kafka Operations documentation that covers MirrorMaker v2.

[GitHub] [kafka-site] scott-confluent commented on pull request #323: adding trademark disclaimer page

scott-confluent commented on pull request #323: URL: https://github.com/apache/kafka-site/pull/323#issuecomment-765489425 For now, here's a screenshot: ![Screen Shot 2021-01-22 at 10 34 27

[GitHub] [kafka-site] scott-confluent opened a new pull request #323: adding trademark disclaimer page

scott-confluent opened a new pull request #323: URL: https://github.com/apache/kafka-site/pull/323 Per requested. Will get a preview up shortly as soon as I can. This is an automated message from the Apache Git Service. To

[DISCUSS] KIP-707: The future of KafkaFuture

Hi, Following a recent discussion on a PR[1], I've written KIP-707 to establish what should be done to improve the API of KafkaFuture. If you have the time, your comments would be most welcome, as some of the rejected alternatives are not unreasonable.

Re: [DISCUSS] KIP-676: Respect the logging hierarchy

Hi Randall, Thanks for pointing this out. You're quite right about the behaviour of the LoggingResource, and I've updated the KIP with your suggested wording. However, looking at it has made me realise that while KIP-676 means the logger levels are now hierarchical there's still an inconsistency

Build failed in Jenkins: Kafka » kafka-trunk-jdk15 #441

See Changes: [github] KAFKA-12212; Bump Metadata API version to remove `ClusterAuthorizedOperations` fields (KIP-700) (#9945) -- [...truncated 3.58 MB...]

Build failed in Jenkins: Kafka » kafka-trunk-jdk8 #393

See Changes: [github] KAFKA-12212; Bump Metadata API version to remove `ClusterAuthorizedOperations` fields (KIP-700) (#9945) -- [...truncated 3.55 MB...]

Build failed in Jenkins: Kafka » kafka-trunk-jdk11 #422

See Changes: [github] KAFKA-12212; Bump Metadata API version to remove `ClusterAuthorizedOperations` fields (KIP-700) (#9945) -- [...truncated 3.58 MB...]

[jira] [Resolved] (KAFKA-10740) Replace OffsetsForLeaderEpochRequest.PartitionData with automated protocol

[ https://issues.apache.org/jira/browse/KAFKA-10740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot resolved KAFKA-10740. - Fix Version/s: 2.8.0 Resolution: Fixed > Replace

[jira] [Resolved] (KAFKA-10851) Add Cluster Describe API

[ https://issues.apache.org/jira/browse/KAFKA-10851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot resolved KAFKA-10851. - Fix Version/s: 2.8.0 Resolution: Fixed > Add Cluster Describe API >

[jira] [Resolved] (KAFKA-12212) Bump Metadata API version to remove `ClusterAuthorizedOperations` fields

[ https://issues.apache.org/jira/browse/KAFKA-12212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot resolved KAFKA-12212. - Fix Version/s: 2.8.0 Resolution: Fixed > Bump Metadata API version to remove