[jira] [Created] (KAFKA-10585) Kafka Streams should clean up the state store directory from cleanup

Rohan Desai created KAFKA-10585: --- Summary: Kafka Streams should clean up the state store directory from cleanup Key: KAFKA-10585 URL: https://issues.apache.org/jira/browse/KAFKA-10585 Project: Kafka

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

See Changes: [github] MINOR: trivial cleanups, javadoc errors, omitted StateStore tests, etc. (#8130) [github] KAFKA-10562: Properly invoke new StateStoreContext init (#9388) -

Re: [VOTE] KIP-584: Versioning scheme for features

Hi Jun, This is a very good point. I have updated the feature version deprecation section mentioning the same: https://cwiki.apache.org/confluence/display/KAFKA/KIP-584%3A+Versioning+scheme+for+features#KIP584:Versioningschemeforfeatures-Featureversiondeprecation . Thank you for the suggestion.

New release branch 2.7

Hello Kafka developers and friends, As promised, we now have a release branch for the 2.7 release (with 2.7.0 as the version). Trunk has been bumped to 2.8.0-SNAPSHOT. I'll be going over the JIRAs to move every non-blocker from this release to the next release. >From this point, most changes sho

[jira] [Created] (KAFKA-10586) MirrorMaker 2.0 REST support

Daniel Urban created KAFKA-10586: Summary: MirrorMaker 2.0 REST support Key: KAFKA-10586 URL: https://issues.apache.org/jira/browse/KAFKA-10586 Project: Kafka Issue Type: Improvement

Re: [VOTE] KIP-635: GetOffsetShell: support for multiple topics and consumer configuration override

Thanks for the KIP, +1 (binding). On Mon, Jul 27, 2020 at 1:09 AM Dániel Urbán wrote: > Hello everyone, > > I'd like to start a vote on KIP-635. The KIP enhances the GetOffsetShell > tool by enabling querying multiple topic-partitions, adding new filtering > options, and adding a config override

Re: [VOTE] KIP-635: GetOffsetShell: support for multiple topics and consumer configuration override

Thank you for the votes! The KIP passes with 3 binding votes (Manikumar, Mickael, Ismael) and 3 non-binding votes (Viktor, Kamal, David). Daniel Ismael Juma ezt írta (időpont: 2020. okt. 8., Cs, 16:27): > Thanks for the KIP, +1 (binding). > > On Mon, Jul 27, 2020 at 1:09 AM Dániel Urbán > wro

Build failed in Jenkins: Kafka » kafka-2.7-jdk8 #1

See Changes: -- [...truncated 3.37 MB...] org.apache.kafka.streams.test.OutputVerifierTest > shouldFailIfValueIsDifferentWithNullReverseForCompareValue PASSED org.apache.kaf

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

Hi Tom, I also agree that the current behavior is clearly wrong and I think it was mistakenly omitted in the KIP-412 discussion process. The current implementation does not reflect log4j's logger hierarchy. Regards, Dongjin On Thu, Oct 8, 2020 at 1:27 AM John Roesler wrote: > Ah, thanks Tom, >

Jenkins build is back to normal : Kafka » kafka-trunk-jdk8 #122

See

[jira] [Created] (KAFKA-10587) Rename kafka-mirror-maker CLI command line arguments for KIP-629

Xavier Léauté created KAFKA-10587: - Summary: Rename kafka-mirror-maker CLI command line arguments for KIP-629 Key: KAFKA-10587 URL: https://issues.apache.org/jira/browse/KAFKA-10587 Project: Kafka

[jira] [Created] (KAFKA-10589) Rename kafka-replica-verification CLI command line arguments for KIP-629

Xavier Léauté created KAFKA-10589: - Summary: Rename kafka-replica-verification CLI command line arguments for KIP-629 Key: KAFKA-10589 URL: https://issues.apache.org/jira/browse/KAFKA-10589 Project: K

[jira] [Created] (KAFKA-10588) Rename kafka-console-consumer CLI command line arguments for KIP-629

Xavier Léauté created KAFKA-10588: - Summary: Rename kafka-console-consumer CLI command line arguments for KIP-629 Key: KAFKA-10588 URL: https://issues.apache.org/jira/browse/KAFKA-10588 Project: Kafka

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

See Changes: [Bill Bejeck] Updating trunk versions after cutting branch for 2.7 -- [...truncated 6.80 MB...] org.apache.kafka.streams.TopologyTestDriverTest

Re: Kafka Contributor List Addition

Hi Do I need special permission to be able to comment on KIP discussion on confluence wikis? I have some KIPs I am interested in discussing / commenting on. Many thanks in advance, Saher On Tue, May 12, 2020 at 9:54 AM Saher Ahwal wrote: > Thanks! > I look forward to contributing and being par

Re: [VOTE] KIP-673: Emit JSONs with new auto-generated schema

Thanks everyone for the votes. In summary, the vote passed and the KIP was accepted with 3 binding and 3 non-binding +1s. Best, Anastasia On Mon, Oct 5, 2020 at 2:50 PM Jason Gustafson wrote: > +1 Thanks for the KIP! > > On Fri, Oct 2, 2020 at 4:37 PM Colin McCabe wrote: > > > Thanks, Anastasi

[jira] [Resolved] (KAFKA-10271) Performance regression while fetching a key from a single partition

[ https://issues.apache.org/jira/browse/KAFKA-10271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-10271. --- Fix Version/s: (was: 2.5.2) 2.7.0 Resolution: Fixed > Performa

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

Thanks, Sophie, Guozhang, and Matthias for sharing your thoughts. I am glad that another meaningful KIP is coming out of this discussion. I am good towards parking this KIP, till we can make the changes towards the RESTORING state we have discussed above. I will update this KIP with the closure

Re: Kafka Contributor List Addition

KIP discussions happen on the mailing list. You should not leave comments on the wiki and thus you don't need any special wiki permissions to participate in the discussion. Each KIP contains a link to the mail archive of the DISCUSS thread, and you should reply to the corresponding thread with you

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

I guess I understand now. However, it seems to be an "issue" with record caching. Setting the commit interval to zero would flush the cache each time, but it is not the "right" config change. You should just disable the `KTable` cache instead. You can disable caching globally by setting `cache.ma

Re: Kafka Contributor List Addition

Great! - Thanks Matthias! On Thu, Oct 8, 2020 at 12:03 PM Matthias J. Sax wrote: > KIP discussions happen on the mailing list. You should not leave > comments on the wiki and thus you don't need any special wiki > permissions to participate in the discussion. > > Each KIP contains a link to the

Build failed in Jenkins: Kafka » kafka-2.7-jdk8 #2

See Changes: [John Roesler] KAFKA-9929: Support backward iterator on SessionStore (#9139) -- [...truncated 6.78 MB...] org.apache.kafka.streams.test.OutputVerifi

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

See Changes: [Guozhang Wang] KAFKA-10271: Performance regression while fetching a key from a single partition (#9020) -- [...truncated 3.16 MB...] org.apache.ka

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

You're right. The behavior is correct with the cache disabled. Anyway I think the operator I propose can be useful. The need to generate a value from the previous and current value of a record can be quite common. I think the only way to implement it is through an aggregate using a helper class. I

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

See Changes: [github] KAFKA-9929: Support backward iterator on SessionStore (#9139) [github] MINOR: remove unused scala files from core module (#9296) [github] MINOR: correct package of LinuxIoMetr

Build failed in Jenkins: Kafka » kafka-2.7-jdk8 #3

See Changes: [Jun Rao] KAFKA-10028: Minor fixes to describeFeatures and updateFeatures apis (#9393) [Matthias J. Sax] KAFKA-7334: Suggest changing config for state.dir in case of FileNotFoundException

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

See Changes: [github] KAFKA-10028: Minor fixes to describeFeatures and updateFeatures apis (#9393) [github] KAFKA-10271: Performance regression while fetching a key from a single partition (#9020)

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

See Changes: [github] KAFKA-10028: Minor fixes to describeFeatures and updateFeatures apis (#9393) [github] KAFKA-10271: Performance regression while fetching a key from a single partition (#9020)

Re: New release branch 2.7

Hey Bill! Thank you for driving this release! We are only now starting to work on KIP-629, so we missed feature freeze. However the KIP is a collection of small changes (either a single method or literally just renames). We are wondering how you feel about us cherry-picking the PRs into 2.7 branc

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

See

Re: [VOTE] KIP-665 Kafka Connect Hash SMT

Just wanted to give another bump on this and see if anyone had any comments. Thanks! Brandon Brown > On Oct 1, 2020, at 9:11 AM, "bran...@bbrownsound.com" > wrote: > > Hey Kafka Developers, > > I’ve created the following KIP and updated it based on feedback from Mickael. > I was wondering

Build failed in Jenkins: Kafka » kafka-2.7-jdk8 #4

See Changes: [Guozhang Wang] KAFKA-10271: Performance regression while fetching a key from a single partition (#9020) -- [...truncated 6.78 MB...] org.apache.kaf

[jira] [Resolved] (KAFKA-10571) Replace occurrences of blackout with backoff for KIP-629

[ https://issues.apache.org/jira/browse/KAFKA-10571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xavier Léauté resolved KAFKA-10571. --- Resolution: Fixed > Replace occurrences of blackout with backoff for KIP-629 > -

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

See

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

See Changes: [cshapi] KAFKA-10571; Replace blackout with backoff for KIP-629 -- [...truncated 6.78 MB...] org.apache.kafka.streams.TopologyTestDriverTest >

[jira] [Created] (KAFKA-10590) Whole kafka node hungs when one node goes down.

sandeep p created KAFKA-10590: - Summary: Whole kafka node hungs when one node goes down. Key: KAFKA-10590 URL: https://issues.apache.org/jira/browse/KAFKA-10590 Project: Kafka Issue Type: Bug

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

I agree that there are cases when it is useful to get the old and new value. In fact, the DSL internally often tracks old and new value via a `Change` value type. We did have some discussion that it might be useful to expose this currently internal `Change` type in the public API. But if we do thi