[jira] [Created] (KAFKA-7062) Simplify MirrorMaker loop after removal of old consumer support

Ismael Juma created KAFKA-7062: -- Summary: Simplify MirrorMaker loop after removal of old consumer support Key: KAFKA-7062 URL: https://issues.apache.org/jira/browse/KAFKA-7062 Project: Kafka

[jira] [Resolved] (KAFKA-6445) Remove deprecated metrics in 2.0

[ https://issues.apache.org/jira/browse/KAFKA-6445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-6445. Resolution: Fixed Assignee: Dong Lin (was: Charly Molter) Fix Version/s

[jira] [Resolved] (KAFKA-2837) FAILING TEST: kafka.api.ProducerBounceTest > testBrokerFailure

[ https://issues.apache.org/jira/browse/KAFKA-2837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-2837. Resolution: Fixed Fix Version/s: (was: 0.10.0.0) 2.0.0 This test has

[jira] [Resolved] (KAFKA-4237) Avoid long request timeout for the consumer

[ https://issues.apache.org/jira/browse/KAFKA-4237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-4237. Resolution: Duplicate Duplicate of KAFKA-7050. > Avoid long request timeout for the consu

[jira] [Resolved] (KAFKA-3355) GetOffsetShell command doesn't work with SASL enabled Kafka

[ https://issues.apache.org/jira/browse/KAFKA-3355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-3355. Resolution: Duplicate Fix Version/s: (was: 2.1.0) This will be done as part of KAFKA

[jira] [Resolved] (KAFKA-5234) GetOffsetShell: retrieve offsets for multiple topics with single request

[ https://issues.apache.org/jira/browse/KAFKA-5234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-5234. Resolution: Duplicate Let's consolidate GetOffsetShell improvements under KAFKA-5235

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

Sorry for the delay Dongjin. Everyone is busy finalising 2.0.0. This KIP seems like a great candidate for 2.1.0 and hopefully there will be more of a discussion next week. :) Ismael On Wed, 13 Jun 2018, 05:17 Dongjin Lee, wrote: > Hello. I just updated my draft implementation: > > 1. Rebased

[jira] [Resolved] (KAFKA-7029) ReplicaVerificationTool should not use the deprecated SimpleConsumer

[ https://issues.apache.org/jira/browse/KAFKA-7029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-7029. Resolution: Fixed > ReplicaVerificationTool should not use the deprecated SimpleConsu

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

> > > > > > I'm +1 for not using `max.block.ms`. I like > > Guozhang's > > > > > > > > > suggestion of > > > > > > > > > > > ` > > > > > > > > > > > > > default.block.ms` for the

[jira] [Created] (KAFKA-7029) ReplicaVerificationTool should not use the deprecated SimpleConsumer

Ismael Juma created KAFKA-7029: -- Summary: ReplicaVerificationTool should not use the deprecated SimpleConsumer Key: KAFKA-7029 URL: https://issues.apache.org/jira/browse/KAFKA-7029 Project: Kafka

[jira] [Created] (KAFKA-7028) super.users doesn't work with custom principals

Ismael Juma created KAFKA-7028: -- Summary: super.users doesn't work with custom principals Key: KAFKA-7028 URL: https://issues.apache.org/jira/browse/KAFKA-7028 Project: Kafka Issue Type: Bug

Re: kafka ack=all and min-isr

The key point is: if (leaderReplica.highWatermark.messageOffset >= requiredOffset) { The high watermark only moves when all the replicas in ISR have that particular offset. Does that clarify it? Ismael On Thu, Jun 7, 2018 at 10:31 PM Carl Samuelson wrote: > Hi > > Hopefully this is the

Re: [DISCUSS] 0.10.2.2 bug fix release

. Ismael On 7 Jun 2018 4:34 pm, "Ismael Juma" wrote: Thanks for doing this Matthias, +1. Ismael On Thu, Jun 7, 2018 at 1:50 PM Matthias J. Sax wrote: > Dear all, > > I want to propose a 0.10.2.2 bug fix release. 0.10.2.1 is over a year > old and a couple of critic

Re: [DISCUSS] 0.11.0.3 bug fix release

+1, thanks! On Thu, 7 Jun 2018, 11:16 Matthias J. Sax, wrote: > Dear all, > > I want to propose a 0.11.0.3 bug fix release. 0.11.0.2 is 6 months old > and a couple of critical fixes are available for 0.11.0.3. > > Please find a list of all 16 resolved tickets here: > > >

Re: [DISCUSS] 1.0.2 bug fix release

+1, thanks! On Thu, 7 Jun 2018, 11:16 Matthias J. Sax, wrote: > Dear all, > > I want to propose a 1.0.2 bug fix release. 1.0.1 is 3 months old and a > couple of critical fixes are available for 1.0.2. > > Please find a list of all 14 resolved tickets here: > > >

Re: [DISCUSS] 0.10.2.2 bug fix release

Thanks for doing this Matthias, +1. Ismael On Thu, Jun 7, 2018 at 1:50 PM Matthias J. Sax wrote: > Dear all, > > I want to propose a 0.10.2.2 bug fix release. 0.10.2.1 is over a year > old and a couple of critical fixes are available for 0.10.2.2. > > Please find a list of all 24 resolved

[jira] [Resolved] (KAFKA-6919) Trogdor documentation points to wrong location for trogdor.sh

[ https://issues.apache.org/jira/browse/KAFKA-6919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-6919. Resolution: Fixed Fix Version/s: 2.0.0 > Trogdor documentation points to wrong locat

[jira] [Resolved] (KAFKA-6996) ConsumerGroupCommand.scala uses deprecated components

[ https://issues.apache.org/jira/browse/KAFKA-6996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-6996. Resolution: Duplicate Duplicate of KAFKA-6884, > ConsumerGroupCommand.scala uses depreca

[jira] [Resolved] (KAFKA-6762) log-cleaner thread terminates due to java.lang.IllegalStateException

[ https://issues.apache.org/jira/browse/KAFKA-6762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-6762. Resolution: Duplicate Duplicate of KAFKA-6854. > log-cleaner thread terminates

[jira] [Resolved] (KAFKA-6965) log4j:WARN log messages printed when running kafka-console-producer OOB

[ https://issues.apache.org/jira/browse/KAFKA-6965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-6965. Resolution: Not A Bug > log4j:WARN log messages printed when running kafka-console-producer

[jira] [Resolved] (KAFKA-6760) responses not logged properly in controller

[ https://issues.apache.org/jira/browse/KAFKA-6760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-6760. Resolution: Fixed Fix Version/s: 1.1.1 2.0.0 > responses not log

[jira] [Resolved] (KAFKA-6973) setting invalid timestamp causes Kafka broker restart to fail

[ https://issues.apache.org/jira/browse/KAFKA-6973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-6973. Resolution: Fixed Fix Version/s: 2.0.0 > setting invalid timestamp causes Kafka bro

Re: referencing OffsetCheckpoint in downstream project

Hi Ted, There are two such classes. The example you have is for the broker class, not the Streams one. Ismael On Thu, 31 May 2018, 09:03 Ted Yu, wrote: > Hi, > OffsetCheckpoint has been relocated > to org.apache.kafka.streams.state.internals package. > > Does this mean that downstream project

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

Sounds good to me, On Wed, May 30, 2018 at 12:40 PM Jason Gustafson wrote: > Perhaps one minute? That is the default used by the producer. > > -Jason > > On Wed, May 30, 2018 at 9:50 AM, Ismael Juma wrote: > > > Option 1 sounds good to me provided that we can come up

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

Option 1 sounds good to me provided that we can come up with a good default. What would you suggest? Ismael On Wed, May 30, 2018 at 9:41 AM Jason Gustafson wrote: > Hi Everyone, > > There remains some inconsistency in the timeout behavior of the consumer > APIs which do not accept a timeout.

[jira] [Created] (KAFKA-6956) Use Java AdminClient in BrokerApiVersionsCommand

Ismael Juma created KAFKA-6956: -- Summary: Use Java AdminClient in BrokerApiVersionsCommand Key: KAFKA-6956 URL: https://issues.apache.org/jira/browse/KAFKA-6956 Project: Kafka Issue Type

[jira] [Created] (KAFKA-6955) Use Java AdminClient in DeleteRecordsCommand

Ismael Juma created KAFKA-6955: -- Summary: Use Java AdminClient in DeleteRecordsCommand Key: KAFKA-6955 URL: https://issues.apache.org/jira/browse/KAFKA-6955 Project: Kafka Issue Type

[jira] [Resolved] (KAFKA-6930) Update KafkaZkClient debug log

[ https://issues.apache.org/jira/browse/KAFKA-6930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-6930. Resolution: Fixed > Update KafkaZkClient debug

Re: [VOTE] KIP-176: Remove deprecated new-consumer option for tools

+1 (binding). Ismael On Wed, 23 May 2018, 09:04 Paolo Patierno, wrote: > Sorry ... I hope it's not too late but I created the KIP-176 on September > > > https://cwiki.apache.org/confluence/display/KAFKA/KIP-176%3A+Remove+deprecated+new-consumer+option+for+tools > > but due

Re: [VOTE] KIP-235 Add DNS alias support for secured connection

Thanks for the KIP. I think this is a good and low risk change. It would be good to ensure that it works well with KIP-302 if we think that makes sense too. In any case, +1 (binding). Ismael On Fri, Mar 23, 2018 at 12:05 PM Skrzypek, Jonathan < jonathan.skrzy...@gs.com> wrote: > Hi, > > I would

Java 8 switch in trunk

Hi all, We have switched to Java 8 in trunk. We can now use Java 8 for new code, but I suggest we don't refactor existing code to use Java 8 features like lambdas just yet. Let's focus on getting the 2.0.0 release out and after the first bug fix, we can consider refactors that will make backports

Re: [VOTE] KIP-303: Add Dynamic Routing Support in Kafka Streams' Topology Sink

Breaking API without a deprecation cycle doesn't seem good. Are we sure about this? Ismael On Mon, 21 May 2018, 15:04 Guozhang Wang, wrote: > Hello Matthias, > > I've tried it out on the PR, the implementation should be fine but one > concern I had is that, as you may also

Re: [DISCUSS] KIP-290: Support for wildcard suffixed ACLs

It got 3 binding votes already and the deadline is only tomorrow. :) Ismael On Mon, 21 May 2018, 21:50 Colin McCabe, wrote: > On Mon, May 21, 2018, at 04:53, Andy Coates wrote: > > Hey Piyush, > > > > Thanks for the updated KIP! Couple of minor points from me: > > > > When

Re: KAFKA-6733 feedback

Hi Mateusz, This is a good change, but it requires a KIP as mentioned in the PR. You gave an example of a similar PR without a KIP, but there was a KIP for it: https://cwiki.apache.org/confluence/display/KAFKA/KIP-265%3A+Make+Windowed+Serde+to+public+APIs Ismael On Mon, May 21, 2018 at 4:00 PM

Re: [VOTE] KIP-306: Configuration for Delaying Response to Failed Client Authentication

Thanks for the KIP, +1 (binding). Ismael On Mon, May 21, 2018 at 7:52 AM Dhruvil Shah wrote: > Hi, > > I would like to start a vote on KIP-306 which proposes to add a > configuration to delay responses to failed authentication. > > Link to the KIP: > >

[jira] [Resolved] (KAFKA-3665) Default ssl.endpoint.identification.algorithm should be https

[ https://issues.apache.org/jira/browse/KAFKA-3665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-3665. Resolution: Fixed > Default ssl.endpoint.identification.algorithm should be ht

[jira] [Reopened] (KAFKA-3665) Default ssl.endpoint.identification.algorithm should be https

[ https://issues.apache.org/jira/browse/KAFKA-3665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reopened KAFKA-3665: > Default ssl.endpoint.identification.algorithm should be ht

Re: [VOTE] KIP-277 - Fine Grained ACL for CreateTopics API

Thanks for the KIP, +1 (binding). Can you also please describe the compatibility impact of changing the error code from CLUSTER_AUTHORIZATION_FAILED to TOPIC_AUTHORIZATION_FAILED? Ismael On Wed, Apr 25, 2018 at 2:45 AM Edoardo Comar wrote: > Hi, > > The discuss thread on

[jira] [Resolved] (KAFKA-6873) Broker is not returning data including requested offset

[ https://issues.apache.org/jira/browse/KAFKA-6873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-6873. Resolution: Not A Problem > Broker is not returning data including requested off

[jira] [Created] (KAFKA-6923) Deprecate ExtendedSerializer/Serializer and ExtendedDeserializer/Deserializer

Ismael Juma created KAFKA-6923: -- Summary: Deprecate ExtendedSerializer/Serializer and ExtendedDeserializer/Deserializer Key: KAFKA-6923 URL: https://issues.apache.org/jira/browse/KAFKA-6923 Project

[jira] [Created] (KAFKA-6921) Remove old Scala producer and all related code, tests, and tools

Ismael Juma created KAFKA-6921: -- Summary: Remove old Scala producer and all related code, tests, and tools Key: KAFKA-6921 URL: https://issues.apache.org/jira/browse/KAFKA-6921 Project: Kafka

Re: [VOTE] KIP-282: Add the listener name to the authentication context

Thanks for the KIP, +1 (binding). Ismael On Wed, Apr 25, 2018 at 1:52 AM Mickael Maison wrote: > Hi, > > There has been no objections in the DISCUSS thread so I'd like to > start a vote on KIP-282: > >

Re: [VOTE] KIP-283: Efficient Memory Usage for Down-Conversion

Thanks for the KIP Dhruvil, this is a welcome improvement! My understanding is that you have done some work to validate that the change has the desired effect, it would be good to include that information in the "Testing Strategy" section. +1 (binding) Ismael On Wed, May 2, 2018 at 9:27 AM

[jira] [Resolved] (KAFKA-5907) Support aggregatedJavadoc in Java 9

[ https://issues.apache.org/jira/browse/KAFKA-5907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-5907. Resolution: Fixed [~omkreddy] It does seem to work now, so will mark it as resolved. > Supp

Re: [VOTE] KIP-235 Add DNS alias support for secured connection

Thanks for the KIP, Jonathan. It would be helpful to have more detail on how SSL authentication could be broken if the new behaviour is the default. I know this was discussed in the mailing list thread, but it's important to include it in the KIP since it's the main reason why a new config is

Re: [VOTE] KIP-281: ConsumerPerformance: Increase Polling Loop Timeout and Make It Reachable by the End User

Thanks for the KIP, +1 (binding). A few suggestions: 1. We normally include the time unit in configs. Not sure if we do it for command line parameters though, so can we please verify and make it consistent? 2. The KIP mentions --polling-loop-timeout and --timeout. Which is it? 3. Can we include

Re: [VOTE] KIP-294 - Enable TLS hostname verification by default

Thanks for the KIP, +1 (binding) from me. Ismael On Wed, May 9, 2018 at 8:29 AM Rajini Sivaram wrote: > Hi all, > > Since there have been no objections on this straightforward KIP, I would > like to initiate the voting process. KIP-294 proposes to use a secure >

[jira] [Resolved] (KAFKA-6828) Index files are no longer sparse in Java 9/10 due to OpenJDK regression

[ https://issues.apache.org/jira/browse/KAFKA-6828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-6828. Resolution: Fixed Great! Let's close this then. > Index files are no longer sparse in Java 9

Re: Use of a formatter like Scalafmt

Sounds good about doing this for Kafka streams scala first. Core is a bit more complicated so may require more discussion. Ismael On Wed, 9 May 2018, 16:59 Matthias J. Sax, wrote: > Joan, > > thanks for starting this initiative. I am overall +1 > > However, I am worried

Re: [VOTE] KIP-283: Efficient Memory Usage for Down-Conversion

Maybe it should message instead of record to be consistent with message.format.version. On Wed, 9 May 2018, 09:04 Jason Gustafson, wrote: > Hi Dhruvil, > > Thanks for the KIP. +1 from me. Just a minor nitpick on the name of the new > config. I would suggest

[jira] [Resolved] (KAFKA-6879) Controller deadlock following session expiration

[ https://issues.apache.org/jira/browse/KAFKA-6879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-6879. Resolution: Fixed > Controller deadlock following session expirat

[jira] [Resolved] (KAFKA-6390) Update ZooKeeper to 3.4.11, Gradle and other minor updates

[ https://issues.apache.org/jira/browse/KAFKA-6390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-6390. Resolution: Fixed > Update ZooKeeper to 3.4.11, Gradle and other minor upda

[jira] [Reopened] (KAFKA-4041) kafka unable to reconnect to zookeeper behind an ELB

[ https://issues.apache.org/jira/browse/KAFKA-4041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reopened KAFKA-4041: > kafka unable to reconnect to zookeeper behind an

Re: Java 10 replacing Java 9 in Jenkins for trunk

gt; if (JavaVersion.current().isJava9Compatible()) > options.compilerArgs << "--release" << "7" > > If so, we need to adjust it. > > Cheers > > On Mon, Apr 9, 2018 at 9:46 AM, Ismael Juma <ism...@juma.me.uk> wrote: > > > Hi a

[jira] [Resolved] (KAFKA-6853) ResponseMetadata calculates latency incorrectly (and therefore ZooKeeperRequestLatencyMs is incorrect)

[ https://issues.apache.org/jira/browse/KAFKA-6853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-6853. Resolution: Fixed > ResponseMetadata calculates latency incorrectly (and theref

[jira] [Resolved] (KAFKA-6855) Kafka fails to start due to faulty Java version detection

[ https://issues.apache.org/jira/browse/KAFKA-6855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-6855. Resolution: Fixed Fix Version/s: 1.1.1 2.0.0 Thanks for the report

Re: [VOTE] KIP-282: Add the listener name to the authentication context

ListenerName is in an internal package, so we would have to move it before exposing it in a public API. Ismael On Wed, 25 Apr 2018, 01:52 Mickael Maison, wrote: > Hi, > > There has been no objections in the DISCUSS thread so I'd like to > start a vote on KIP-282: >

Re: [DISCUSS] KIP-219 - Improve Quota Communication

Hi Jon, Not sure about this approach. It's worth mentioning this in the vote thread as well so that the people who voted originally have a chance to comment. Also, we should really get input from developers of Kafka clients (librdkafka, kafka-python, etc.) for this KIP. Ismael On Thu, Apr 5,

[jira] [Resolved] (KAFKA-6796) Surprising UNKNOWN_TOPIC error for produce/fetch requests to non-replicas

[ https://issues.apache.org/jira/browse/KAFKA-6796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-6796. Resolution: Fixed Fix Version/s: 1.2.0 > Surprising UNKNOWN_TOPIC error for produce/fe

Re: [VOTE] Kafka 2.0.0 in June 2018

votes On Wed, Apr 18, 2018 at 11:35 AM, Ismael Juma <ism...@juma.me.uk> wrote: > Hi all, > > I started a discussion last year about bumping the version of the June > 2018 release to 2.0.0[1]. To reiterate the reasons in the original post: > > 1. Adopt KIP-118 (Drop Su

Re: [DISCUSS] KIP-278: Add version option to Kafka's commands

FYI, the injection via the build process that is mentioned here already happens. See AppInfoParser. Ismael On Mon, Apr 23, 2018 at 9:39 AM, Colin McCabe wrote: > Hi Sasaki, > > Thanks for the KIP. I think a version flag is a good idea. > > Can you give a little more detail

[jira] [Reopened] (KAFKA-2334) Prevent HW from going back during leader failover

[ https://issues.apache.org/jira/browse/KAFKA-2334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reopened KAFKA-2334: > Prevent HW from going back during leader failo

[VOTE] Kafka 2.0.0 in June 2018

Hi all, I started a discussion last year about bumping the version of the June 2018 release to 2.0.0[1]. To reiterate the reasons in the original post: 1. Adopt KIP-118 (Drop Support for Java 7), which requires a major version bump due to semantic versioning. 2. Take the chance to remove

Re: [VOTE] KIP-279: Fix log divergence between leader and follower after fast leader fail over

Thanks for the detailed KIP. +1 (binding) Ismael On Sat, Apr 14, 2018 at 3:54 PM, Anna Povzner wrote: > Hi All, > > > I would like to start the vote on KIP-279: Fix log divergence between > leader and follower after fast leader fail over. > > > For reference, here's the KIP

Re: [VOTE] KIP-270 A Scala wrapper library for Kafka Streams

Thanks for the contribution. I haven't reviewed all the new APIs in detail, but the general approach sounds good to me. +1 (binding). Ismael On Wed, Apr 11, 2018 at 3:09 AM, Debasish Ghosh < debasish.gh...@lightbend.com> wrote: > Hello everyone - > > This is in continuation to the discussion

[jira] [Created] (KAFKA-6772) Broker should load credentials from ZK before requests are allowed

Ismael Juma created KAFKA-6772: -- Summary: Broker should load credentials from ZK before requests are allowed Key: KAFKA-6772 URL: https://issues.apache.org/jira/browse/KAFKA-6772 Project: Kafka

Java 10 replacing Java 9 in Jenkins for trunk

Hi all, Java 10 was recently released and support for Java 9 has ended since it's not a LTS release. I've added a kafka-trunk Jenkins job for Java 10 and disabled the Java 9 job. I also added a PR Jenkins job for Java 10 and will soon disable the Java 9 PR job. The general idea is to have a

[jira] [Created] (KAFKA-6763) Consider using direct byte buffers in SslTransportLayer

Ismael Juma created KAFKA-6763: -- Summary: Consider using direct byte buffers in SslTransportLayer Key: KAFKA-6763 URL: https://issues.apache.org/jira/browse/KAFKA-6763 Project: Kafka Issue Type

Re: [DISCUSS] KIP-257 - Configurable Quota Management

have updated the KIP to reflect this. > > Let me know if there are any concerns. > > Thanks, > > Rajini > > On Thu, Apr 5, 2018 at 1:04 PM, Rajini Sivaram <rajinisiva...@gmail.com> > wrote: > > > Thanks, Ismael. > > > > I have updated the KIP an

Re: [DISCUSS] KIP-257 - Configurable Quota Management

Sounds good to me Rajini. Good catch spotting this before it's included in a release. :) Ismael On Wed, Apr 4, 2018 at 11:13 AM, Rajini Sivaram wrote: > For compatibility reasons, we are now using Java rather than Scala for all > pluggable interfaces including those on

Re: Permissions to edit KIP page / add pages

Done. On Wed, Apr 4, 2018 at 3:41 AM, Moshe Blumberg wrote: > https://cwiki.apache.org/confluence/display/KAFKA/ > Kafka+Improvement+Proposals > > Can you please add permissions to the following users: > > mine: >

Re: Permission request

Done. On Wed, Apr 4, 2018 at 2:04 AM, Alex Dunayevsky wrote: > Hello, > > I would like to add a KIP for kafka-consumer-perf-test according to this > PR: > https://github.com/apache/kafka/pull/4818 > (please check the details in comments) but do not have a permission to >

[jira] [Reopened] (KAFKA-6390) Update ZooKeeper to 3.4.11, Gradle and other minor updates

[ https://issues.apache.org/jira/browse/KAFKA-6390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reopened KAFKA-6390: > Update ZooKeeper to 3.4.11, Gradle and other minor upda

Re: [DISCUSS] KIP-277 - Fine Grained ACL for CreateTopics API

Thanks for the KIP. I think this is going in the right direction, but we need a better compatibility story. Also, it's worth considering whether we want to tackle better wildcard support at the same time. Ismael On Thu, Mar 29, 2018 at 6:51 AM, Edoardo Comar wrote: > Hi all,

Re: [ANNOUNCE] Apache Kafka 1.1.0 Released

Netflix, Pinterest, Rabobank, > > Target, The New York Times, Uber, Yelp, and Zalando, among others. > > > > > A big thank you for the following 120 contributors to this release! > > > Adem Efe Gencer, Alex Good, Andras Beni, Andy Bryant, Antony Stubbs, > > Apurva M

Re: [DISCUSS] KIP-273 Kafka to support using ETCD beside Zookeeper

Here's a link to the previous discussion: https://lists.apache.org/thread.html/2bc187040051008452b40b313db06b476c248ef7a5ed7529afe7b118@1448997154@%3Cdev.kafka.apache.org%3E Ismael On Wed, Mar 28, 2018 at 10:40 AM, Ismael Juma <ism...@juma.me.uk> wrote: > Hi Gwen, > > I don't th

Re: [ANNOUNCE] New Committer: Dong Lin

Congratulations Dong! Thanks for your contributions so far and looking forward to future ones. Ismael On Wed, 28 Mar 2018, 10:58 Becket Qin, wrote: > Hello everyone, > > The PMC of Apache Kafka is pleased to announce that Dong Lin has accepted > our invitation to be a new

Re: [DISCUSS] KIP-273 Kafka to support using ETCD beside Zookeeper

the big change is a new public > API. But it's difficult to judge from the KIP if the API is a good one > because it is built to 100% match the one implementation we have. I'm > curious if the plan includes contributing the Etcd module to Apache Kafka? > > > On Wed, Mar 28,

Re: [DISCUSS] KIP-273 Kafka to support using ETCD beside Zookeeper

Thanks for the KIP. This was proposed previously via "KIP-30 Allow for brokers to have plug-able consensus and meta data storage sub systems" and the community was not in favour. Have you considered the points discussed then? Ismael On Wed, Mar 28, 2018 at 9:18 AM, Molnár Bálint

Re: [DISCUSSION] KIP-266: Add TimeoutException to KafkaConsumer#position()

; that the > > > shortcomings for this approach would be similar to what we faced if we > > let > > > request.timeout.ms control all method timeouts. In comparison, adding > > > overloads > > > does not have this problem. > > > > >

[jira] [Resolved] (KAFKA-6683) ReplicaFetcher crashes with "Attempted to complete a transaction which was not started"

[ https://issues.apache.org/jira/browse/KAFKA-6683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-6683. Resolution: Fixed Fix Version/s: 1.1.0 > ReplicaFetcher crashes with "Attempted to

Re: Kafka version and JDK version

Hi Stephane, I don't see why we would increment Kafka versions as quick as Java versions. The way I think it should work is that we support LTS versions for a long time and only support the most recent non LTS version. The latter is to ensure that we catch any issues with newer Java releases

Re: [DISCUSS] KIP-263: Allow broker to skip sanity check of inactive segments on broker startup

Clarificarion, it's a by name parameter so nothing happens unless the first parameter evaluates to false. Ismael On Mon, 19 Mar 2018, 19:21 Jay Kreps, wrote: > Optimizing startup seems really valuable but I'm a little confused by this. > > There are two different things: >

Re: [DISCUSSION] KIP-266: Add TimeoutException to KafkaConsumer#position()

Hi, An option that is not currently covered in the KIP is to have a separate config max.block.ms, which is similar to the producer config with the same name. This came up during the KAFKA-2391 discussion. I think it's clear that we can't rely on request.timeout.ms, so the decision is between

Re: Subject: [VOTE] 1.1.0 RC3

Vahid, The Java 9 Connect issue is similar to the one being fixed for Trogdor in the following PR: https://github.com/apache/kafka/pull/4725 We need to do something similar for Connect. Ismael On Fri, Mar 16, 2018 at 3:10 PM, Vahid S Hashemian < vahidhashem...@us.ibm.com> wrote: > Hi Damian,

Re: [DISCUSS] KIP-270 A Scala wrapper library for Kafka Streams

>>>> this KIP is accepted then perhaps a PR to that project could be > >>> made > >>>>> to > >>>>>>>> support the new wrapper implementations. > >>>>>>>> > >>>>>>>> https://github.com/manub/scalatest-embedded

Re: [DISCUSS] KIP-270 A Scala wrapper library for Kafka Streams

e > names .. > > regards. > > > > On Fri, Mar 16, 2018 at 10:28 PM, Ismael Juma <ism...@juma.me.uk> wrote: > > > What does "mixed mode application" mean? What are the cases where a user > > would want to use both APIs? I think that would help unders

Re: [DISCUSS] KIP-270 A Scala wrapper library for Kafka Streams

What does "mixed mode application" mean? What are the cases where a user would want to use both APIs? I think that would help understand the reasoning. Thanks, Ismael On Fri, Mar 16, 2018 at 8:48 AM, Debasish Ghosh < debasish.gh...@lightbend.com> wrote: > Hi Damian - > > We could. But in case

Re: [DISCUSS] KIP-270 A Scala wrapper library for Kafka Streams

Thanks for the KIP! It will be nice to have an API for Kafka Streams that is more concise _and_ safer. Like Damian, I would prefer if we didn't have a suffix and relied on package names. However, if there's a good reason why this won't work well, we should explain it in the "Rejected

Re: [VOTE] 1.1.0 RC1

Thanks Jeff: https://github.com/apache/kafka/pull/4678 Ismael On Fri, Mar 9, 2018 at 1:56 AM, Damian Guy wrote: > Hi Jeff, > > Thanks, we will look into this. > > Regards, > Damian > > On Thu, 8 Mar 2018 at 18:27 Jeff Chao wrote: > > > Hello, > > >

Re: [ANNOUNCE] Apache Kafka 1.0.1 Released

, among others. > > > > A big thank you for the following 36 contributors to this release! > > Alex Good, Andras Beni, Andy Bryant, Arjun Satish, Bill Bejeck, Colin P. > Mccabe, Colin Patrick McCabe, ConcurrencyPractitioner, Damian Guy, Daniel > Wojda, Dong Lin, Edoardo Comar, Ew

[jira] [Resolved] (KAFKA-4974) System test failure in 0.8.2.2 upgrade tests

[ https://issues.apache.org/jira/browse/KAFKA-4974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-4974. Resolution: Fixed > System test failure in 0.8.2.2 upgrade te

[jira] [Created] (KAFKA-6616) kafka-merge-pr.py should use GitHub's REST API to merge

Ismael Juma created KAFKA-6616: -- Summary: kafka-merge-pr.py should use GitHub's REST API to merge Key: KAFKA-6616 URL: https://issues.apache.org/jira/browse/KAFKA-6616 Project: Kafka Issue Type

Re: [VOTE] KIP-186: Increase offsets retention default to 7 days

+1 (binding) Ismael On Mon, Mar 5, 2018 at 11:35 AM, Ewen Cheslack-Postava wrote: > I'd like to kick off voting for KIP-186: > https://cwiki.apache.org/confluence/display/KAFKA/KIP- > 186%3A+Increase+offsets+retention+default+to+7+days > > This is the trivial fix that people

Re: [VOTE] 1.0.1 RC2

Thanks for running the release Ewen! Ismael On Fri, Mar 2, 2018 at 10:10 AM, Ewen Cheslack-Postava wrote: > Thanks everyone for voting. This passes with 3 binding +1, 5 non-binding > +1, and no dissenting votes. > > I'll work on getting the release finalized and send out an

Re: [VOTE] KIP-171 - Extend Consumer Group Reset Offset for Stream Application

a > > Y / N (or yes or no) input from the command-line. Then, if the --execute > > flag is passed, we skip this. That seems 99% compatible, and also > > accomplishes the goal of making the tool less confusing. > > > > best, > > Colin > > > > >

Re: [VOTE] KIP-171 - Extend Consumer Group Reset Offset for Stream Application

Yes, let's revert the incompatible changes. There was no mention of compatibility impact on the KIP and we should ensure that is the case for 1.1.0. Ismael On Thu, Feb 22, 2018 at 9:55 AM, Jason Gustafson wrote: > I know it's a been a while since this vote passed, but I

Re: Do the Jackson security vulnerabilities affect Kafka at all?

Hi Jeff, Have you checked trunk and 1.1? They should be using the latest version. Ismael On Tue, Feb 20, 2018 at 10:38 PM, Jeff Widman wrote: > The Jackson JSON parser library had a couple of CVE's announced: > 1. CVE-2017-7525 > 2. CVE 2017-15095 > > Here's a skimmable

[jira] [Resolved] (KAFKA-6430) Improve Kafka GZip compression performance

[ https://issues.apache.org/jira/browse/KAFKA-6430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-6430. Resolution: Fixed Fix Version/s: 1.1.0 > Improve Kafka GZip compression performa

Re: 1.1 release progress

Sounds good. Thanks Becket. Ismael On 15 Feb 2018 5:30 pm, "Becket Qin" <becket@gmail.com> wrote: > Hi Ismael, > > Yes, I am working on the fix. Will submit patch today. > > Thanks, > > Jiangjie (Becket) Qin > > On Thu, Feb 15, 2018 at 2:5

<    5   6   7   8   9   10   11   12   13   14   >