Transitioning from Java 10 to Java 11 in Jenkins

Hi all, Java 11 was released recently and Java 10 is no longer supported. Java 11 is the first LTS release since the new Java release cadence was announced. As of today, all of our tests pass with Java 11 so it's time to transition Jenkins builds to use Java 11 instead of Java 10. I have updated t

Re: Transitioning from Java 10 to Java 11 in Jenkins

support was added in 1.0 and kafka-pr-jdk11-scala2.12 replaced this in 2.1 and newer. https://builds.apache.org/job/kafka-pr-jdk11-scala2.12: Enabled for trunk, 2.1 and newer release branches. Java 11 support was added in 2.1. Ismael On Wed, Oct 10, 2018 at 1:47 PM Ismael Juma wrote: > Hi

Re: [ANNOUNCE] New Committer: Manikumar Reddy

Congratulations Manikumar! Thanks for your continued contributions. Ismael On Thu, Oct 11, 2018 at 10:39 AM Jason Gustafson wrote: > Hi all, > > The PMC for Apache Kafka has invited Manikumar Reddy as a committer and we > are > pleased to announce that he has accepted! > > Manikumar has contrib

Re: Build failed in Jenkins: kafka-trunk-jdk8 #3137

I configured Jenkins to delete the workspace once as it looks like the Git checkout was corrupted. Ismael On Sun, Oct 14, 2018 at 7:13 AM Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See > > ---

Re: [DISCUSS] 2.0.1 bug fix release

Thanks for managing the release Manikumar! Ismael On Tue, 16 Oct 2018, 12:13 Manikumar, wrote: > Hi all, > > I would like to volunteer to be the release manager for 2.0.1 bug fix > release. > 2.0 was released July 30, 2018 and 44 issues are fixed so far. > > Please find all the resolved tickets

Re: [VOTE] KIP-369 Alternative Partitioner to Support "Always Round-Robin" Selection

Thanks for the KIP. Can you please elaborate on the need for the key in this case? The KIP simply states that the key is needed for metadata, but doesn't give any more details. Ismael On Tue, Sep 4, 2018 at 3:39 AM M. Manna wrote: > Hello, > > I have made necessary changes as per the original d

Re: Throwing away prefetched records optimisation.

Hi, I think a KIP to discuss a concrete proposal makes sense. One suggestion is to explore the possibility of fixing the issue without a new config. Would that break existing users? Generally, we should strive for avoiding configs if at all possible. Ismael On 16 Oct 2018 12:30 am, "Zahari Diche

Re: [VOTE] 2.0.1 RC0

Since that was just a system tests fix, it doesn't seem to require another RC. We just need a couple more votes. I'll ping some PMC members. Ismael On Wed, Nov 7, 2018 at 5:01 AM Manikumar wrote: > KAFKA-7581, KAFKA-7579 are not blockers for 2.0.1 release. KAFKA-7579 got > fixed on 2.0 branch.

Re: [VOTE] 2.0.1 RC0

Manikumar, looks like you have the necessary votes. :) Ismael On Wed, Nov 7, 2018, 10:45 AM Rajini Sivaram +1 (binding) > > Checked source build and unit tests. Ran quickstart with source and binary. > > Thank you for managing the release, Manikumar! > > Regards, > > Rajini > > On Wed, Nov 7, 20

Re: [DISCUSS] KIP-388 Add observer interface to record request and response

I agree, the current KIP doesn't discuss the public API that we would be exposing and it's extensive if the normal usage would allow for casting AbstractRequest into the various subclasses and potentially even accessing Records and related for produce request. There are many use cases where this c

Heads up: javac warnings are now treated as errors

Hi all, As part of KAFKA-7612, all javac warnings were fixed or suppressed. To prevent them from reappearing, javac warnings are now treated as errors. We still have some scalac warnings (see KAFKA-7614 for details on what's needed to eliminate them) and 3 xlint warnings are not yet enabled (KAFKA

Re: [VOTE] 2.1.0 RC1

Hi Dong, I was looking through the Maven repository for 2.1.0 and there are some weird files there that didn't exist in 2.0.1: kafka_2.12-2.1.0.mapping Fri Nov 09 23:08:52 UTC 2018 198 kafka_2.12-2.1.0.mapping.asc Fri Nov 09 23:09:03 UTC 2018 821 kafka_2.12-2.1.0.mapping.asc.md5 Fri Nov 09 23:09:

Re: [ANNOUNCE] Apache Kafka 2.1.0

sei Izmalkin, Alex Dunayevsky, Amit Sela, Andras > Katona, Andy Coates, Anna Povzner, Arjun Satish, Attila Sasvari, Aviem Zur, > Bibin Sebastian, Bill Bejeck, Bob Barrett, Brandon Kirchner, Bridger > Howell, Chia-Ping Tsai, Colin Hicks, Colin Patrick McCabe, Dhruvil Shah, > Dong Lin, Edo

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

Thanks for the KIP, this is helpful. A few questions: 1. Have we considered whether we want to allow a similar topic config? 2. Can we rely on a method from the library to pick the default compression level if compression.level is not set? We do it for gzip and it would seem reasonable to do some

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

gt; > For the problem of the buffer/block size, I have no strong opinion. If the > community needs it, I will do it all together. How do you think? > > In short, it seems like I need to update the KIP document for issue #1 and > update the compression wrapper for issue #2, #3. Is t

Heads up: spotBugs enabled for Java 11 builds

Hi, As per https://issues.apache.org/jira/browse/KAFKA-7389, spotBugs is now enabled for Java 11 builds and the Java 11 PR build will fail for old PRs that don't include the commit from KAFKA-7389. The fix is to rebase/merge. Ismael

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

ld be better to > update the title of the KIP like 'Allow fine-grained configuration for > compression'. Is that right? > > @Other committers: > > Is there any other opinion on allowing the buffer/block size to be > configurable? > > Thanks, > Dongjin > >

Re: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org

Hi Daniel, We moved to Gitbox a while back for kafka and kafka-site. Which repository is still using git-wip-us.apache.org? Ismael On Fri, Dec 7, 2018 at 8:53 AM Daniel Gruno wrote: > [IF YOUR PROJECT DOES NOT HAVE GIT REPOSITORIES ON GIT-WIP-US PLEASE > DISREGARD THIS EMAIL; IT WAS MASS-MAI

Re: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org

Thanks Daniel and Christopher! My bad for missing the header. :) Ismael On Fri, Dec 7, 2018, 9:31 AM Daniel Gruno On 12/7/18 6:28 PM, Ismael Juma wrote: > > Hi Daniel, > > > > We moved to Gitbox a while back for kafka and kafka-site. Which > > repository is still usi

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

guration+for+compression > > Please have a look when you are free. > > Thanks, > Dongjin > > On Mon, Dec 3, 2018 at 12:50 AM Ismael Juma wrote: > > > The updated title sounds fine to me. > > > > Ismael > > > > On Sun, Dec 2, 2018, 5:25 AM Dongjin Lee &g

Re: [DISCUSS] Kafka 2.2.0 in February 2018

Thanks for volunteering Matthias! The plan sounds good to me. Ismael On Tue, Jan 8, 2019, 1:07 PM Matthias J. Sax Hi all, > > I would like to propose a release plan (with me being release manager) > for the next time-based feature release 2.2.0 in February. > > The recent Kafka release history c

Re: [VOTE] KIP-389: Introduce a configurable consumer group size limit

+1 (binding), thanks. On Fri, Jan 11, 2019, 1:09 AM Stanislav Kozlovski Hey folks, > > I'd like to initiate a vote thread about KIP-389 > < > https://cwiki.apache.org/confluence/display/KAFKA/KIP-389%3A+Introduce+a+configurable+consumer+group+size+limit > > > . > > -- > Best, > Stanislav >

Re: [DISCUSS] KIP-402: Improve fairness in SocketServer processors

I think the point is that we distribute the time more fairly between connection handling and other operations where before we could block on the TLS handshake for a long time given a large number of connections. Ismael On Tue, Jan 15, 2019 at 11:39 AM Colin McCabe wrote: > Hi Rajini, > > Thanks

Re: [DISCUSS] 2.1.1 bug-fix release

Thanks for volunteering Colin. There are some important fixes since 2.1.0 so I think this would be great. Ismael On Tue, Jan 15, 2019 at 11:50 AM Colin McCabe wrote: > Hi all, > > I'd like to volunteer to be the release manager for the 2.1.1 bug fix > release. > > 2.1 was released November 20,

Re: [ANNOUNCE] New Committer: Vahid Hashemian

Congratulations Vahid! On Tue, Jan 15, 2019, 2:45 PM Jason Gustafson Hi All, > > The PMC for Apache Kafka has invited Vahid Hashemian as a project > committer and > we are > pleased to announce that he has accepted! > > Vahid has made numerous contributions to the Kafka community over the past >

Re: [VOTE] KIP-402: Improve fairness in SocketServer processors

Thanks for the KIP, +1 (binding). Ismael On Tue, Jan 15, 2019, 3:38 PM Rajini Sivaram Hi all, > > I would like to start vote on KIP-402 to improve fairness in channel > processing in SocketServer to protect brokers from connection storms and > limit the total number of connections in brokers to

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

, Jan 7, 2019 at 6:23 AM Dongjin Lee wrote: > > > Thanks for pointing out Ismael. It's now updated. > > > > Best, > > Dongjin > > > > On Mon, Jan 7, 2019 at 4:36 AM Ismael Juma wrote: > > > >> Thanks Dongjin. One minor suggestion:

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

he above reasons, I think the only alternative is providing options > that can be used when the topic's 'compression.type' is 'producer.' In > other words, adding compression.[gzip, lz4, zstd].level and > compression.[gzip.snappy.lz4].buffer.size options - and it is w

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 would

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 ar

Re: Java 10 replacing Java 9 in Jenkins for trunk

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 wrote: > > > Hi all, > > > > Java 10 was recently released

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 "record.downconversion.enable". The "r

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 about applying it to `co

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 > default value for endpoint ident

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 th

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 neede

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 Dhruv

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: > > https://cwiki.apache.org/confluence/display/KAFKA/KIP-282%3A+Add+the+listener+name+to+the+aut

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 KIP-277 ( > https://www

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: > > https://cwiki.apache.org/confluence/displa

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: [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 storing wildcard-suff

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 realize users of > Dy

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-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

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 to be a breaking chan

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. So

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: 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: [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 ticke

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: > > > https://issues.apache.org/jira/br

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: > > > https://issues.apache.or

Re: [DISCUSS] 0.10.2.2 bug fix release

ecent. 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 criti

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 correc

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

> > is even more confusing. > > > > > > > > > > > > > > > > > > > > > > > > > > I'm +1 for not using `max.block.ms`. I like > > Guozhang's > > > > > > > > > suggestion of >

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 to

Re: [VOTE] 1.1.1 RC0

Thanks Dong. One issue that came up is that Gradle dependency resolution no longer works with Java 7 due to a minimum TLS version change in Maven Central. Gradle 4.8.1 solves the issue ( https://github.com/apache/kafka/pull/5263). This means that if someone tries to build from source with Java 7, i

Re: [VOTE] 0.11.0.3 RC0

+1 (binding) Verified signature of source artifact, ran tests and verified quickstart on source artifact with Java 7, verified quickstart on binary artifact (Scala 2.11) with Java 7, sanity checked release notes and Maven staging repository. Thanks for running the release! Ismael On Fri, Jun 22

Re: [VOTE] 1.0.2 RC1

+1 (binding) Verified signature of source artifact, ran tests and verified quickstart on source artifact with Java 7, verified quickstart on binary artifact (Scala 2.12) with Java 8, sanity checked release notes and Maven staging repository. Ismael On Fri, Jun 29, 2018 at 10:02 PM Matthias J. Sa

Re: [ANNOUNCE] Apache Kafka 0.11.0.3 Released

am, Randall Hauch, tedyu, Jagadesh > Adireddi, Jarek Rudzinski, Jason Gustafson, Jeremy Custenborder, Anna > Povzner, Joel Hamill, John Roesler, Max Zheng, Mickael Maison, Robert > Yokota, Yaswanth Kumar, parafiend, Jiangjie (Becket) Qin, Arjun > Satish, Bill Bejeck, Damian Guy, Gitomain,

Re: [DISCUSS] KIP-334 Include partitions in exceptions raised during consumer record deserialization/validation

Thanks for the KIP, Stanislav. The following PR looks related: https://github.com/apache/kafka/pull/4093/files Ismael On Thu, Jul 5, 2018 at 8:44 AM Stanislav Kozlovski wrote: > Hey everybody, > > I just created a new KIP about exposing more information in exceptions > caused by consumer recor

Re: [kafka-clients] [VOTE] 1.1.1 RC2

Thanks Dong. There are a couple of quickstart links below: https://repository.apache.org/content/groups/staging/org/apache/kafka/ Ismael On Thu, Jul 5, 2018 at 10:32 AM Dong Lin wrote: > Hey everyone, > > Thanks for the vote! Sorry for late reply. I have been trying to understand > whether str

Re: [DISCUSS] KIP-334 Include partitions in exceptions raised during consumer record deserialization/validation

ure to not expose the cause of the exception when not needed, maybe I'll outright remove the `cause` attribute On Thu, Jul 5, 2018 at 4:55 PM Ismael Juma wrote: > Thanks for the KIP, Stanislav. The following PR looks related: > > https://github.com/apache/kafka/pull/4093/files >

Re: [kafka-clients] [VOTE] 1.1.1 RC2

go? If so, can we get another +1 from PMC? > > Thanks! > Dong > > On Thu, Jul 5, 2018 at 10:38 AM, Ismael Juma wrote: > Thanks Dong. There are a couple of quickstart links below: >> >> https://repository.apache.org/content/groups/staging/org/apache/kafka/ >> >>

Re: [VOTE] KIP-331 Add default implementation to close() and configure() for Serializer, Deserializer and Serde

Thanks for the KIP. I think we should be thinking about https://issues.apache.org/jira/browse/KAFKA-6923 at the same time. Ismael On Thu, 5 Jul 2018, 07:45 Chia-Ping Tsai, wrote: > hi all, > > I would like to start voting on "KIP-331 Add default implementation to > close() and configure() for S

Re: [VOTE] KIP-280: Enhanced log compaction

Thanks for the KIP, Luis. A brief comment below. On Wed, Jul 4, 2018 at 11:11 AM Luís Cabral wrote: > As a reader, I tend to prefer brief documentation on new features (they > tend to be too many for me to find the willpower to read a 200-page essay > about each one), so that influences me to av

Re: Old deprecated producer

The old Scala producers were removed in 2.0.0. The Java producer supports batching. Ismael On Sat, 7 Jul 2018, 05:38 jna, wrote: > Hello, > > I'm using the old producer API, and i saw since a long time (few > versions) that this API is deprecated. When will you decide to remove > this old API?

Re: [VOTE] KIP-331 Add default implementation to close() and configure() for Serializer, Deserializer and Serde

The KIP needs 3 binding votes to pass. I still think we should include the details of how things will look like with the headers being passed to serializers/deserializers to ensure things actually make sense as a whole. Ismael On Sun, 8 Jul 2018, 18:31 Chia-Ping Tsai, wrote: > All, > > The 72

Re: [DISCUSSION] KIP-336: Consolidate ExtendedSerializer/Serializer and ExtendedDeserializer/Deserializer

Thanks for the KIP. It would be helpful to understand the user experience for the case where the implementor uses the headers. It seems like it would require overriding two methods? Ismael On Mon, Jul 9, 2018 at 1:50 AM Viktor Somogyi wrote: > Hi folks, > > I've published KIP-336 which is about

Re: [VOTE] KIP-231: Improve the Required ACL of ListGroups API

Late +1 (binding) from me too. Ismael On Mon, Jul 9, 2018 at 3:18 PM Vahid S Hashemian wrote: > KIP-231 is approved with 3 "+1" binding votes by Ewen, Jason, and Harsha. > > Thanks to everyone who provided feedback and/or voted. > > Regards. > --Vahid > > > > > From: Vahid S Hashemian/Silicon

Re: [VOTE] 2.0.0 RC2

Hi Rajini, Thanks for generating the RC. It seems like the kafka-streams-scala 2.12 artifact is missing from the Maven repository: https://repository.apache.org/content/groups/staging/org/apache/kafka/ Since this is the first time we are publishing this artifact, it is possible that this never w

Re: [DISCUSSION] KIP-336: Consolidate ExtendedSerializer/Serializer and ExtendedDeserializer/Deserializer

give up the @FunctionalInterface > annotation and we'll end up with an interface with no abstract methods but > only defaults. > What do you think? > > Cheers, > Viktor > > > On Mon, Jul 9, 2018 at 11:02 AM Ismael Juma wrote: > > > Thanks for the KIP. I

Re: [VOTE] 1.1.1 RC3

+1 (binding) Verified signature of source artifact, ran tests and verified quickstart on source artifact with Java 8, verified quickstart on binary artifact (Scala 2.12) with Java 8, sanity checked release notes and Maven staging repository. Thanks for managing the release Dong! Ismael On Sun,

Re: [VOTE] 2.0.0 RC2

ael, > > Thank you for pointing that out. I have re-uploaded the RC2 artifacts to > maven including streams-scala_2.12. Also submitted a PR to update build & > release scripts to include this. > > Thank you, > > Rajini > > > > On Fri, Jul 13, 2018 at 7

Re: [ANNOUNCE] Apache Kafka 1.1.1 Released

et data > between > systems or applications. > > ** Building real-time streaming applications that transform or react > to the streams > of data. > > > Apache Kafka is in use at large and small companies worldwide, including > Capital One, Goldman Sachs, ING, LinkedIn, Netf

Re: [VOTE] KIP-331 Add default implementation to close() and configure() for Serializer, Deserializer and Serde

his kip. Please correct > me if I didn't catch what you said. > > Cheers, > Chia-Ping > > On 2018/07/09 01:55:41, Ismael Juma wrote: > > The KIP needs 3 binding votes to pass. I still think we should include > the > > details of how things will look like with the

Re: Question about issues of Kafka release version 1.1.1

Seems like you're right Lambdaliu. Rajini/Jason, can you please check and update the JIRAs? Ismael On Mon, Jul 23, 2018 at 7:09 AM lambdaliu(刘少波) wrote: > Hi team, > > I Have downloaded the source release of kafka version 1.1.1 and found the > JIRA > issues KAFKA-6911 and KAFKA-6809 listed in t

Re: Build failed in Jenkins: kafka-trunk-jdk10 #342

Seems like the git repository was corrupt. I forced a fresh clone and the build is proceeding. Ismael On Sat, Jul 28, 2018 at 8:37 AM Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See > > ---

Re: [ANNOUNCE] Apache Kafka 2.0.0 Released

vzner, Arjun Satish, asutosh936, > > Attila Sasvari, bartdevylder, Benedict Jin, Bill Bejeck, Blake Miller, > > Boyang Chen, cburroughs, Chia-Ping Tsai, Chris Egerton, Colin P. Mccabe, > > Colin Patrick McCabe, ConcurrencyPractitioner, Damian Guy, dan norwood, > > Daniel Sh

Re: KIP-352: Distinguish URPs caused by reassignment

Thanks Jason. This is definitely a pain point. I actually prefer the option to redefine what under-replicated means (currently under rejected alternatives). Also, do we need to make changes to what we store in ZK? If so, that should be in the KIP too. Ismael On Thu, Aug 2, 2018 at 11:45 AM Jason

Re: KIP-352: Distinguish URPs caused by reassignment

to > > partition them based on the replication factor. Do you see any problems > > with this? > > > > -Jason > > > > > > On Thu, Aug 2, 2018 at 12:14 PM, Ismael Juma wrote: > > > > > Thanks Jason. This is definitely a pain point. I actually

Re: [DISCUSS] KIP-232: Detect outdated metadata by adding ControllerMetadataEpoch field

On Fri, Jan 5, 2018 at 7:15 PM, Jason Gustafson wrote: > > class OffsetAndMetadata { > long offset; > byte[] offsetMetadata; > String metadata; > } > Admittedly, the naming is a bit annoying, but we can probably come up with > something better. Internally the byte array would have a versio

Re: [DISCUSS] KIP 226 - Dynamic Broker Configuration

Hi Rajini, Quick question (sorry if this was already discussed). How were the following chosen? Name: password.encoder.keyfactory.algorithm Type: String Default: PBKDF2WithHmacSHA512 if available, otherwise PBKDF2WithHmacSHA1 (e.g. Java7) Name: password.encoder.cipher.algorithm Type: String De

Re: [DISCUSS] KIP 226 - Dynamic Broker Configuration

Thanks Rajini. Sounds good. Ismael On Wed, Jan 10, 2018 at 11:41 AM, Rajini Sivaram wrote: > Hi Ismael, > > I have updated the KIP to use AES-256 if available and AES-128 otherwise > for password encryption. Looking at GCM, it looks like GCM is typically > used with a variable initialization ve

Re: [DISCUSS] February Release Plan

Thanks for volunteering Damian! On Fri, Jan 12, 2018 at 11:04 AM, Damian Guy wrote: > Hi all, > > I would like to volunteer to be the release manager > for our next time-based feature release (v1.1.0). See > https://cwiki.apache.org/ > confluence/display/KAFKA/Time+Based+Release+Plan if you miss

Re: [ANNOUNCE] New committer: Matthias J. Sax

Congratulations Matthias! On 12 Jan 2018 10:59 pm, "Guozhang Wang" wrote: > Hello everyone, > > The PMC of Apache Kafka is pleased to announce Matthias J. Sax as our > newest Kafka committer. > > Matthias has made tremendous contributions to Kafka Streams API since early > 2016. His footprint ha

Re: [ANNOUNCE] New Kafka PMC Member: Rajini Sivaram

Congratulations Rajini! On 17 Jan 2018 10:49 am, "Gwen Shapira" wrote: Dear Kafka Developers, Users and Fans, Rajini Sivaram became a committer in April 2017. Since then, she remained active in the community and contributed major patches, reviews and KIP discussions. I am glad to announce that

Re: [VOTE] KIP-227: Introduce Fetch Requests that are Incremental to Increase Partition Scalability

Thanks for the KIP, +1 (binding). On Tue, Dec 19, 2017 at 7:28 PM, Colin McCabe wrote: > Hi all, > > I'd like to start the vote on KIP-227: Incremental Fetch Requests. > > The KIP is here: https://cwiki.apache.org/confluence/display/KAFKA/KIP- > 227%3A+Introduce+Incremental+FetchRequests+to+Incr

Re: [VOTE] KIP-227: Introduce Fetch Requests that are Incremental to Increase Partition Scalability

Colin, You get a cumulative count for rates since we added https://cwiki.apache.org/confluence/display/KAFKA/KIP-187+-+Add+cumulative+count+metric+for+all+Kafka+rate+metrics Ismael On Tue, Jan 23, 2018 at 4:21 PM, Colin McCabe wrote: > On Tue, Jan 23, 2018, at 11:57, Jun Rao wrote: > > Hi, Col

Re: [DISCUSS] KIP 226 - Dynamic Broker Configuration

1,k2=v2* > > If anyone has any concerns about these options being added to > kafka-configs.sh, please let me know. Otherwise, I will update KIP-226 and > add the options to one of the KIP-226 PRs. > > Thank you, > > Rajini > > On Wed, Jan 10, 2018 at 5:14 AM, Ismael Juma

Re: [VOTE] KIP-86: Configurable SASL callback handlers

Thanks for the KIP, Rajini. This is a useful improvement, so +1 (binding) from me. I really don't like how the Java Security classes work, so I would have preferred to avoid emulating them, but the KIP is consistent with previous related KIPs and that's the direction we chose previously. Also, I t

Re: [VOTE] KIP-227: Introduce Fetch Requests that are Incremental to Increase Partition Scalability

gt; > > On Tue, Jan 23, 2018, at 21:47, Ismael Juma wrote: > > > Colin, > > > > > > You get a cumulative count for rates since we added > > > https://cwiki.apache.org/confluence/display/KAFKA/KIP- > > 187+-+Add+cumulative+count+metric+for+all+Kafka+rate

Re: Excessive Memory Usage with Compression enabled and possible resolutions

Thanks for the report. I haven't looked at the code, but it seems like we would want to do both 1 and 2. Can you please file a JIRA with 1.1.0 as the target version? Ismael On 30 Jan 2018 5:46 pm, "Kyle Tinker" wrote: > I'm using Kafka 1.0.0 and the Java producer. > > I've noticed high memory u

Re: Excessive Memory Usage with Compression enabled and possible resolutions

u need > any additional information. I'm new to this project so hopefully the > format is what you were looking for. > > - Kyle > > -Original Message- > From: Ismael Juma [mailto:isma...@gmail.com] > Sent: Tuesday, January 30, 2018 9:01 PM > To: dev > Subject: Re:

Re: 1.1 release progress

Hi Becket, Thanks for filing that. Are you working on a fix? Ismael On Thu, Feb 15, 2018 at 2:51 PM, Becket Qin wrote: > Hi Damian, > > I just created another ticket KAFKA-6568, which I believe should also be a > blocker unless people disagree. > > Thanks, > > Jiangjie (Becket) Qin > > On Wed,

Re: 1.1 release progress

Sounds good. Thanks Becket. Ismael On 15 Feb 2018 5:30 pm, "Becket Qin" 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:53 PM, Ismael Juma wrote: > >

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 summary: > https://adam

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 think we need to > recon

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

mand-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 > > > > > > On Thu, Feb 22, 2018, at 10:23, Ism

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 announcement > when

  1   2   3   4   5   6   7   8   9   10   >