[DISCUSS] Release Plan for 1.1.1

Hi all, I would like to start the process for doing a 1.1.1 bug fix release. 1.1.0 was released Mar 28, 2018, and about 2.5 months have passed and 25 bug fixes have accumulated so far. A few of the more important fixes that have been merged in 1.1 branch so far: KAFKA-6925

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

See -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on H34 (ubuntu xenial) in workspace

Re: [DISCUSS] KIP-297: Externalizing Secrets for Connect Configurations

Sounds great, happy to hear we all agree! Thanks everyone! - Konstantine On Mon, Jun 11, 2018 at 4:22 PM, Colin McCabe wrote: > Sounds good. Thanks, Konstantin. > > Colin > > > On Mon, Jun 11, 2018, at 13:41, Rajini Sivaram wrote: > > Hi Konstantine, > > > > Sounds reasonable to me too. > >

Build failed in Jenkins: kafka-0.11.0-jdk7 #372

See Changes: [github] MINOR: update jackson dependencies (#5180) -- [...truncated 761.55 KB...] at java.io.RandomAccessFile.write(RandomAccessFile.java:550)

[jira] [Created] (KAFKA-7045) Consumer may not be able to consume all messages when down-conversion is required

Dhruvil Shah created KAFKA-7045: --- Summary: Consumer may not be able to consume all messages when down-conversion is required Key: KAFKA-7045 URL: https://issues.apache.org/jira/browse/KAFKA-7045 Project

[jira] [Created] (KAFKA-7044) kafka-consumer-groups.sh NullPointerException describing round robin or sticky assignors

Jeff Field created KAFKA-7044: - Summary: kafka-consumer-groups.sh NullPointerException describing round robin or sticky assignors Key: KAFKA-7044 URL: https://issues.apache.org/jira/browse/KAFKA-7044 Proj

Re: [VOTE] KIP-266: Add TimeoutException for KafkaConsumer#position

+1 Original message From: Ismael Juma Date: 6/11/18 5:43 PM (GMT-08:00) To: dev Subject: Re: [VOTE] KIP-266: Add TimeoutException for KafkaConsumer#position Sounds good to me. Ismael On Mon, Jun 11, 2018 at 5:38 PM Jason Gustafson wrote: > Hey All, > > I wanted to get to

Jenkins build is back to normal : kafka-1.1-jdk7 #141

See

Re: [VOTE] KIP-266: Add TimeoutException for KafkaConsumer#position

Sounds good to me. Ismael On Mon, Jun 11, 2018 at 5:38 PM Jason Gustafson wrote: > Hey All, > > I wanted to get to some closure on this issue before the release. I think > the config `default.api.timeout.ms` sounds good to me. Guozhang and I had > actually discussed using this name before we sa

Re: [VOTE] KIP-266: Add TimeoutException for KafkaConsumer#position

Re: special handling JoinGroup request so that we can use reasonable request.timeout.ms, sounds great to me :) Guozhang On Mon, Jun 11, 2018 at 5:38 PM, Jason Gustafson wrote: > Hey All, > > I wanted to get to some closure on this issue before the release. I think > the config `default.api.tim

Re: [VOTE] KIP-266: Add TimeoutException for KafkaConsumer#position

Hey All, I wanted to get to some closure on this issue before the release. I think the config `default.api.timeout.ms` sounds good to me. Guozhang and I had actually discussed using this name before we saw Colin's comment. As for the default value, the main reason that the current ` request.timeo

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

See

[jira] [Resolved] (KAFKA-6906) Kafka Streams does not commit transactions if data is produced via wall-clock punctuation

[ https://issues.apache.org/jira/browse/KAFKA-6906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax resolved KAFKA-6906. Resolution: Fixed Fix Version/s: 1.1.1 2.0.0 > Kafka Streams does

Re: [DISCUSS] KIP-297: Externalizing Secrets for Connect Configurations

Sounds good. Thanks, Konstantin. Colin On Mon, Jun 11, 2018, at 13:41, Rajini Sivaram wrote: > Hi Konstantine, > > Sounds reasonable to me too. > > Regards, > > Rajini > > On Mon, Jun 11, 2018 at 7:55 PM, Robert Yokota wrote: > > > Hi Konstantine, > > > > Sounds reasonable! > > > > Thanks

Jenkins build is back to normal : kafka-trunk-jdk10 #191

See

[jira] [Resolved] (KAFKA-7003) Add headers with error context in messages written to the Connect DeadLetterQueue topic

[ https://issues.apache.org/jira/browse/KAFKA-7003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava resolved KAFKA-7003. -- Resolution: Fixed Fix Version/s: 2.1.0 2.0.0 Issue re

[jira] [Created] (KAFKA-7043) Connect isolation whitelist does not include new primitive converters (KIP-305)

Randall Hauch created KAFKA-7043: Summary: Connect isolation whitelist does not include new primitive converters (KIP-305) Key: KAFKA-7043 URL: https://issues.apache.org/jira/browse/KAFKA-7043 Project

[jira] [Created] (KAFKA-7042) Fall back to the old behavior when the broker is too old to recognize LIST_OFFSET versions

Guozhang Wang created KAFKA-7042: Summary: Fall back to the old behavior when the broker is too old to recognize LIST_OFFSET versions Key: KAFKA-7042 URL: https://issues.apache.org/jira/browse/KAFKA-7042

[jira] [Created] (KAFKA-7041) Using RocksDB bulk loading for StandbyTasks

Matthias J. Sax created KAFKA-7041: -- Summary: Using RocksDB bulk loading for StandbyTasks Key: KAFKA-7041 URL: https://issues.apache.org/jira/browse/KAFKA-7041 Project: Kafka Issue Type: Imp

Re: kafka ack=all and min-isr

Thanks Ismael - that explains it. Thanks for the link James - I will take a look. On Sat, Jun 9, 2018 at 6:13 AM, James Cheng wrote: > I wrote a blog post on min.isr that explains it in more detail: > https://logallthethings.com/2016/07/11/min-insync-replicas-what-does-it- > actually-do/ > > The

Re: [DISCUSS] KIP-297: Externalizing Secrets for Connect Configurations

Hi Konstantine, Sounds reasonable to me too. Regards, Rajini On Mon, Jun 11, 2018 at 7:55 PM, Robert Yokota wrote: > Hi Konstantine, > > Sounds reasonable! > > Thanks, > Robert > > On Mon, Jun 11, 2018 at 11:49 AM, Konstantine Karantasis < > konstant...@confluent.io> wrote: > > > Hi everyone,

[jira] [Resolved] (KAFKA-7005) Remove duplicate Java Resource class.

[ https://issues.apache.org/jira/browse/KAFKA-7005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-7005. Resolution: Fixed merged the PR to trunk and 2.0 branch. > Remove duplicate Java Resource class. > ---

[jira] [Created] (KAFKA-7040) The replica fetcher thread may truncate accepted messages during multiple fast leadership transitions

Lucas Wang created KAFKA-7040: - Summary: The replica fetcher thread may truncate accepted messages during multiple fast leadership transitions Key: KAFKA-7040 URL: https://issues.apache.org/jira/browse/KAFKA-7040

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

See Changes: [lindong28] KAFKA-6946; Keep the session id for incremental fetch when fetch -- [...truncated 2.01 MB...] org.apache.kafka.streams.integration.StreamTableJoi

Re: [DISCUSS] KIP-312: Add Overloaded StreamsBuilder Build Method to Accept java.util.Properties

Thanks Matthias, I buy this reasoning. -John On Mon, Jun 11, 2018 at 12:48 PM, Matthias J. Sax wrote: > @John: I don't think this is a good idea. `KafkaStreams` executes a > `Topology` and should be agnostic if the topology was build manually or > via `StreamsBuilder` (at least from my point o

Re: [DISCUSS] KIP-297: Externalizing Secrets for Connect Configurations

Hi Konstantine, Sounds reasonable! Thanks, Robert On Mon, Jun 11, 2018 at 11:49 AM, Konstantine Karantasis < konstant...@confluent.io> wrote: > Hi everyone, after fixing an issue with a regular expression in Connect's > class loading isolation of the new component type ConfigProvider here: > >

Build failed in Jenkins: kafka-2.0-jdk8 #10

See Changes: [lindong28] KAFKA-6946; Keep the session id for incremental fetch when fetch -- [...truncated 481.75 KB...] kafka.javaapi.message.ByteBufferMessageSetTest > test

[jira] [Created] (KAFKA-7039) DelegatingClassLoader creates plugin instance even if its not Versioned

Magesh kumar Nandakumar created KAFKA-7039: -- Summary: DelegatingClassLoader creates plugin instance even if its not Versioned Key: KAFKA-7039 URL: https://issues.apache.org/jira/browse/KAFKA-7039

Re: [DISCUSS] KIP-297: Externalizing Secrets for Connect Configurations

Hi everyone, after fixing an issue with a regular expression in Connect's class loading isolation of the new component type ConfigProvider here: https://github.com/apache/kafka/pull/5177 I noticed that the new interface ConfigProvider, along with its first implementation FileConfigProvider, have

[jira] [Resolved] (KAFKA-6946) Keep the session id for incremental fetch when fetch responses are throttled

[ https://issues.apache.org/jira/browse/KAFKA-6946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin resolved KAFKA-6946. - Resolution: Fixed > Keep the session id for incremental fetch when fetch responses are throttled > -

Re: [DISCUSS] KIP-312: Add Overloaded StreamsBuilder Build Method to Accept java.util.Properties

@John: I don't think this is a good idea. `KafkaStreams` executes a `Topology` and should be agnostic if the topology was build manually or via `StreamsBuilder` (at least from my point of view). -Matthias On 6/11/18 9:53 AM, Guozhang Wang wrote: > Another implementation detail that we can conside

Re: [DISCUSS] KIP-312: Add Overloaded StreamsBuilder Build Method to Accept java.util.Properties

Another implementation detail that we can consider: currently the InternalTopologyBuilder#setApplicationId() is used because we do not have such a mechanism to pass in configs to the topology building process. Once we add such mechanism we should consider removing this function as well. Guozhang

Re: [DISCUSS] KIP-312: Add Overloaded StreamsBuilder Build Method to Accept java.util.Properties

Hello Bill, While working on https://github.com/apache/kafka/pull/5163 I am wondering if we can hide this from the public API, to e.g. add an additional function in InternalTopologyBuilder of InternalStreamsBuilder (since in your current working PR we're reusing InternalStreamsBuilder for the logi

Re: [DISCUSS] KIP-312: Add Overloaded StreamsBuilder Build Method to Accept java.util.Properties

Hi Bill, Thanks for the KIP. Just a small thought. This new API will result in calls that look like this: new KafkaStreams(builder.build(props), props); Do you think that's a significant enough eyesore to warrant adding a new KafkaStreams constructor taking a KStreamsBuilder like this: new Kafka

Re: [DISCUSS] KIP-313: Add KStream.flatTransform and KStream.flatTransformValues

Thanks for the KIP, it's a +1 for me. Looking forward to having a look at the PR. On Mon, Jun 11, 2018 at 9:58 AM Damian Guy wrote: > Thanks for the KIP. LGTM > > On Mon, 11 Jun 2018 at 00:44 Matthias J. Sax > wrote: > > > Thanks for the KIP. > > > > I don't have any comments at this pint. O

[jira] [Created] (KAFKA-7038) Support AdminClient Example

darion yaphet created KAFKA-7038: Summary: Support AdminClient Example Key: KAFKA-7038 URL: https://issues.apache.org/jira/browse/KAFKA-7038 Project: Kafka Issue Type: New Feature C

Apache Kafka 2.0.0 Release Progress

Hi all, I have moved out most of the JIRAs that aren't currently being worked on. We still have 24 JIRAs with 2.0.0 as the fix version ( https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=80448820). Six of these are marked as blockers. Since KIP freeze was delayed by a day due to hol

Re: [DISCUSS] KIP-110: Add Codec for ZStandard Compression (Updated)

I greatly appreciate your comprehensive reasoning. so: +1 for b until now. For the license issues, I will have a check on how the over projects are doing and share the results. Best, Dongjin On Mon, Jun 11, 2018 at 10:08 PM Viktor Somogyi wrote: > Hi Dongjin, > > A couple of comments: > I woul

Re: [DISCUSS] KIP-313: Add KStream.flatTransform and KStream.flatTransformValues

Thanks for the KIP. LGTM On Mon, 11 Jun 2018 at 00:44 Matthias J. Sax wrote: > Thanks for the KIP. > > I don't have any comments at this pint. Overall I am +1 on the KIP. > > > -Matthias > > On 6/8/18 2:56 PM, Bruno Cadonna wrote: > > Hi list, > > > > I created KIP-313 [1] for JIRA issue KAFKA-4

Re: [DISCUSS] KIP-110: Add Codec for ZStandard Compression (Updated)

Hi Dongjin, A couple of comments: I would vote for option b. in the "backward compatibility" section. My reasoning for this is that users upgrading to a zstd compatible version won't start to use it automatically, so manual reconfiguration is required. Therefore an upgrade won't mess up the cluste

[jira] [Created] (KAFKA-7037) Kafka doesn't allow to delete topic with '+' in the name

Sandeep Nemuri created KAFKA-7037: - Summary: Kafka doesn't allow to delete topic with '+' in the name Key: KAFKA-7037 URL: https://issues.apache.org/jira/browse/KAFKA-7037 Project: Kafka Issu

[jira] [Created] (KAFKA-7036) Complete the docs of KafkaConsumer#poll

Chia-Ping Tsai created KAFKA-7036: - Summary: Complete the docs of KafkaConsumer#poll Key: KAFKA-7036 URL: https://issues.apache.org/jira/browse/KAFKA-7036 Project: Kafka Issue Type: Improveme

[jira] [Created] (KAFKA-7035) Kafka Processor's init() method sometimes is not called

Oleksandr Konopko created KAFKA-7035: Summary: Kafka Processor's init() method sometimes is not called Key: KAFKA-7035 URL: https://issues.apache.org/jira/browse/KAFKA-7035 Project: Kafka

[jira] [Created] (KAFKA-7034) Remove the duplicated listTopics from Consumer

darion yaphet created KAFKA-7034: Summary: Remove the duplicated listTopics from Consumer Key: KAFKA-7034 URL: https://issues.apache.org/jira/browse/KAFKA-7034 Project: Kafka Issue Type: Imp

[jira] [Created] (KAFKA-7033) Modify AbstractOptions's timeoutMs as Long type

darion yaphet created KAFKA-7033: Summary: Modify AbstractOptions's timeoutMs as Long type Key: KAFKA-7033 URL: https://issues.apache.org/jira/browse/KAFKA-7033 Project: Kafka Issue Type: Imp

Support Kafka Broker Status

Hi team: I think we should support a tool to display kafka cluster broker's status . Maybe I should create a KIP (Kafka Improvement Proposals) ? or create JIRA directly ?? thanks ~