[GitHub] kafka pull request: KAFKA-3761: Controller has RunningAsBroker ins...

GitHub user theduderog opened a pull request: https://github.com/apache/kafka/pull/1437 KAFKA-3761: Controller has RunningAsBroker instead of RunningAsController state @junrao @ijuma This works for me in local testing. Do you see any issues? You can merge this pull

[jira] [Work started] (KAFKA-3761) Controller has RunningAsBroker instead of RunningAsController state

[ https://issues.apache.org/jira/browse/KAFKA-3761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-3761 started by Roger Hoover. --- > Controller has RunningAsBroker instead of RunningAsController state >

[jira] [Commented] (KAFKA-2394) Use RollingFileAppender by default in log4j.properties

[ https://issues.apache.org/jira/browse/KAFKA-2394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15303544#comment-15303544 ] Ewen Cheslack-Postava commented on KAFKA-2394: -- [~cotedm] If there are risks with

[jira] [Resolved] (KAFKA-3757) Add new client to "clients" page please

[ https://issues.apache.org/jira/browse/KAFKA-3757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava resolved KAFKA-3757. -- Resolution: Fixed Added to the wiki, thanks for the contribution! > Add new

[jira] [Assigned] (KAFKA-3757) Add new client to "clients" page please

[ https://issues.apache.org/jira/browse/KAFKA-3757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava reassigned KAFKA-3757: Assignee: Ewen Cheslack-Postava > Add new client to "clients" page please

[jira] [Commented] (KAFKA-3740) Add configs for RocksDBStores

[ https://issues.apache.org/jira/browse/KAFKA-3740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15303531#comment-15303531 ] Guozhang Wang commented on KAFKA-3740: -- Sounds good. > Add configs for RocksDBStores >

Jenkins build is back to normal : kafka-trunk-jdk8 #654

See

[jira] [Resolved] (KAFKA-3710) MemoryOffsetBackingStore creates a non-daemon thread that prevents clean shutdown

[ https://issues.apache.org/jira/browse/KAFKA-3710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava resolved KAFKA-3710. -- Resolution: Fixed Fix Version/s: 0.10.1.0 Issue resolved by pull request

[jira] [Commented] (KAFKA-3710) MemoryOffsetBackingStore creates a non-daemon thread that prevents clean shutdown

[ https://issues.apache.org/jira/browse/KAFKA-3710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15303440#comment-15303440 ] ASF GitHub Bot commented on KAFKA-3710: --- Github user asfgit closed the pull request at:

[GitHub] kafka pull request: KAFKA-3710: MemoryOffsetBackingStore shutdown

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1383 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Commented] (KAFKA-3740) Add configs for RocksDBStores

[ https://issues.apache.org/jira/browse/KAFKA-3740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15303428#comment-15303428 ] Henry Cai commented on KAFKA-3740: -- Looks like you want two sets of RocksDB settings, one for K/V store,

Re: [HEADS-UP] Modification to KIP Template

++1 Sent from my iPhone > On May 26, 2016, at 7:24 PM, Gwen Shapira wrote: > > Hi Kafka Developers, > > Just a quick heads-up that I added a new section to the KIP template: "Test > Plans". > I think its a good habit to think about how a feature will be tested while >

[HEADS-UP] Modification to KIP Template

Hi Kafka Developers, Just a quick heads-up that I added a new section to the KIP template: "Test Plans". I think its a good habit to think about how a feature will be tested while planning it. I'm talking about high-level notes on system tests, not gritty details. This will apply to new KIPs,

Re: KAFKA-3744: Message format to identify serializer

Hi David, Thank you for bringing this up. I do agree that improving Kafka's message metadata is important and we are slightly lacking on the story. We don't have built in support for message types, or for tagging messages with things like source host or source cluster (which were frequently

[jira] [Commented] (KAFKA-3740) Add configs for RocksDBStores

[ https://issues.apache.org/jira/browse/KAFKA-3740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15303345#comment-15303345 ] Guozhang Wang commented on KAFKA-3740: -- Some thoughts on the default config values: I think there

[jira] [Commented] (KAFKA-3689) ERROR Processor got uncaught exception. (kafka.network.Processor)

[ https://issues.apache.org/jira/browse/KAFKA-3689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15303301#comment-15303301 ] Jun Rao commented on KAFKA-3689: Hmm, interesting. I assume that all the errors are for the same client

[jira] [Created] (KAFKA-3762) Log.loadSegments() should log the message in exception

Jun Rao created KAFKA-3762: -- Summary: Log.loadSegments() should log the message in exception Key: KAFKA-3762 URL: https://issues.apache.org/jira/browse/KAFKA-3762 Project: Kafka Issue Type:

Re: [DISCUSS] KIP-54 Sticky Partition Assignment Strategy

Hi Guozhang, I was looking at the implementation of StreamsPartitionAssignor through its unit tests and expected to find some tests that - verify stickiness by making at least two calls to the assign() method (so we check the second assign() call output preserves the assignments coming from

[jira] [Created] (KAFKA-3761) Controller has RunningAsBroker instead of RunningAsController state

Ismael Juma created KAFKA-3761: -- Summary: Controller has RunningAsBroker instead of RunningAsController state Key: KAFKA-3761 URL: https://issues.apache.org/jira/browse/KAFKA-3761 Project: Kafka

[jira] [Resolved] (KAFKA-3760) Set broker state as running after publishing to ZooKeeper

[ https://issues.apache.org/jira/browse/KAFKA-3760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-3760. Resolution: Fixed Assignee: Roger Hoover (was: Jun Rao) Reviewer: Jun Rao

[jira] [Commented] (KAFKA-3760) Set broker state as running after publishing to ZooKeeper

[ https://issues.apache.org/jira/browse/KAFKA-3760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15303170#comment-15303170 ] ASF GitHub Bot commented on KAFKA-3760: --- Github user theduderog closed the pull request at:

[GitHub] kafka pull request: KAFKA-3760: Set broker state as running after ...

Github user theduderog closed the pull request at: https://github.com/apache/kafka/pull/1436 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Issue Comment Deleted] (KAFKA-3760) Set broker state as running after publishing to ZooKeeper

[ https://issues.apache.org/jira/browse/KAFKA-3760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Hoover updated KAFKA-3760: Comment: was deleted (was: Create PR: https://github.com/apache/kafka/pull/1436) > Set broker

[jira] [Commented] (KAFKA-3760) Set broker state as running after publishing to ZooKeeper

[ https://issues.apache.org/jira/browse/KAFKA-3760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15303141#comment-15303141 ] Roger Hoover commented on KAFKA-3760: - Create PR: https://github.com/apache/kafka/pull/1436 > Set

[jira] [Commented] (KAFKA-3760) Set broker state as running after publishing to ZooKeeper

[ https://issues.apache.org/jira/browse/KAFKA-3760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15303140#comment-15303140 ] ASF GitHub Bot commented on KAFKA-3760: --- GitHub user theduderog opened a pull request:

[GitHub] kafka pull request: KAFKA-3760: Set broker state as running after ...

GitHub user theduderog opened a pull request: https://github.com/apache/kafka/pull/1436 KAFKA-3760: Set broker state as running after publishing to ZooKeeper Redoing PR #1426 with a JIRA You can merge this pull request into a Git repository by running: $ git pull

[jira] [Updated] (KAFKA-3760) Set broker state as running after publishing to ZooKeeper

[ https://issues.apache.org/jira/browse/KAFKA-3760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Hoover updated KAFKA-3760: Summary: Set broker state as running after publishing to ZooKeeper (was: Setting broker state as

[jira] [Created] (KAFKA-3760) Setting broker state as running after publishing to ZooKeeper

Roger Hoover created KAFKA-3760: --- Summary: Setting broker state as running after publishing to ZooKeeper Key: KAFKA-3760 URL: https://issues.apache.org/jira/browse/KAFKA-3760 Project: Kafka

Jenkins build is back to normal : kafka-trunk-jdk7 #1316

See

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

See Changes: [me] KAFKA-3723: Cannot change size of schema cache for JSON converter -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on ubuntu-4

[jira] [Commented] (KAFKA-3723) Cannot change size of schema cache for JSON converter

[ https://issues.apache.org/jira/browse/KAFKA-3723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15302946#comment-15302946 ] ASF GitHub Bot commented on KAFKA-3723: --- Github user asfgit closed the pull request at:

[jira] [Resolved] (KAFKA-3723) Cannot change size of schema cache for JSON converter

[ https://issues.apache.org/jira/browse/KAFKA-3723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava resolved KAFKA-3723. -- Resolution: Fixed Fix Version/s: 0.10.1.0 Issue resolved by pull request

[GitHub] kafka pull request: KAFKA-3723 Cannot change size of schema cache ...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1401 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Closed] (KAFKA-3137) Delete tombstones in log compacted topics may never get removed.

[ https://issues.apache.org/jira/browse/KAFKA-3137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Cheng closed KAFKA-3137. -- > Delete tombstones in log compacted topics may never get removed. >

[jira] [Resolved] (KAFKA-3137) Delete tombstones in log compacted topics may never get removed.

[ https://issues.apache.org/jira/browse/KAFKA-3137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Cheng resolved KAFKA-3137. Resolution: Invalid > Delete tombstones in log compacted topics may never get removed. >

[jira] [Commented] (KAFKA-3137) Delete tombstones in log compacted topics may never get removed.

[ https://issues.apache.org/jira/browse/KAFKA-3137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15302857#comment-15302857 ] James Cheng commented on KAFKA-3137: Jay was right about this. The compacted segments retain the

Re: [DISCUSS] KIP-62: Allow consumer to send heartbeats from a background thread

Hey Grant, Thanks for the feedback. I'm definitely open to including heartbeat() in this KIP. One thing we should be clear about is what the behavior of heartbeat() should be when the group begins rebalancing. I think there are basically two options: 1. heartbeat() simply keeps heartbeating even

[jira] [Created] (KAFKA-3759) Incorrect JDBC credentials cause Connect worker to permanently fail

Lars George created KAFKA-3759: -- Summary: Incorrect JDBC credentials cause Connect worker to permanently fail Key: KAFKA-3759 URL: https://issues.apache.org/jira/browse/KAFKA-3759 Project: Kafka

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

See Changes: [cshapi] MINOR: Fix wrong comments -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on ubuntu-2 (docker Ubuntu ubuntu yahoo-not-h2) in

[GitHub] kafka pull request: MINOR: Fix tracing in KafkaApis.handle()

GitHub user mimaison opened a pull request: https://github.com/apache/kafka/pull/1435 MINOR: Fix tracing in KafkaApis.handle() requestObj() returns null for the o.a.k.c.requests objects so use header() for these. Once all the requests will have been replaced by

Build failed in Jenkins: kafka-trunk-jdk7 #1315

See Changes: [junrao] Setting broker state as running after publishing to ZK [cshapi] MINOR: Use `--force` instead of `--yes` in `AclCommand` [cshapi] MINOR: Fix wrong comments -- Started by

[jira] [Commented] (KAFKA-3758) KStream job fails to recover after Kafka broker stopped

[ https://issues.apache.org/jira/browse/KAFKA-3758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15302542#comment-15302542 ] Greg Fodor commented on KAFKA-3758: --- Also, the log is truncated at the top to the point where we shut

[jira] [Updated] (KAFKA-3758) KStream job fails to recover after Kafka broker stopped

[ https://issues.apache.org/jira/browse/KAFKA-3758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Greg Fodor updated KAFKA-3758: -- Attachment: muon.log.1.gz > KStream job fails to recover after Kafka broker stopped >

[jira] [Created] (KAFKA-3758) KStream job fails to recover after Kafka broker stopped

Greg Fodor created KAFKA-3758: - Summary: KStream job fails to recover after Kafka broker stopped Key: KAFKA-3758 URL: https://issues.apache.org/jira/browse/KAFKA-3758 Project: Kafka Issue Type:

[jira] [Created] (KAFKA-3757) Add new client to "clients" page please

Vadim Chekan created KAFKA-3757: --- Summary: Add new client to "clients" page please Key: KAFKA-3757 URL: https://issues.apache.org/jira/browse/KAFKA-3757 Project: Kafka Issue Type: Task

[GitHub] kafka pull request: MINOR: Fix wrong comments

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1198 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

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

See Changes: [junrao] Setting broker state as running after publishing to ZK [cshapi] MINOR: Use `--force` instead of `--yes` in `AclCommand` -- Started by an SCM change [EnvInject] - Loading

[jira] [Commented] (KAFKA-3689) ERROR Processor got uncaught exception. (kafka.network.Processor)

[ https://issues.apache.org/jira/browse/KAFKA-3689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15302469#comment-15302469 ] Buvaneswari Ramanan commented on KAFKA-3689: The error manifests in 0.10.0.0 RC6 as well Here

[GitHub] kafka pull request: MINOR: Use `--force` instead of `--yes` in `Ac...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1430 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] kafka pull request: Setting broker state as running after publishi...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1426 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

Re: Kafka Wiki

Done :) On Thu, May 26, 2016 at 7:48 AM, Matthias J. Sax wrote: > Hi, > > can I get write access to the Kafka Wiki? Username is: mjsax > > Thanks. > > -Matthias > >

Re: [DISCUSS] KIP-62: Allow consumer to send heartbeats from a background thread

Hi Jason, Thanks for writing up a proposal (and a thorough one)! This is something that I had been thinking about this week too as I have run into it more than a handful of times now. I like the idea of having a larger processing timeout, that timeout in unison with max.poll.records should in

Kafka Wiki

Hi, can I get write access to the Kafka Wiki? Username is: mjsax Thanks. -Matthias signature.asc Description: OpenPGP digital signature

Re: [kafka-clients] Adding new client to wiki

I believe wiki requests usually go to the kafka dev mailing list (cc'd) On May 26, 2016 6:51 AM, "Vijay Jadhav" wrote: > > > Hi, > > Can someone point out what is procedure for adding "libasynckafkaclient > " (C++ based

[jira] [Commented] (KAFKA-2394) Use RollingFileAppender by default in log4j.properties

[ https://issues.apache.org/jira/browse/KAFKA-2394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15302150#comment-15302150 ] Dustin Cote commented on KAFKA-2394: [~hachikuji] the attached PR removes references to the

[jira] [Commented] (KAFKA-2394) Use RollingFileAppender by default in log4j.properties

[ https://issues.apache.org/jira/browse/KAFKA-2394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15302104#comment-15302104 ] ASF GitHub Bot commented on KAFKA-2394: --- GitHub user cotedm opened a pull request:

[GitHub] kafka pull request: KAFKA-2394: move to RollingFileAppender by def...

GitHub user cotedm opened a pull request: https://github.com/apache/kafka/pull/1434 KAFKA-2394: move to RollingFileAppender by default for log4j This PR sets up the default max log size to be about 1GB. That default should probably be vetted. You can merge this pull request into

[jira] [Commented] (KAFKA-2394) Use RollingFileAppender by default in log4j.properties

[ https://issues.apache.org/jira/browse/KAFKA-2394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15302098#comment-15302098 ] Dustin Cote commented on KAFKA-2394: [~jinxing6...@126.com] I'll go ahead and take this one to move it

KAFKA-3744: Message format to identify serializer

All, I plan to submit a KIP to begin discussion on https://issues.apache.org/jira/browse/KAFKA-3744 and the associated Pull Request https://github.com/apache/kafka/pull/1419. I'll notify this list when the KIP is submitted. Please discard my previous message containing bogus subject and

KAFKA-3698: Message format to identify serializer

All, I plan to submit a KIP to begin discussion on https://issues.apache.org/jira/browse/KAFKA-3698 and the associated PR https://github.com/apache/kafka/commit/27a19b964af35390d78e1b3b50bc03d23327f4d0. I'll

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

See Changes: [ismael] KAFKA-3718; propagate all KafkaConfig __consumer_offsets configs to -- [...truncated 737 lines...] kafka.api.SaslSslConsumerTest > testPauseStateNotPreservedByRebalance

[jira] [Commented] (KAFKA-3177) Kafka consumer can hang when position() is called on a non-existing partition.

[ https://issues.apache.org/jira/browse/KAFKA-3177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15301940#comment-15301940 ] Edoardo Comar commented on KAFKA-3177: -- see also Consumer.poll() stuck in loop on non-existent topic

[jira] [Commented] (KAFKA-1379) Partition reassignment resets clock for time-based retention

[ https://issues.apache.org/jira/browse/KAFKA-1379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15301936#comment-15301936 ] Moritz Siuts commented on KAFKA-1379: - >From the user-mailinglist: {quote} We’ve recently upgraded to

Build failed in Jenkins: kafka-0.10.0-jdk7 #109

See Changes: [ismael] KAFKA-3718; propagate all KafkaConfig __consumer_offsets configs to -- Started by an SCM change Started by an SCM change Started by an SCM change [EnvInject] - Loading

Build failed in Jenkins: kafka-trunk-jdk7 #1314

See Changes: [ismael] KAFKA-3718; propagate all KafkaConfig __consumer_offsets configs to -- Started by an SCM change Started by an SCM change [EnvInject] - Loading node environment variables.

[GitHub] kafka pull request: delete unused code

GitHub user leisore opened a pull request: https://github.com/apache/kafka/pull/1433 delete unused code You can merge this pull request into a Git repository by running: $ git pull https://github.com/leisore/kafka master Alternatively you can review and apply these changes

[jira] [Commented] (KAFKA-3718) propagate all KafkaConfig __consumer_offsets configs to OffsetConfig instantiation

[ https://issues.apache.org/jira/browse/KAFKA-3718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15301740#comment-15301740 ] ASF GitHub Bot commented on KAFKA-3718: --- Github user asfgit closed the pull request at:

Re: Kafka broker crash - broker id then changed

Possibly tmp got cleaned up? Seems like one of the log files where deleted while a producer was writing messages to it: On Thursday, 26 May 2016, cs user wrote: > Hi All, > > We are running Kafka version 0.9.0.1, at the time the brokers crashed > yesterday we were running

[jira] [Resolved] (KAFKA-3718) propagate all KafkaConfig __consumer_offsets configs to OffsetConfig instantiation

[ https://issues.apache.org/jira/browse/KAFKA-3718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-3718. Resolution: Fixed Reviewer: Ismael Juma > propagate all KafkaConfig __consumer_offsets

[GitHub] kafka pull request: KAFKA-3718: propagate all KafkaConfig __consum...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1394 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Commented] (KAFKA-3511) Add common aggregation functions like Sum and Avg as build-ins in Kafka Streams DSL

[ https://issues.apache.org/jira/browse/KAFKA-3511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15301718#comment-15301718 ] Eno Thereska commented on KAFKA-3511: - >From feedback, it's probably best to hold off from this one

[jira] [Work stopped] (KAFKA-3511) Add common aggregation functions like Sum and Avg as build-ins in Kafka Streams DSL

[ https://issues.apache.org/jira/browse/KAFKA-3511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-3511 stopped by Eno Thereska. --- > Add common aggregation functions like Sum and Avg as build-ins in Kafka >

[jira] [Resolved] (KAFKA-3511) Add common aggregation functions like Sum and Avg as build-ins in Kafka Streams DSL

[ https://issues.apache.org/jira/browse/KAFKA-3511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska resolved KAFKA-3511. - Resolution: Won't Fix > Add common aggregation functions like Sum and Avg as build-ins in Kafka

Kafka broker crash - broker id then changed

Hi All, We are running Kafka version 0.9.0.1, at the time the brokers crashed yesterday we were running in a 2 mode cluster. This has now been increased to 3. We are not specifying a broker id and relying on kafka generating one. After the brokers crashed (at exactly the same time) we left

[jira] [Commented] (KAFKA-3511) Add common aggregation functions like Sum and Avg as build-ins in Kafka Streams DSL

[ https://issues.apache.org/jira/browse/KAFKA-3511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15301710#comment-15301710 ] ASF GitHub Bot commented on KAFKA-3511: --- Github user enothereska closed the pull request at:

[GitHub] kafka pull request: KAFKA-3511: Initial commit for aggregators [Wi...

Github user enothereska closed the pull request at: https://github.com/apache/kafka/pull/1424 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature