Jenkins build is back to normal : kafka-2.0-jdk8 #138

See

Build failed in Jenkins: kafka-trunk-jdk10 #459

See Changes: [jason] KAFKA-7385; Fix log cleaner behavior when only empty batches are -- [...truncated 2.25 MB...] org.apache.kafka.streams.test.OutputVerifierTest > shou

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

See Changes: [github] MINOR: Move common out of range handling into AbstractFetcherThread -- [...truncated 2.68 MB...] org.apache.kafka.streams.test.OutputVerifierTest >

Build failed in Jenkins: kafka-trunk-jdk10 #458

See Changes: [github] MINOR: Move common out of range handling into AbstractFetcherThread -- [...truncated 2.21 MB...] org.apache.kafka.streams.TopologyTestDriverTest > s

[jira] [Resolved] (KAFKA-7385) Log cleaner crashes when empty batches are retained with idempotent or transactional producers

[ https://issues.apache.org/jira/browse/KAFKA-7385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-7385. Resolution: Fixed Fix Version/s: 2.0.1 > Log cleaner crashes when empty batches are

Build failed in Jenkins: kafka-trunk-jdk10 #457

See -- [...truncated 2.31 MB...] org.apache.kafka.streams.test.OutputVerifierTest > shouldFailIfValueIsDifferentForCompareValueTimestamp STARTED org.apache.kafka.streams.test.OutputVer

Re: [DISCUSS] KIP-367 Introduce close(Duration) to Producer instead of close(long, TimeUnit)

Thanks for updating the KIP! Some more nits: - showing the signatures of methods is sufficient (no need to have implementation details in the KIP). - `KafkaAdminClient#close(long duration, TimeUnit unit)` should be added as deprecated in the KIP, too - `AdminClient#close(long duration, TimeU

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

See Changes: [ismael] MINOR: Enable topic deletion in test configs (#5616) -- [...truncated 2.67 MB...] org.apache.kafka.streams.test.OutputVerifierTest > shouldFailIfVa

[VOTE] KIP-367 Introduce close(Duration) to Producer and AdminClient instead of close(long, TimeUnit)

Hi All, I'd like to put KIP-367 to the vote. https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=89070496 -- Chia-Ping

Re: [DISCUSS] KIP-367 Introduce close(Duration) to Producer instead of close(long, TimeUnit)

> It's a little hard to read -- it's easier if you just list the methods > (without JavaDocs) and indicate if the get deprecated or added. Please > don't show a diff as in a patch :) > > Is there already a JIRA for this? If not, please create on and link it > in the KIP. > > Besides this, I think

[jira] [Created] (KAFKA-7391) Introduce close(Duration) to Producer and AdminClient instead of close(long, TimeUnit)

Chia-Ping Tsai created KAFKA-7391: - Summary: Introduce close(Duration) to Producer and AdminClient instead of close(long, TimeUnit) Key: KAFKA-7391 URL: https://issues.apache.org/jira/browse/KAFKA-7391

Build failed in Jenkins: kafka-trunk-jdk10 #456

See Changes: [ismael] MINOR: Enable topic deletion in test configs (#5616) -- [...truncated 2.23 MB...] org.apache.kafka.streams.test.OutputVerifierTest > shouldPassIfVa

[jira] [Created] (KAFKA-7390) Enable the find-sec-bugs spotBugs plugin for Gradle

Ismael Juma created KAFKA-7390: -- Summary: Enable the find-sec-bugs spotBugs plugin for Gradle Key: KAFKA-7390 URL: https://issues.apache.org/jira/browse/KAFKA-7390 Project: Kafka Issue Type: Imp

[jira] [Created] (KAFKA-7389) Upgrade spotBugs for Java 11 support

Ismael Juma created KAFKA-7389: -- Summary: Upgrade spotBugs for Java 11 support Key: KAFKA-7389 URL: https://issues.apache.org/jira/browse/KAFKA-7389 Project: Kafka Issue Type: Sub-task

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

Hi Jan I have included a diagram of what I attempted on the KIP. https://cwiki.apache.org/confluence/display/KAFKA/KIP-213+Support+non-key+joining+in+KTable#KIP-213Supportnon-keyjoininginKTable-GroupBy+Reduce/Aggregate I attempted this back at the start of my own implementation of this solution,

Re: [DISCUSS] KIP-349 Priorities for Source Topics

Hi All, Thanks for all the comments on KIP-349. I agree with Mathias’ comment that topic prioritization and Message chooser are complimentary. And since the two API’s are not strongly coupled my inclination is not to add MessageChooser to KIP-349. MessageChoose could be done in a separate f

Re: [DISCUSS] KIP 368: Allow SASL Connections to Periodically Re-Authenticate

Hi yet again, Rajini. If we decide that interleaving is impossible with the low-level approach but we still want to at least support the possibility given that it reduces the size of latency spikes, then I do have a suggestion. I documented in the KIP how I rejected a single, one-size-fits-all qu

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

Hi James, nice to see you beeing interested. kafka streams at this point supports all sorts of joins as long as both streams have the same key. Adam is currently implementing a join where a KTable and a KTable can have a one to many relation ship (1:n). We exploit that rocksdb is a datastore th

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

See Changes: [junrao] KAFKA-7117: Support AdminClient API in AclCommand (KIP-332) (#5463) -- [...truncated 538.00 KB...] kafka.KafkaTest > testGetKafkaConfigFromArgsNonArg