Build failed in Jenkins: kafka-trunk-jdk11 #864

See Changes: [matthias] KAFKA-7245: Deprecate WindowStore#put(key, value) (#7105) -- [...truncated 5.42 MB...] org.apache.kafka.streams.MockProcessorContextTest > fullCo

Build failed in Jenkins: kafka-2.4-jdk8 #3

See Changes: [matthias] MINOR: Modified Exception handling for KIP-470 (#7461) -- [...truncated 2.91 MB...] org.apache.kafka.streams.TopologyTestDriverTest > shouldThrowPatte

RE: group.instance.id for StickyAssignors

Ah, thank you - so there is in fact a ticket. That's all I wanted to know. Thanks guys. See you over there... Kind regards Georg Friedrich -Original Message- From: Matthias J. Sax Sent: Monday, October 7, 2019 3:48 PM To: dev@kafka.apache.org Subject: Re: group.instance.id for StickyAssig

Build failed in Jenkins: kafka-2.3-jdk8 #123

See Changes: [wangguoz] KAFKA-8262, KAFKA-8263: Fix flaky test `MetricsIntegrationTest` (#6922) -- [...truncated 2.85 MB...] kafka.server.ReplicaManagerQuotasTest > testC

Build failed in Jenkins: kafka-2.4-jdk8 #2

See Changes: [wangguoz] KAFKA-8179: Part 7, cooperative rebalancing in Streams (#7386) [jason] KAFKA-8985; Add flexible version support to inter-broker APIs (#7453) [wangguoz] HOTFIX: Hide built-in metrics version (

[jira] [Created] (KAFKA-8995) Add new metric on broker to illustrate produce request compression percentage

Guozhang Wang created KAFKA-8995: Summary: Add new metric on broker to illustrate produce request compression percentage Key: KAFKA-8995 URL: https://issues.apache.org/jira/browse/KAFKA-8995 Project:

[jira] [Created] (KAFKA-8994) Streams should expose standby replication information & allow stale reads of state store

Vinoth Chandar created KAFKA-8994: - Summary: Streams should expose standby replication information & allow stale reads of state store Key: KAFKA-8994 URL: https://issues.apache.org/jira/browse/KAFKA-8994

Re: group.instance.id for StickyAssignors

As we have a ticket, I would recommend to move the discussion to the ticket. -Matthias On 10/7/19 3:40 PM, Boyang Chen wrote: > Hey Georg, > > thanks for your interest. We do have an open ticket for that task: > https://issues.apache.org/jira/browse/KAFKA-8432, and we believe it's > something

[jira] [Resolved] (KAFKA-8839) Improve logging in Kafka Streams around debugging task lifecycle

[ https://issues.apache.org/jira/browse/KAFKA-8839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinoth Chandar resolved KAFKA-8839. --- Resolution: Fixed Closing since the PR has been merged > Improve logging in Kafka Streams ar

Re: [DISCUSS]KIP-216: IQ should throw different exceptions for different errors

Sorry for the late reply. The 2.4 deadline kept us quite busy. About `StateStoreMigratedException`: Why is it only thrown if the state is REBALANCING? A store might be migrated during a rebalance, and Kafka Streams might resume back to RUNNING state and afterward somebody tries to use an old stor

Re: [VOTE] KIP-527: Add VoidSerde to Serdes

Hello Nikolay, Could you clarify in the wiki doc what would happen if the passed in `byte[] bytes` or `Void data` parameters are not null? From the example PR we would throw exception here. I think it worth documenting it as part of the contract in the wiki page. Otherwise, I'm +1. Guozhang On

Build failed in Jenkins: kafka-trunk-jdk11 #863

See Changes: [github] KAFKA-8985; Add flexible version support to inter-broker APIs (#7453) [wangguoz] KAFKA-8179: Part 7, cooperative rebalancing in Streams (#7386) --

Re: group.instance.id for StickyAssignors

Hey Georg, thanks for your interest. We do have an open ticket for that task: https://issues.apache.org/jira/browse/KAFKA-8432, and we believe it's something worth doing just didn't get chance to implement. Feel free to take it if you want. Guozhang and Matthias, could you share your opinion o

Re: [DISCUSSION] KIP-418: A method-chaining way to branch KStream

I am moving this KIP into "inactive status". Feel free to resume the KIP at any point. If anybody else is interested in picking up this KIP, feel free to do so. -Matthias On 7/11/19 4:00 PM, Matthias J. Sax wrote: > Ivan, > > did you see my last reply? What do you think about my proposal to m

RE: group.instance.id for StickyAssignors

Hi Matthias, Let's see if I can explain my idea in more detail: As far as I understood the group.instance.id is used to assign some ID to the consumer, so it keeps the same ID even if the consumer is restarted and by that allowing Kafka to keep the old assignment order. This is why it got part e

Re: [VOTE] KIP-527: Add VoidSerde to Serdes

Thanks for the KIP. +1(binding) -Bill On Mon, Oct 7, 2019 at 5:57 PM Matthias J. Sax wrote: > +1 (binding) > > > -Matthias > > On 10/6/19 8:02 PM, Nikolay Izhikov wrote: > > Hello, > > > > Any additional feedback on this? > > Do we need this in Kafka? > > > > В Ср, 02/10/2019 в 08:30 +0200, Br

Re: [DISCUSS] KIP-448: Add State Stores Unit Test Support to Kafka Streams Test Utils

What is the status of this KIP? Any updates? -Matthias On 9/10/19 8:08 PM, Sophie Blee-Goldman wrote: > Just took a look at the current KIP, and I think you should actually be > fine if you're just mocking the stores. > The issue I brought up isn't necessarily blocking this KIP, but it is > rel

Re: [DISCUSS] KIP-399: Extend ProductionExceptionHandler to cover serialization exceptions

Alaa, what is the status of this KIP? Are you still working on it? It would also be good to get feedback from other about the open questions. -Matthias On 9/17/19 5:33 PM, Matthias J. Sax wrote: > Thanks for picking up this KIP. > > My personal take about repartition topics is, that it seems

Re: kafka streams application design on state stores

I am not sure if I understand your scenario. What do you exactly mean by "back ground job" and by "sweeps the records in the store using range calls" ? As you noted, only the `Processor` that have access to the store should write/delete anything from it. You should not try to modify the store from

Re: join kafka contribution

Xu, thanks for your interest in contributing to Kafka! Kafka is very busy project and sometimes it's hard get attention. Sorry for your bad experience. To get started, I would recommend to read https://kafka.apache.org/contributing and also check out the corresponding page on the wiki: https://cw

Re: [DISCUSS] KIP-527: Add NothingSerde to Serdes

Thanks, Overall LGTM. Can you maybe add the corresponding package name for the new classes? -Matthias On 9/30/19 9:26 AM, Nikolay Izhikov wrote: > Hello, Bruno. > > Thanks for feedback. > KIP [1] updated according to your comments. > > [1] > https://cwiki.apache.org/confluence/display/KAFKA

Re: [Discuss] - KIP-532 - Add KStream#toTable to the Streams DSL

Aishwarya, Why is bullet point (2) formatted as "strike through"? If you intend to replace it with bullet point (3), just remove it completely. The KIP should reflect the actual proposal. Maybe move it to "Rejected Alternative" section? For (3c), it should also say, if `Materialize` specifies a q

Build failed in Jenkins: kafka-2.4-jdk8 #1

See Changes: -- [...truncated 2.68 MB...] org.apache.kafka.streams.TopologyTestDriverTest > shouldThrowForUnknownTopic[Eos enabled = false] PASSED org.apache.kafka.streams.TopologyTestDriv

Re: [VOTE] KIP-527: Add VoidSerde to Serdes

+1 (binding) -Matthias On 10/6/19 8:02 PM, Nikolay Izhikov wrote: > Hello, > > Any additional feedback on this? > Do we need this in Kafka? > > В Ср, 02/10/2019 в 08:30 +0200, Bruno Cadonna пишет: >> Hi Nikolay, >> >> Thank you for the KIP! >> >> +1 (non-binding) >> >> Best, >> Bruno >> >> On

Re: group.instance.id for StickyAssignors

`groud.instance.id` is for static group membership. What advantage to you imply by re-using it for (Cooperative)StickyAssignor? >> As far as I understand this would make the behavior of those assignors more >> predictable. Can you elaborate? I am not aware of any re-use, and I personally belie

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

See

[jira] [Created] (KAFKA-8993) Add an EOS performance test suite similar to ProducerPerformance

Boyang Chen created KAFKA-8993: -- Summary: Add an EOS performance test suite similar to ProducerPerformance Key: KAFKA-8993 URL: https://issues.apache.org/jira/browse/KAFKA-8993 Project: Kafka I

Build failed in Jenkins: kafka-trunk-jdk11 #862

See Changes: [github] MINOR: Bump version to 2.5.0-SNAPSHOT (#7455) -- [...truncated 2.67 MB...] org.apache.kafka.streams.TopologyTestDriverTest > shouldPunctuateOnStrea

Re: [DISCUSS] Apache Kafka 2.4.0 release

Thanks Manikumar. To be clear, we should be focusing on stabilization from now until the code freeze. It's OK to merge small PRs that complete KIPs that have been partially merged or that are effectively fixes, but features should generally target trunk and the next release. Ismael On Mon, Oct 7,

Re: [DISCUSS] Apache Kafka 2.4.0 release

Hi all, I have moved couple of accepted KIPs without a PR to the next release. We still have quite a few KIPs with PRs that are being reviewed, but haven't yet been merged. I have left all of these in assuming these PRs are ready and not risky to merge. Please update your assigned KIPs/JIRAs, if

KAFKA-8104: Help with the fair reproducer and review

Hello. We have KAFKA-8104 "Consumer cannot rejoin to the group after rebalancing" [1] issue. It reproduces on many production environments. I prepared reproducer and fix [2] for this issue. But, I need assistance with the "fair" reproducer. Please, help me with the review and "fair" reproducer:

[jira] [Created] (KAFKA-8992) Don't expose Errors in Admin result objects

Jason Gustafson created KAFKA-8992: -- Summary: Don't expose Errors in Admin result objects Key: KAFKA-8992 URL: https://issues.apache.org/jira/browse/KAFKA-8992 Project: Kafka Issue Type: Bug

[jira] [Resolved] (KAFKA-6263) Expose metric for group metadata loading duration

[ https://issues.apache.org/jira/browse/KAFKA-6263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-6263. -- Fix Version/s: 2.4.0 Resolution: Fixed > Expose metric for group metadata loading duration > ---

[jira] [Resolved] (KAFKA-8985) Use flexibleVersions with LeaderAndIsr, UMR, etc., and improve RequestResponseTest coverage

[ https://issues.apache.org/jira/browse/KAFKA-8985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-8985. Fix Version/s: 2.4.0 Assignee: Jason Gustafson (was: Colin McCabe) Resoluti

Re: [DISCUSS] KIP-530: Considerrenaming'UsePreviousTimeOnInvalidTimeStamp' classto'UsePartitionTimeOnInvalidTimeStamp'

Hi Rabi, no need to include images for the code. There is a code block feature in the wiki. I added one of those code blocks in your KIP as an example. Best, Bruno On Mon, Oct 7, 2019 at 4:55 PM Rabi Kumar K C wrote: > > Hi Bruno, > > Ha I see what you were talking about the extract method in

Build failed in Jenkins: kafka-trunk-jdk11 #861

See Changes: [manikumar] KAFKA-7500: MirrorMaker 2.0 (KIP-382) -- [...truncated 2.67 MB...] org.apache.kafka.streams.TopologyTestDriverTest > shouldThrowIfPersistentBuil

Re: A New Contributor

Hi Ersin, Thanks for your interest in Apache Kafka. You're all set now. -Bill On Mon, Oct 7, 2019 at 10:44 AM Ersin Bayraktar wrote: > Hello Kafka devs, > > I would like to contribute to Kafka Core, Kafka-Streams and documentation. > For this purpose, I would like to be added to the contributo

RE: [DISCUSS] KIP-530: Considerrenaming'UsePreviousTimeOnInvalidTimeStamp' classto'UsePartitionTimeOnInvalidTimeStamp'

Hi Bruno, Ha I see what you were talking about the extract method in UsePreviousTimeInvalidTimeStamp. Please ignore my last mail and I will update the KIP accordingly. With Best Regards, Rabi Kumar K C Sent from Mail for Windows 10 From: Rabi Kumar K C Sent: Monday, October 7, 2019 4:50 PM T

RE: [DISCUSS] KIP-530: Consider renaming'UsePreviousTimeOnInvalidTimeStamp' class to'UsePartitionTimeOnInvalidTimeStamp'

Hi Bruno, Thank You for your suggestions. I have made necessary changes in KIP and hopefully it’s fine now and if not then please do let me know. To answer your question 4) right now in trunk we can see that extract method is not present in UsePreviousTimeOnInvalidTimestamp instead it implemen

A New Contributor

Hello Kafka devs, I would like to contribute to Kafka Core, Kafka-Streams and documentation. For this purpose, I would like to be added to the contributor list. Please let me know if I need to provide any additional information. My Jira username : ersinbyrktr Thanks in advance, Cheers, -- Ers

Re: [VOTE] KIP-416: Notify SourceTask of ACK'd offsets, metadata

Thanks for the votes y'all! I'm closing this KIP, as equivalent functionality has now been merged as part of KIP-382. Ryanne On Sun, Oct 6, 2019, 7:55 AM Eno Thereska wrote: > +1 > > (Non binding) > > Thanks > Eno > > > On 4 Oct 2019, at 15:09, Harsha Chintalapani wrote: > > > > +1 (binding).

Re: [DISCUSS] KIP-530: Consider renaming 'UsePreviousTimeOnInvalidTimeStamp' class to 'UsePartitionTimeOnInvalidTimeStamp'

Hi Rabi, Thank you for the KIP! 1.) Could you please improve the formatting of the KIP? For instance, use appropriate formatting for code to differentiate it from the text. Also, we usually do not use italics to write KIPs. Look at other KIPs to get an idea of the formatting. 2.) "Public Interfa

New release branch 2.4

Hello Kafka developers and friends, As promised in the release plan, we now have a release branch for 2.4 release (with 2.4.0 target release version). Trunk will soon be bumped to 2.5.0-SNAPSHOT via https://github.com/apache/kafka/pull/7455. I'll be going over the JIRAs to move every non-blocker

RE: [DISCUSS] KIP-519: Make SSL context/engine configuration extensible

If I understand correctly, you are proposing to abandon the idea of a pluggable extension point for SSL in Kafka because we could rely on the JCE provider mechanism. I will reiterate that nobody does it that way. That in itself should be enough but let's discuss some of the reasons why. Changi

Build failed in Jenkins: kafka-trunk-jdk11 #860

See Changes: [matthias] KAFKA-8233: TopologyTestDriver test input and output usability [github] MINOR: Update documentation.html to refer to 2.4 (#7454) -- [...truncated

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

See Changes: [jason] KAFKA-8885; The Kafka Protocol should Support Optional Tagged Fields -- [...truncated 5.36 MB...] org.apache.kafka.streams.test.OutputVerifierTest >

group.instance.id for StickyAssignors

Hi, I'm wondering whether it is planned to make use of the group.instance.id also in the (Cooperative)StickyAssignor. As far as I understand this would make the behavior of those assignors more predictable. Maybe you have some information on this or whether I should open a Jira-Ticket for it. T

[jira] [Resolved] (KAFKA-8934) Introduce Instance-level Metrics

[ https://issues.apache.org/jira/browse/KAFKA-8934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Cadonna resolved KAFKA-8934. -- Fix Version/s: 2.4.0 Resolution: Fixed > Introduce Instance-level Metrics >

[jira] [Resolved] (KAFKA-7471) Multiple Consumer Group Management (Describe, Reset, Delete)

[ https://issues.apache.org/jira/browse/KAFKA-7471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-7471. -- Fix Version/s: 2.4.0 Resolution: Fixed > Multiple Consumer Group Management (Describe, Reset, De

[jira] [Resolved] (KAFKA-7800) Extend Admin API to support dynamic application log levels

[ https://issues.apache.org/jira/browse/KAFKA-7800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-7800. -- Fix Version/s: 2.4.0 Resolution: Fixed > Extend Admin API to support dynamic application log lev

[jira] [Resolved] (KAFKA-8696) Clean up Sum/Count/Total metrics

[ https://issues.apache.org/jira/browse/KAFKA-8696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-8696. -- Resolution: Fixed > Clean up Sum/Count/Total metrics > > >

[jira] [Resolved] (KAFKA-8669) Add java security providers in Kafka Security config

[ https://issues.apache.org/jira/browse/KAFKA-8669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-8669. -- Fix Version/s: 2.4.0 Assignee: Sai Sandeep Resolution: Fixed Fixed in https://github.co

[jira] [Resolved] (KAFKA-8907) Return topic configs in CreateTopics response

[ https://issues.apache.org/jira/browse/KAFKA-8907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-8907. -- Reviewer: Manikumar Reddy Resolution: Fixed > Return topic configs in CreateTopics response > --

Build failed in Jenkins: kafka-trunk-jdk11 #859

See Changes: [jason] KAFKA-8885; The Kafka Protocol should Support Optional Tagged Fields -- [...truncated 2.65 MB...] org.apache.kafka.streams.TopologyTestDriverTest >

Re: KAFKA-8584: Support of ByteBuffer for bytes field implemented[Convert Kafka RPCs to use automatically generated code]

Hello. Please, review my changes [1] I fixed all conflicts after KAFKA-8885 [2] merge [3]. [1] https://github.com/apache/kafka/pull/7342 [2] https://issues.apache.org/jira/browse/KAFKA-8885 [3] https://github.com/apache/kafka/commit/0de61a4683b92bdee803c51211c3277578ab3edf В Пт, 20/09/2019 в 09