[jira] [Created] (KAFKA-9316) ConsoleProducer help info not expose default properties

huxihx created KAFKA-9316: - Summary: ConsoleProducer help info not expose default properties Key: KAFKA-9316 URL: https://issues.apache.org/jira/browse/KAFKA-9316 Project: Kafka Issue Type: Improveme

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

See Changes: [vvcephei] MINOR: Refactor versions in `FutureSubscriptionInfo` (#7849) [vvcephei] MINOR: Fix static membership link in Streams upgrade notes (#7439) -- [..

Re: [DISCUSS] KIP-158 UPDATED: Enable source connectors to create new topics with specific configs in Kafka Connect during runtime

Hi Tom, thanks for your comments, they are good points and useful corrections. Here's how things look now, after I updated the KIP: 10) I assumed proper escaping, but indeed it's better to be precise that every pattern will be treated as a regex. I also added an example with a topic name that con

[jira] [Reopened] (KAFKA-5756) Synchronization issue on flush

[ https://issues.apache.org/jira/browse/KAFKA-5756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton reopened KAFKA-5756: -- > Synchronization issue on flush > -- > > Key: KAFKA-57

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

See Changes: [manikumar.reddy] MINOR: Fix small typo in main README (#7779) [manikumar] MINOR: trivial cleanups -- [...truncated 5.61 MB...] org.apache.kafka.streams.tes

[jira] [Created] (KAFKA-9315) The Kafka Metrics class should clear the mbeans map when closing

Colin McCabe created KAFKA-9315: --- Summary: The Kafka Metrics class should clear the mbeans map when closing Key: KAFKA-9315 URL: https://issues.apache.org/jira/browse/KAFKA-9315 Project: Kafka

Re: [DISCUSS] KIP-405: Kafka Tiered Storage

Hi, Satish and Ivan, There are different ways for doing push based metadata propagation. Some object stores may support that already. For example, S3 supports events notification ( https://docs.aws.amazon.com/AmazonS3/latest/dev/NotificationHowTo.html). Otherwise one could use a separate metadata

[jira] [Created] (KAFKA-9314) Connect put() and poll() retries not conforming to KIP-298

Nigel Liang created KAFKA-9314: -- Summary: Connect put() and poll() retries not conforming to KIP-298 Key: KAFKA-9314 URL: https://issues.apache.org/jira/browse/KAFKA-9314 Project: Kafka Issue Ty

Re: [EXTERNAL] Re: [DISCUSS] KIP-280: Enhanced log compaction

Hi Radai, This is an interesting idea indeed. However since this KIP is already voted I'd also suggest maybe we can discuss about it in a separate thread so that we do not drag too long on it (as you can tell from the KIP number it has been proposed for quite some time and it would be great to hav

[jira] [Created] (KAFKA-9313) Set default for client.dns.lookup to use_all_dns_ips

Yeva Byzek created KAFKA-9313: - Summary: Set default for client.dns.lookup to use_all_dns_ips Key: KAFKA-9313 URL: https://issues.apache.org/jira/browse/KAFKA-9313 Project: Kafka Issue Type: Impr

Fwd: KIP-392 Allow consumers to fetch from closest replica

I was checking the release notes for 2.4.0 and noticed this KIP. Looks pretty awesome, but I didn't see anything about streams in the KIP. I did a quick glance at the code and also didn't see anywhere where the client.rack for the consumer was exposed out to where it could be set from the streams.

Re: [DISCUSS] KIP-489 Kafka Consumer Record Latency Metric

Thanks Sean. Look forward to the updated KIP. Regards, Habib On Fri, Dec 13, 2019, at 6:22 AM, Sean Glover wrote: > Hi, > > After my last reply I had a nagging feeling something wasn't right, and I > remembered that epoch time is UTC. This makes the discussion about > timezone irrelevant, since

Re: [DISCUSS] KIP-158 UPDATED: Enable source connectors to create new topics with specific configs in Kafka Connect during runtime

Hi Konstantine, Thanks for the KIP. I can see this would be a useful addition to Kafka Connect. 10. The documentation of topic.creation.$alias.include says "A list of strings that represent either exact topic names or regular expressions that may match topic names." How do you know whether the st

Re: [DISCUSS] KIP-405: Kafka Tiered Storage

Hi all, A.1 As commented on PR 7561, S3 consistency model [1][2] implies RSM cannot relies solely on S3 APIs to guarantee the expected strong consistency. The proposed implementation [3] would need to be updated to take this into account. Let’s talk more about this. A.2 Contract for the RSM API (

Re: [VOTE] KIP-409: Allow creating under-replicated topics and partitions

+1 non-binding. Thanks! On Wed, Dec 18, 2019 at 1:05 PM Sönke Liebau wrote: > Hi Mickael, > > thanks for your response! That all makes perfect sense and I cannot > give any actual use cases for where what I asked about would be useful > :) > It was more the idle thought if this might be low hang

[jira] [Resolved] (KAFKA-9301) KafkaProducer#flush should block until all the sent records get completed

[ https://issues.apache.org/jira/browse/KAFKA-9301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomoyuki Saito resolved KAFKA-9301. --- Resolution: Duplicate > KafkaProducer#flush should block until all the sent records get compl

Re: [VOTE] KIP-409: Allow creating under-replicated topics and partitions

Hi Mickael, thanks for your response! That all makes perfect sense and I cannot give any actual use cases for where what I asked about would be useful :) It was more the idle thought if this might be low hanging fruit while changing this anyway to avoid having to circle back later on and wanted to

Re: [VOTE] KIP-531: Drop support for Scala 2.11 in Kafka 2.5

+1 (non-binding). Thanks, On Tue, 17 Dec 2019 at 22:14, Ewen Cheslack-Postava wrote: > +1 (binding), though there is definitely still some compatibility risk -- > regardless of updates, people are going to have apps that may need other > updates but upgrading between scala versions is still too

Re: [VOTE] KIP-409: Allow creating under-replicated topics and partitions

Thanks Sönke for the feedback. I debated this point quite a bit before deciding to base creation around "min.insync.replicas". For me, the goal of this KIP is to enable administrators to provide higher availability. In a 3 node cluster configured for high availability (3 replicas, 2 min ISR), by