Jenkins build is still unstable: Kafka » Kafka Branch Builder » trunk #1363

See

Re: [DISCUSS] KIP-884: Add config to configure KafkaClientSupplier in Kafka Streams

SG. Can we clarify/document the behavior on the KIP? -Matthias On 11/15/22 4:19 PM, Hao Li wrote: Thanks for the questions Matthias! 1. I think we can check the config in the constructor which doesn't take the client supplier as a parameter. This one: public KafkaStreams(final

Jenkins build is still unstable: Kafka » Kafka Branch Builder » trunk #1362

See

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

See

Re: [DISCUSS] KIP-883: Add delete callback method to Connector API

Hi, I've updated the KIP with the new #stop(boolean isDeleted) overloaded method, and have also amended the PR and JIRA tickets. I also added a couple entries to the "Rejected alternatives" section with the reasons why I pivoted from introducing new callback methods to retrofit the existing

[VOTE] KIP-884: Add config to configure KafkaClientSupplier in Kafka Streams

Hi all, I would like start a vote on KIP-884: https://cwiki.apache.org/confluence/display/KAFKA/KIP-884%3A+Add+config+to+configure+KafkaClientSupplier+in+Kafka+Streams Thanks, Hao

Re: [DISCUSS] KIP-875: First-class offsets support in Kafka Connect

Hi Mickael, Thanks for your thoughts! IMO it's most intuitive to use a null value in the PATCH API to signify that an offset should be reset, since it aligns nicely with the API we provide to source connectors, where null offsets are translated under the hood to tombstone records in the internal

Re: [DISCUSS] KIP-875: First-class offsets support in Kafka Connect

Hi Yash, I've updated the KIP with the correct "kafka_topic", "kafka_partition", and "kafka_offset" keys in the JSON examples (settled on those instead of prefixing with "Kafka " for better interactions with tooling like JQ). I've also added a note about sink offset requests failing if there are

Re: [DISCUSS] KIP-852 Optimize calculation of size for log in remote tier

Hi, Divij, Thanks for the reply. Point #1. Is the average remote segment metadata really 1KB? What's listed in the public interface is probably well below 100 bytes. Point #2. I guess you are assuming that each broker only caches the remote segment metadata in memory. An alternative approach is

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

See Changes: -- [...truncated 428747 lines...] [2022-11-17T19:08:47.160Z] > Task :connect:json:generateMetadataFileForMavenJavaPublication [2022-11-17T19:08:47.160Z] >

[jira] [Resolved] (KAFKA-14375) Remove use of "authorizer-properties" in EndToEndAuthorizationTest.scala

[ https://issues.apache.org/jira/browse/KAFKA-14375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Proven Provenzano resolved KAFKA-14375. --- Resolution: Fixed > Remove use of "authorizer-properties" in

[jira] [Created] (KAFKA-14398) Update EndToEndAuthorizerTest.scala to test with ZK and KRAFT quorum servers

Proven Provenzano created KAFKA-14398: - Summary: Update EndToEndAuthorizerTest.scala to test with ZK and KRAFT quorum servers Key: KAFKA-14398 URL: https://issues.apache.org/jira/browse/KAFKA-14398

Re: [DISCUSS] KIP-852 Optimize calculation of size for log in remote tier

Hi Jun There are three points that I would like to present here: 1. We would require a large cache size to efficiently cache all segment metadata. 2. Linear scan of all metadata at broker startup to populate the cache will be slow and will impact the archival process. 3. There is no other use

Re: [DISCUSS] Apache Kafka 3.3.2

Thanks for volunteering! +1 Best, Bruno On 17.11.22 09:57, Luke Chen wrote: Thanks for volunteering! On Thu, Nov 17, 2022 at 1:07 AM José Armando García Sancio wrote: +1. Thanks for volunteering. -- -José

Jenkins build is still unstable: Kafka » Kafka Branch Builder » trunk #1359

See

Re: [DISCUSS] Apache Kafka 3.3.2

Thanks for volunteering! On Thu, Nov 17, 2022 at 1:07 AM José Armando García Sancio wrote: > +1. Thanks for volunteering. > > -- > -José >