Jenkins build is back to normal : Kafka » kafka-trunk-jdk11 #123

See

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

See

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

See Changes: [github] KAFKA-9274: fix incorrect default value for `task.timeout.ms` config (#9385) [github] KAFKA-10564: only process non-empty task directories when internally cleaning obsolete

Jenkins build is back to normal : Kafka » kafka-2.6-jdk8 #30

See

Re: KIP-675: Convert KTable to a KStream using the previous value

I have done a small demo example. I hope it serves as a clarification. https://github.com/javierfreire/KTableToKStreamTest Thank you very much El mié., 7 oct. 2020 a las 3:01, Matthias J. Sax () escribió: > Thanks for the KIP. > > I am not sure if I understand the motivation. In particular the

[jira] [Created] (KAFKA-10584) IndexSearchType should use sealed trait instead of Enumeration

Jun Rao created KAFKA-10584: --- Summary: IndexSearchType should use sealed trait instead of Enumeration Key: KAFKA-10584 URL: https://issues.apache.org/jira/browse/KAFKA-10584 Project: Kafka Issue

[jira] [Created] (KAFKA-10583) Thread-safety of AdminClient is not documented

Adem Efe Gencer created KAFKA-10583: --- Summary: Thread-safety of AdminClient is not documented Key: KAFKA-10583 URL: https://issues.apache.org/jira/browse/KAFKA-10583 Project: Kafka Issue

[jira] [Resolved] (KAFKA-9930) Prevent ReplicaFetcherThread from throwing UnknownTopicOrPartitionException upon topic creation and deletion.

[ https://issues.apache.org/jira/browse/KAFKA-9930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adem Efe Gencer resolved KAFKA-9930. Resolution: Fixed > Prevent ReplicaFetcherThread from throwing

Is AdminClient of Kafka thread-safe?

Hi All, Other than a Stack Overflow comment (see https://stackoverflow.com/a/61738065) by Colin Patrick McCabe (CC'd), there is no source that verifies the thread-safety of KafkaAdminClient. * In particular, JavaDocs of KafkaAdminClient class and Admin interface have no discussion on

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

See Changes: [github] MINOR: Remove `TargetVoters` from `DescribeQuorum` (#9376) [github] KAFKA-10186; Abort transaction with pending data with TransactionAbortedException (#9280) [github]

[jira] [Resolved] (KAFKA-10362) When resuming Streams active task with EOS, the checkpoint file should be deleted

[ https://issues.apache.org/jira/browse/KAFKA-10362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-10362. --- Fix Version/s: 2.7.0 Resolution: Fixed > When resuming Streams active task with EOS,

Re: [DISCUSS] KIP-406: GlobalStreamThread should honor custom reset policy

I synced with John in-person and he emphasized his concerns about breaking code if we change the state machine. From an impl point of view, I am concerned that maintaining two state machines at the same time, might be very complex. John had the idea though, that we could actually do an internal

[jira] [Resolved] (KAFKA-9497) Brokers start up even if SASL provider is not loaded and throw NPE when clients connect

[ https://issues.apache.org/jira/browse/KAFKA-9497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram resolved KAFKA-9497. --- Resolution: Duplicate > Brokers start up even if SASL provider is not loaded and throw NPE

[jira] [Created] (KAFKA-10582) Mirror Maker 2 not replicating new topics until restart

Robert Martin created KAFKA-10582: - Summary: Mirror Maker 2 not replicating new topics until restart Key: KAFKA-10582 URL: https://issues.apache.org/jira/browse/KAFKA-10582 Project: Kafka

[jira] [Resolved] (KAFKA-10028) Implement write path for feature versioning scheme

[ https://issues.apache.org/jira/browse/KAFKA-10028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-10028. - Fix Version/s: 2.7.0 Resolution: Fixed merged the PR to trunk > Implement write path for

[jira] [Resolved] (KAFKA-10122) Consumer should allow heartbeat during rebalance as well

[ https://issues.apache.org/jira/browse/KAFKA-10122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-10122. --- Fix Version/s: 2.6.1 2.7.0 Resolution: Fixed > Consumer should

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

See Changes: [Ismael Juma] Revert "KAFKA-10469: Resolve logger levels hierarchically (#9266)" -- [...truncated 3.41 MB...]

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

See Changes: [Ismael Juma] Revert "KAFKA-10469: Resolve logger levels hierarchically (#9266)" -- [...truncated 3.38 MB...]

Re: [DISCUSSION] Upgrade system tests to python 3

Hello Nikolay, I've merged the PR to trunk. Thanks for your huge effort and patience going through the review! Guozhang On Wed, Oct 7, 2020 at 6:52 AM Nikolay Izhikov wrote: > Great news! > Thanks Magnus! > > I’ve updated the PR. > > Looks like we ready to merge it. > > > 7 окт. 2020 г., в

[jira] [Resolved] (KAFKA-10186) Aborting transaction with pending data should throw non-fatal exception

[ https://issues.apache.org/jira/browse/KAFKA-10186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-10186. - Fix Version/s: 2.7.0 Resolution: Fixed > Aborting transaction with pending data

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

Ah, thanks Tom, My only concern was that we might silently start logging a lot more or less after the upgrade, but if the logging behavior won't change at all, then the concern is moot. Since the KIP is only to make the APIs return an accurrate representation of the actual log level, I have no

Re: [DISCUSS] Apache Kafka 2.7.0 release

Hi Anna, I've updated the table to only show KAFKA-10023 as going into 2.7 Thanks, Bill On Tue, Oct 6, 2020 at 6:51 PM Anna Povzner wrote: > Hi Bill, > > Regarding KIP-612, only the first half of the KIP will get into 2.7 > release: Broker-wide and per-listener connection rate limits,

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

Hi John, You're right, but note that this affects the level the broker/connect worker was _reporting_ for that logger, not the level at which the logger was actually logging, which would be TRACE both before and after upgrading. I've added more of an explanation to the KIP, since it wasn't very

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

Thanks for this KIP Tom, Just to clarify the impact: In your KIP you described a situation in which the root logger is configured at INFO, an "kafka.foo" is configured at TRACE, and then "kafka.foo.bar" is resolved to INFO. Assuming this goes into 3.0, would it be the case that if I had the

[DISCUSS] KIP-676: Respect the logging hierarchy

Hi all, I would like to start discussion on a small KIP which seeks to rectify an inconsistency between how Kafka reports logger levels and how logger configuration is inherited hierarchically in log4j. https://cwiki.apache.org/confluence/display/KAFKA/KIP-676%3A+Respect+logging+hierarchy

Re: [DISCUSSION] Upgrade system tests to python 3

Great news! Thanks Magnus! I’ve updated the PR. Looks like we ready to merge it. > 7 окт. 2020 г., в 15:29, Magnus Edenhill написал(а): > > Hi, > > ducktape v0.8.0 is now released. > > Regards, > Magnus > > > Den ons 7 okt. 2020 kl 10:50 skrev Nikolay Izhikov : > >> Hello. >> >> Got 4

[jira] [Created] (KAFKA-10581) Ability to filter events at Kafka broker based on Kafka header value

Bhukailas Reddy created KAFKA-10581: --- Summary: Ability to filter events at Kafka broker based on Kafka header value Key: KAFKA-10581 URL: https://issues.apache.org/jira/browse/KAFKA-10581 Project:

Re: [DISCUSSION] Upgrade system tests to python 3

Hi, ducktape v0.8.0 is now released. Regards, Magnus Den ons 7 okt. 2020 kl 10:50 skrev Nikolay Izhikov : > Hello. > > Got 4 approvals for PR [1] > The only thing we need to be able to merge it is a ducktape 0.8 release. > If ducktape team need any help with the release, please, let me know.

Re: [DISCUSSION] Upgrade system tests to python 3

Hello. Got 4 approvals for PR [1] The only thing we need to be able to merge it is a ducktape 0.8 release. If ducktape team need any help with the release, please, let me know. [1] https://github.com/apache/kafka/pull/9196 > 21 сент. 2020 г., в 12:58, Nikolay Izhikov > написал(а): > >