[jira] [Resolved] (KAFKA-8046) Shutdown broker because all log dirs in /tmp/kafka-logs have failed

[ https://issues.apache.org/jira/browse/KAFKA-8046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaren resolved KAFKA-8046. -- Resolution: Not A Bug > Shutdown broker because all log dirs in /tmp/kafka-logs have failed >

[DISCUSS] KIP-439: Deprecate Interface WindowStoreIterator

Hi, I would like to propose KIP-439 to deprecate interface `WindowStoreIterator`. https://cwiki.apache.org/confluence/display/KAFKA/KIP-439%3A+Deprecate+Interface+WindowStoreIterator Looking forward to your feedback. -Matthias signature.asc Description: OpenPGP digital signature

[jira] [Created] (KAFKA-8088) Deprecate `WindowStoreIterator` interface

Matthias J. Sax created KAFKA-8088: -- Summary: Deprecate `WindowStoreIterator` interface Key: KAFKA-8088 URL: https://issues.apache.org/jira/browse/KAFKA-8088 Project: Kafka Issue Type:

Re: Wiki permission to create KIPs

Done. On 3/10/19 4:39 PM, Yaroslav Tkachenko wrote: > Hello, > > I'd love to propose a new KIP, but I don't have permissions to create wiki > pages. My Wiki ID is "sap1ens". > > Thanks! > signature.asc Description: OpenPGP digital signature

Re: KIP-213 - Scalable/Usable Foreign-Key KTable joins - Rebooted.

I agree that the LHS side must encode this information and tell the RHS if a tombstone requires a reply or not. >> Would this pose some sort of verbosity problem in the internal topics, >> especially if we have to rebuild state off of them? I don't see an issue atm. Can you elaborate how this

bug KAFKA-3881

Hi, In chasing down a metric bug, came across an older issue that looks to me to have the fix at least as of that time. Since that PR, the bug has been copied to two other locations in Fetcher.java, so I suppose a new PR is needed. Is there anything else I can do to help get this bug fixed?

Wiki permission to create KIPs

Hello, I'd love to propose a new KIP, but I don't have permissions to create wiki pages. My Wiki ID is "sap1ens". Thanks! -- Yaroslav Tkachenko sap1ens.com

Re: KIP-213 - Scalable/Usable Foreign-Key KTable joins - Rebooted.

Hi Matthias I have been mulling over the unsubscribe / delete optimization, and I have one main concern. I believe that the RHS can only determine whether to propagate the tombstone or not based on the value passed over from the LHS. This value would need to be non-null, and so wouldn't the

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

See Changes: [manikumar] KAFKA-7922: Return authorized operations in Metadata request response -- [...truncated 4.69 MB...]

[jira] [Resolved] (KAFKA-7922) Returned authorized operations in describe responses (KIP-430)

[ https://issues.apache.org/jira/browse/KAFKA-7922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-7922. -- Resolution: Fixed Fix Version/s: 2.3.0 > Returned authorized operations in describe responses

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

See