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

See Changes: [github] KAFKA-3522: Add internal RecordConverter interface (#6150) -- [...truncated 2.27 MB...] org.apache.kafka.streams.test.OutputVerifierTest >

[jira] [Resolved] (KAFKA-6964) Add ability to print all internal topic names

[ https://issues.apache.org/jira/browse/KAFKA-6964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-6964. -- Resolution: Won't Fix > Add ability to print all internal topic names >

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

See Changes: [github] KAFKA-3522: Add internal RecordConverter interface (#6150) -- [...truncated 2.47 MB...] kafka.utils.json.JsonValueTest > testDecodeLong PASSED

Re: [DISCUSS] KIP-390: Add producer option to adjust compression level

Hi Ismael, It seems like it needs more explanation. Here is the detailed reasoning. You know, topic and broker's 'compression.type' allows 'uncompressed', 'producer' with standard codecs (i.e., gzip, snappy, lz4, zstd.) And this configuration is used by the broker in the re-compressing process

Re: [DISCUSS] KIP-400 - Improve exit status in case of errors in ConsoleProducer

Thank you for the KIP. In my opinion, this feature must work well with shell scripts, by improving interoperability. Isn't it? Thanks, Dongjin On Fri, Jan 18, 2019, 6:30 AM kamal kaur Hi everyone, > > This is ready for discussion. > > *Jira* - https://issues.apache.org/jira/browse/KAFKA-6812 >

Re: [DISCUSS] KIP-390: Add producer option to adjust compression level

Hi Dongjin, When the compression type is "producer", then the broker doesn't recompress though. Thinking about it some more, there are some uncommon cases where recompression does happen (the old (and hopefully hardly used by now) message format == 0 and some edge cases), so it is a good point

Re: [DISCUSS] KIP-394: Require member.id for initial join group request

Hi, I'm late to the discussion, so apologies. One question, did we consider having the client generate a member id in the first join group? This could be random or known to be unique and would avoid a second join group request in the common case. If we considered and rejected this option, it

Re: [DISCUSS] KIP-419 Safely notify Kafka Connect SourceTask is stopped

On 2019/01/18 18:02:24, Andrew Schofield wrote: > Hi,> > > I’ve created a new KIP to enhance the SourceTask interface in Kafka Connect.> > > > > https://cwiki.apache.org/confluence/display/KAFKA/KIP-419:+Safely+notify+Kafka+Connect+SourceTask+is+stopped> > > > > Comments welcome.> > > > > Andrew

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

See Changes: [vahid.hashemian] MINOR: Remove unused imports, exceptions, and values (#6117) -- [...truncated 4.21 MB...] org.apache.kafka.streams.test.OutputVerifierTest

Re: Permissions to create KIP

Hi Tejal, Thanks for your interest. Access has been granted. Ismael On Sun, Jan 20, 2019 at 3:08 PM Tejal Adsul wrote: > Hi, > > I work at Confluent. Please could you grant me permission to create a KIP > for apache kafka, I wanted to propose a change to AbstractConfig in Kafka. > Following

Permissions to create KIP

Hi, I work at Confluent. Please could you grant me permission to create a KIP for apache kafka, I wanted to propose a change to AbstractConfig in Kafka. Following are my details Full NameTEJAL ADSUL emailte...@confluent.io ID: tejal Thanks, Tejal

Re: [DISCUSS] KIP-394: Require member.id for initial join group request

Hey Ismael, thanks for the suggestion here! I think the reason is because creating individual id on client is purely random (or at least I couldn't think of how to make sure it is "known to be unique"). Id collision will not be handled gracefully as we could perceive. However let client

[jira] [Created] (KAFKA-7847) KIP-421: Support resolving externalized secrets in AbstractConfig

TEJAL ADSUL created KAFKA-7847: -- Summary: KIP-421: Support resolving externalized secrets in AbstractConfig Key: KAFKA-7847 URL: https://issues.apache.org/jira/browse/KAFKA-7847 Project: Kafka

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

See Changes: [vahid.hashemian] MINOR: Remove unused imports, exceptions, and values (#6117) -- [...truncated 2.27 MB...]

[DISCUSS] KIP-421: Support resolving externalized secrets in AbstractConfig

Hi all, I have published KIP-421: Support resolving externalized secrets in AbstractConfig on the wiki here: https://cwiki.apache.org/confluence/display/KAFKA/KIP-421%3A+Support+resolving+externalized+secrets+in+AbstractConfig This KIP intends to enhance the AbstractConfig base class to support

[jira] [Created] (KAFKA-7846) KIP-421: Support resolving externalized secrets in AbstractConfig

TEJAL ADSUL created KAFKA-7846: -- Summary: KIP-421: Support resolving externalized secrets in AbstractConfig Key: KAFKA-7846 URL: https://issues.apache.org/jira/browse/KAFKA-7846 Project: Kafka

[VOTE] KIP-390: Allow fine-grained configuration for compression

Hi dev, I would like to open a vote for KIP-390: Allow fine-grained configuration for compression. Here is the KIP: https://cwiki.apache.org/confluence/display/KAFKA/KIP-390%3A+Allow+fine-grained+configuration+for+compression You can check the (on-going) discussion here:

Re: [DISCUSS] KIP-390: Add producer option to adjust compression level

I see. Let me have a check. If not needed, of course, we don't have to waste on configuration options. Since the KIP deadline is imminent, I just opened the voting thread. Let's continue the discussion here. Best, Dongjin On Mon, Jan 21, 2019 at 1:30 AM Ismael Juma wrote: > Hi Dongjin, > >

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

See Changes: [mjsax] MINOR: Handle case where connector status endpoints returns 404 (#6176) -- [...truncated 4.53 MB...] org.apache.kafka.streams.test.OutputVerifierTest

Re: [DISCUSS] KIP-300: Add Windowed KTable API in StreamsBuilder

Hey Mattihas, I have addressed the comments in KIP. Feel free to take another look. Also you are right, those are implementation details that we could discuss in diff  Boyang From: Matthias J. Sax Sent: Saturday, January 19, 2019 3:16 AM To:

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

See Changes: [mjsax] MINOR: Handle case where connector status endpoints returns 404 (#6176) -- [...truncated 2.27 MB...] kafka.utils.PasswordEncoderTest >

[DISCUSS] KIP-221: Enhance KStream with Connecting Topic Creation and Repartition Hint

Hey all, I would like to start a new discussion thread for refined KIP-221: https://cwiki.apache.org/confluence/display/KAFKA/KIP-221%3A+Enhance+KStream+with+Connecting+Topic+Creation+and+Repartition+Hint The major goal for this KIP is simplified to empower KStream #to and #groupBy APIs