[jira] [Created] (KAFKA-10035) Improve the AbstractResetIntegrationTest

feyman created KAFKA-10035: -- Summary: Improve the AbstractResetIntegrationTest Key: KAFKA-10035 URL: https://issues.apache.org/jira/browse/KAFKA-10035 Project: Kafka Issue Type: Improvement

Re: [DISCUSSION] KIP-418: A method-chaining way to branch KStream

Hello John, 1. - > Perhaps it would be better to stick with "as" for now > and just file a Jira to switch them all at the same time [for compatibility with Kotlin] Fully agree! BTW it's really not a big problem: in Kotlin they have a standard work

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

See Changes: [github] KAFKA-6145: Add unit tests for assignments of only stateless tasks -- [...truncated 6.17 MB...] org.apache.kafka.streams.TopologyTestDriverTest >

Build failed in Jenkins: kafka-trunk-jdk14 #120

See Changes: [github] KAFKA-6145: Add unit tests for assignments of only stateless tasks -- [...truncated 6.20 MB...] org.apache.kafka.streams.test.OutputVerifierTest >

Build failed in Jenkins: kafka-trunk-jdk11 #1491

See Changes: [github] MINOR: Improve security documentation for Kafka Streams #8710 [github] MINOR: Fix join group request timeout lower bound (#8702) [github] KAFKA-6145: Add unit tests for assignments of onl

[jira] [Created] (KAFKA-10034) Clarify Usage of "batch.size" and "max.request.size" Producer Configs

Mark Cox created KAFKA-10034: Summary: Clarify Usage of "batch.size" and "max.request.size" Producer Configs Key: KAFKA-10034 URL: https://issues.apache.org/jira/browse/KAFKA-10034 Project: Kafka

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

See Changes: [github] KAFKA-6145: KIP-441: Enforce Standby Task Stickiness (#8696) [github] MINOR: Improve security documentation for Kafka Streams #8710 [github] MINOR: Fix join group request timeout lower bou

Build failed in Jenkins: kafka-trunk-jdk14 #119

See Changes: [github] MINOR: Improve security documentation for Kafka Streams #8710 [github] MINOR: Fix join group request timeout lower bound (#8702) -- [...truncated 3

Re: [VOTE] KIP-602: Change default value for client.dns.lookup

Thanks, Badai, I’m +1 (binding) as well. -John On Fri, May 22, 2020, at 13:30, Manikumar wrote: > +1 (binding) > > Thanks for the KIP. > > > On Fri, May 22, 2020 at 11:23 PM Harsha Chintalapani > wrote: > > > +1 (binding). > > -Harsha > > > > On Fri, May 22, 2020 at 10:04 AM Ismael Juma w

Build failed in Jenkins: kafka-trunk-jdk11 #1490

See Changes: [github] KAFKA-6145: KIP-441: Enforce Standby Task Stickiness (#8696) -- [...truncated 3.10 MB...] org.apache.kafka.streams.test.ConsumerRecordFactoryTest >

Build failed in Jenkins: kafka-trunk-jdk14 #118

See Changes: [github] KAFKA-6145: KIP-441: Enforce Standby Task Stickiness (#8696) -- [...truncated 3.10 MB...] org.apache.kafka.streams.TopologyTestDriverTest > shouldT

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

See Changes: [github] KAFKA-10003: Mark KStream.through() as deprecated and update Scala API -- [...truncated 6.16 MB...] org.apache.kafka.streams.TopologyTestDriverTest

Re: [VOTE] KIP-602: Change default value for client.dns.lookup

+1 (binding) Thanks for the KIP. On Fri, May 22, 2020 at 11:23 PM Harsha Chintalapani wrote: > +1 (binding). > -Harsha > > On Fri, May 22, 2020 at 10:04 AM Ismael Juma wrote: > > > Thanks for the KIP, +1 (binding). > > > > Ismael > > > > On Fri, May 22, 2020 at 1:40 AM Badai Aqrandista > > w

Build failed in Jenkins: kafka-trunk-jdk11 #1489

See Changes: [github] KAFKA-10003: Mark KStream.through() as deprecated and update Scala API -- [...truncated 3.10 MB...] org.apache.kafka.streams.TopologyTestDriverTest

Re: [VOTE] KIP-602: Change default value for client.dns.lookup

+1 (binding). -Harsha On Fri, May 22, 2020 at 10:04 AM Ismael Juma wrote: > Thanks for the KIP, +1 (binding). > > Ismael > > On Fri, May 22, 2020 at 1:40 AM Badai Aqrandista > wrote: > > > Hi All, > > > > I would like to start the vote on KIP-602: Change default value for > > client.dns.lookup

Re: [VOTE] KIP-602: Change default value for client.dns.lookup

+1 (non-binding) Thanks, Badai. On Fri, May 22, 2020 at 10:05 AM Ismael Juma wrote: > Thanks for the KIP, +1 (binding). > > Ismael > > On Fri, May 22, 2020 at 1:40 AM Badai Aqrandista > wrote: > > > Hi All, > > > > I would like to start the vote on KIP-602: Change default value for > > client.

Re: [DISCUSS] KIP-606: Add Metadata Context to MetricsReporter

This looks useful, I think the only nit I would pick would be to name the MetricsReporter method contextChanged (past tense), which seems more conventional for methods like this. On Tue, 2020-05-05 at 16:58 -0700, Xavier Léauté wrote: [EXTERNAL EMAIL] Attention: This email was sent from outsid

Build failed in Jenkins: kafka-trunk-jdk14 #117

See Changes: [github] KAFKA-10003: Mark KStream.through() as deprecated and update Scala API -- [...truncated 3.10 MB...] org.apache.kafka.streams.TopologyTestDriverTest

Re: [VOTE] KIP-602: Change default value for client.dns.lookup

Thanks for the KIP, +1 (binding). Ismael On Fri, May 22, 2020 at 1:40 AM Badai Aqrandista wrote: > Hi All, > > I would like to start the vote on KIP-602: Change default value for > client.dns.lookup > > For reference, here is the KIP wiki: > > > https://cwiki.apache.org/confluence/display/KAFKA

Re: [DISCUSS] KIP-613: Add end-to-end latency metrics to Streams

Hey all, I'd like to make one adjustment to the current proposal and go back to the earlier proposal to report the task-level e2e latency metric at the source as well as the sink. I feel this will give users a more complete picture of the e2e latency if they only turn on INFO level metrics. I als

[jira] [Resolved] (KAFKA-10003) Deprecate KStream#through in favor of KStream#repartition

[ https://issues.apache.org/jira/browse/KAFKA-10003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax resolved KAFKA-10003. - Fix Version/s: 2.6.0 Resolution: Fixed > Deprecate KStream#through in favor of KS

[jira] [Created] (KAFKA-10033) AdminClient should throw UnknownTopicOrPartitionException instead of UnknownServerException if altering configs of non-existing topic

Gregory Koshelev created KAFKA-10033: Summary: AdminClient should throw UnknownTopicOrPartitionException instead of UnknownServerException if altering configs of non-existing topic Key: KAFKA-10033 URL: https:

[jira] [Created] (KAFKA-10032) Response to ApiVersionRequest returns wrong Produce(0) version

Antonio Pires created KAFKA-10032: - Summary: Response to ApiVersionRequest returns wrong Produce(0) version Key: KAFKA-10032 URL: https://issues.apache.org/jira/browse/KAFKA-10032 Project: Kafka

[jira] [Resolved] (KAFKA-9173) StreamsPartitionAssignor assigns partitions to only one worker

[ https://issues.apache.org/jira/browse/KAFKA-9173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Cadonna resolved KAFKA-9173. -- Fix Version/s: 2.6.0 Resolution: Fixed > StreamsPartitionAssignor assigns partitions to

[jira] [Created] (KAFKA-10031) Exist client create wrong topic automatically for a total-fresh restarted Kafka cluster

jiamei xie created KAFKA-10031: -- Summary: Exist client create wrong topic automatically for a total-fresh restarted Kafka cluster Key: KAFKA-10031 URL: https://issues.apache.org/jira/browse/KAFKA-10031

Re: [DISCUSS] KIP-602 - Change default value for client.dns.lookup

Voting thread has been posted. KIP-602 page has been updated with suggestions from Rajini. Thanks Badai On Fri, May 22, 2020 at 6:00 AM Ismael Juma wrote: > Badai, would you like to start a vote on this KIP? > > Ismael > > On Wed, May 20, 2020 at 7:45 AM Rajini Sivaram > wrote: > > > Deprecat

[VOTE] KIP-602: Change default value for client.dns.lookup

Hi All, I would like to start the vote on KIP-602: Change default value for client.dns.lookup For reference, here is the KIP wiki: https://cwiki.apache.org/confluence/display/KAFKA/KIP-602%3A+Change+default+value+for+client.dns.lookup And discussion thread: https://lists.apache.org/thread.html

Jenkins build is back to normal : kafka-2.5-jdk8 #130

See

Re: [DISCUSS] KIP-617: Allow Kafka Streams State Stores to be iterated backwards

Thanks Sophie. I like the `reverseAll()` idea. I updated the KIP with your feedback. On Fri, May 22, 2020 at 4:22 AM Sophie Blee-Goldman wrote: > Hm, the case of `all()` does seem to present a dilemma in the case of > variable-length keys. > > In the case of fixed-length keys, you can just co