[jira] [Created] (KAFKA-13248) Class name mismatch for LoggerFactory.getLogger method in TimeOrderedWindowStoreBuilder.java

S. B. Hunter created KAFKA-13248: Summary: Class name mismatch for LoggerFactory.getLogger method in TimeOrderedWindowStoreBuilder.java Key: KAFKA-13248 URL: https://issues.apache.org/jira/browse/KAFKA-13248

[GitHub] [kafka-site] benbromhead commented on pull request #362: Add Instaclustr to the "Powered By" list

benbromhead commented on pull request #362: URL: https://github.com/apache/kafka-site/pull/362#issuecomment-907696024 See attached for a local rendering of the change  cc

Re: [DISCUSS] KIP-770: Replace "buffered.records.per.partition" with "input.buffer.max.bytes"

Thanks Guozhang and Sophie. Yeah a small default value would lower the throughput. I didn't quite realise it earlier. It's slightly hard to predict this value so I would guess around 1/2 GB to 1 GB? WDYT? Regarding the renaming of the config and the new metric, sure would include it in the KIP.

[jira] [Created] (KAFKA-13247) Adding functionality for loading private key entry by alias from the keystore

Tigran Margaryan created KAFKA-13247: Summary: Adding functionality for loading private key entry by alias from the keystore Key: KAFKA-13247 URL: https://issues.apache.org/jira/browse/KAFKA-13247

Jenkins build is unstable: Kafka » Kafka Branch Builder » trunk #438

See

[jira] [Resolved] (KAFKA-10774) Support Describe topic using topic IDs

[ https://issues.apache.org/jira/browse/KAFKA-10774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram resolved KAFKA-10774. Fix Version/s: 3.1.0 Reviewer: Rajini Sivaram Resolution: Fixed > Support

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

See

Build failed in Jenkins: Kafka » Kafka Branch Builder » trunk #437

See Changes: -- [...truncated 488502 lines...] [2021-08-28T07:10:57.430Z] [2021-08-28T07:10:57.430Z] ControllerIntegrationTest > testTopicIdsAreNotAdded() PASSED

Re: [DISCUSS] KIP-763: Range queries with open endpoints

Thanks Patrick for the KIP and sorry for being late to the party here. One thing I would like to understand is, what's the expected behavior when a user specifies a null key in previous versions? In the new version which uses null key for open-ended range queries, could it potentially hide bugs in