[jira] [Work started] (KAFKA-5028) convert kafka controller to a single-threaded event queue model

[ https://issues.apache.org/jira/browse/KAFKA-5028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-5028 started by Onur Karaman. --- > convert kafka controller to a single-threaded event queue model >

[GitHub] kafka pull request #2816: KAFKA-5028: convert kafka controller to a single-t...

GitHub user onurkaraman opened a pull request: https://github.com/apache/kafka/pull/2816 KAFKA-5028: convert kafka controller to a single-threaded event queue model The goal of this ticket is to improve controller maintainability by simplifying the controller's concurrency

[jira] [Commented] (KAFKA-5028) convert kafka controller to a single-threaded event queue model

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

[jira] [Updated] (KAFKA-5028) convert kafka controller to a single-threaded event queue model

[ https://issues.apache.org/jira/browse/KAFKA-5028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Onur Karaman updated KAFKA-5028: Summary: convert kafka controller to a single-threaded event queue model (was: Convert Kafka

[jira] [Created] (KAFKA-5028) Convert Kafka Controller to a single-threaded event queue model

Onur Karaman created KAFKA-5028: --- Summary: Convert Kafka Controller to a single-threaded event queue model Key: KAFKA-5028 URL: https://issues.apache.org/jira/browse/KAFKA-5028 Project: Kafka

[jira] [Created] (KAFKA-5027) Kafka Controller Redesign

Onur Karaman created KAFKA-5027: --- Summary: Kafka Controller Redesign Key: KAFKA-5027 URL: https://issues.apache.org/jira/browse/KAFKA-5027 Project: Kafka Issue Type: Improvement

[jira] [Commented] (KAFKA-5010) Log cleaner crashed with BufferOverflowException when writing to the writeBuffer

[ https://issues.apache.org/jira/browse/KAFKA-5010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15958201#comment-15958201 ] Shuai Lin commented on KAFKA-5010: -- Yeah, from the output of the {{DumpLogSegments}} tool, the topic that

[jira] [Created] (KAFKA-5026) DebuggingConsumerId and DebuggingMessageFormatter and message format v2

Ismael Juma created KAFKA-5026: -- Summary: DebuggingConsumerId and DebuggingMessageFormatter and message format v2 Key: KAFKA-5026 URL: https://issues.apache.org/jira/browse/KAFKA-5026 Project: Kafka

[jira] [Commented] (KAFKA-5010) Log cleaner crashed with BufferOverflowException when writing to the writeBuffer

[ https://issues.apache.org/jira/browse/KAFKA-5010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15958175#comment-15958175 ] Ismael Juma commented on KAFKA-5010: Was compression enabled? > Log cleaner crashed with

[jira] [Created] (KAFKA-5025) FetchRequestTest should use batches with more than one message

Ismael Juma created KAFKA-5025: -- Summary: FetchRequestTest should use batches with more than one message Key: KAFKA-5025 URL: https://issues.apache.org/jira/browse/KAFKA-5025 Project: Kafka

[jira] [Updated] (KAFKA-5010) Log cleaner crashed with BufferOverflowException when writing to the writeBuffer

[ https://issues.apache.org/jira/browse/KAFKA-5010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shuai Lin updated KAFKA-5010: - Description: After upgrading from 0.10.0.1 to 0.10.2.0 the log cleaner thread crashed with

[GitHub] kafka pull request #2814: change language level from java 7 to 8

Github user radai-rosenblatt closed the pull request at: https://github.com/apache/kafka/pull/2814 --- 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

[jira] [Created] (KAFKA-5024) Old clients don't support message format V2

Ismael Juma created KAFKA-5024: -- Summary: Old clients don't support message format V2 Key: KAFKA-5024 URL: https://issues.apache.org/jira/browse/KAFKA-5024 Project: Kafka Issue Type: Sub-task

[jira] [Created] (KAFKA-5023) Remove cyclic dependency between record and protocol packages

Ismael Juma created KAFKA-5023: -- Summary: Remove cyclic dependency between record and protocol packages Key: KAFKA-5023 URL: https://issues.apache.org/jira/browse/KAFKA-5023 Project: Kafka

[jira] [Created] (KAFKA-5022) Improve CRC tests so that we verify which fields are included in the CRC

Ismael Juma created KAFKA-5022: -- Summary: Improve CRC tests so that we verify which fields are included in the CRC Key: KAFKA-5022 URL: https://issues.apache.org/jira/browse/KAFKA-5022 Project: Kafka

[jira] [Created] (KAFKA-5021) Update Message Delivery Semantics section to take into account KIP-98

Ismael Juma created KAFKA-5021: -- Summary: Update Message Delivery Semantics section to take into account KIP-98 Key: KAFKA-5021 URL: https://issues.apache.org/jira/browse/KAFKA-5021 Project: Kafka

[jira] [Created] (KAFKA-5020) Update protocol documentation to mention message format v2

Ismael Juma created KAFKA-5020: -- Summary: Update protocol documentation to mention message format v2 Key: KAFKA-5020 URL: https://issues.apache.org/jira/browse/KAFKA-5020 Project: Kafka Issue

[jira] [Created] (KAFKA-5019) Exactly-once upgrade notes

Ismael Juma created KAFKA-5019: -- Summary: Exactly-once upgrade notes Key: KAFKA-5019 URL: https://issues.apache.org/jira/browse/KAFKA-5019 Project: Kafka Issue Type: Sub-task

[jira] [Commented] (KAFKA-5007) Kafka Replica Fetcher Thread- Resource Leak

[ https://issues.apache.org/jira/browse/KAFKA-5007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15958124#comment-15958124 ] Jun Rao commented on KAFKA-5007: [~joseph.alias...@gmail.com], thanks for reporting this. If the replica

Re: [VOTE] KIP-112 - Handle disk failure for JBOD

+1 Thanks for the KIP. Made a pass and had some minor change. On Mon, Apr 3, 2017 at 3:16 PM, radai wrote: > +1, LGTM > > On Mon, Apr 3, 2017 at 9:49 AM, Dong Lin wrote: > > > Hi all, > > > > It seems that there is no further concern with the

[jira] [Commented] (KAFKA-5010) Log cleaner crashed with BufferOverflowException when writing to the writeBuffer

[ https://issues.apache.org/jira/browse/KAFKA-5010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15958095#comment-15958095 ] Shuai Lin commented on KAFKA-5010: -- For now I can think of a quick fix that may help: to always keep the

[jira] [Commented] (KAFKA-5010) Log cleaner crashed with BufferOverflowException when writing to the writeBuffer

[ https://issues.apache.org/jira/browse/KAFKA-5010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15958091#comment-15958091 ] Shuai Lin commented on KAFKA-5010: -- Hi [~ijuma], I'm not so familiar with kafka internals enough that I'm

[GitHub] kafka pull request #2815: HOTFIX: break infinite loop if Streams input topic...

GitHub user mjsax opened a pull request: https://github.com/apache/kafka/pull/2815 HOTFIX: break infinite loop if Streams input topics are not available You can merge this pull request into a Git repository by running: $ git pull https://github.com/mjsax/kafka

[jira] [Commented] (KAFKA-5007) Kafka Replica Fetcher Thread- Resource Leak

[ https://issues.apache.org/jira/browse/KAFKA-5007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15958049#comment-15958049 ] Joseph Aliase commented on KAFKA-5007: -- [~junrao]Any guidance will be helpfull. > Kafka Replica

[jira] [Created] (KAFKA-5018) LogCleaner tests to verify behaviour of message format v2

Ismael Juma created KAFKA-5018: -- Summary: LogCleaner tests to verify behaviour of message format v2 Key: KAFKA-5018 URL: https://issues.apache.org/jira/browse/KAFKA-5018 Project: Kafka Issue

[jira] [Commented] (KAFKA-4935) Consider disabling record level CRC checks for message format V2

[ https://issues.apache.org/jira/browse/KAFKA-4935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15958033#comment-15958033 ] Ismael Juma commented on KAFKA-4935: Whatever we decide, we should remove the following code comment:

[jira] [Created] (KAFKA-5017) Consider making baseOffset the first offset in message format v2

Ismael Juma created KAFKA-5017: -- Summary: Consider making baseOffset the first offset in message format v2 Key: KAFKA-5017 URL: https://issues.apache.org/jira/browse/KAFKA-5017 Project: Kafka

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

See

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

See Changes: [ismael] KAFKA-4993; Fix findbugs warnings in kafka-clients -- [...truncated 340.48 KB...] kafka.server.KafkaConfigTest > testLogRollTimeMsProvided STARTED

[jira] [Commented] (KAFKA-1211) Hold the produce request with ack > 1 in purgatory until replicas' HW has larger than the produce offset (KIP-101)

[ https://issues.apache.org/jira/browse/KAFKA-1211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15957938#comment-15957938 ] Jun Rao commented on KAFKA-1211: The PR for this issue is https://github.com/apache/kafka/pull/2808 >

[GitHub] kafka pull request #2786: MINOR: Removed dead field

Github user original-brownbear closed the pull request at: https://github.com/apache/kafka/pull/2786 --- 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

[jira] [Updated] (KAFKA-4819) Expose states of active tasks to public API

[ https://issues.apache.org/jira/browse/KAFKA-4819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-4819: --- Description:

[jira] [Updated] (KAFKA-4819) Expose states of active tasks to public API

[ https://issues.apache.org/jira/browse/KAFKA-4819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-4819: --- Labels: kip (was: needs-kip) > Expose states of active tasks to public API >

[jira] [Resolved] (KAFKA-4993) Fix findbugs warnings in kafka-clients

[ https://issues.apache.org/jira/browse/KAFKA-4993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-4993. Resolution: Fixed Fix Version/s: 0.11.0.0 > Fix findbugs warnings in kafka-clients >

[jira] [Commented] (KAFKA-4993) Fix findbugs warnings in kafka-clients

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

[GitHub] kafka pull request #2779: KAFKA-4993: Fix findbugs warnings in kafka-clients

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2779 --- 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: [DISCUSS] KIP-131 : Add access to OffsetStorageReader from SourceConnector

Hi All, Is there any feedback regarding that KIP ? https://cwiki.apache.org/confluence/display/KAFKA/KIP-131+-+Add+access+to+OffsetStorageReader+from+SourceConnector Thanks, 2017-03-14 22:51 GMT+01:00 Florian Hussonnois : > Hi Matthias, > > Sorry I didn't know this page.

[VOTE] KIP 130: Expose states of active tasks to KafkaStreams public API

Hi All, I would like to start the vote for the KIP-130 : https://cwiki.apache.org/confluence/display/KAFKA/KIP+130%3A+Expose+states+of+active+tasks+to+KafkaStreams+public+API Thanks, -- Florian HUSSONNOIS

Re: [VOTE] KIP-122: Add Reset Consumer Group Offsets tooling

Thanks to everyone who voted and/or provided feedback! The vote passed with 4 binding +1s (Gwen, Grant, Jason, Becket) and 5 non-binding +1s (Matthias, Vahid, Bill, Dong, Mickael). El mié., 5 abr. 2017 a las 11:58, Jorge Esteban Quilcate Otoya (< quilcate.jo...@gmail.com>) escribió: > Thanks

[jira] [Resolved] (KAFKA-3455) Connect custom processors with the streams DSL

[ https://issues.apache.org/jira/browse/KAFKA-3455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax resolved KAFKA-3455. Resolution: Not A Problem > Connect custom processors with the streams DSL >

[GitHub] kafka pull request #2776: HOTFIX: WindowedStreamPartitioner does not provide...

Github user mjsax closed the pull request at: https://github.com/apache/kafka/pull/2776 --- 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-5007) Kafka Replica Fetcher Thread- Resource Leak

[ https://issues.apache.org/jira/browse/KAFKA-5007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15957413#comment-15957413 ] Joseph Aliase commented on KAFKA-5007: -- [~gwenshap] Please take a look at this its a major bug >

[jira] [Resolved] (KAFKA-4801) Transient test failure (part 2): ConsumerBounceTest.testConsumptionWithBrokerFailures

[ https://issues.apache.org/jira/browse/KAFKA-4801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Armin Braun resolved KAFKA-4801. Resolution: Fixed Can't reproduce this anymore and could easily do so before. Also haven't seen

Re: [VOTE] KIP-135 : Send of null key to a compacted topic should throw non-retriable error back to user

Bumping up this thread. On Mon, Apr 3, 2017 at 4:22 PM, Mayuresh Gharat wrote: > Hi All, > > It seems that there is no further concern with the KIP-135. At this point > we would like to start the voting process. The KIP can be found at >

Re: [VOTE] KIP-120: Cleanup Kafka Streams builder API

+1 On Tue, Apr 4, 2017 at 9:01 PM, Ewen Cheslack-Postava wrote: > +1 (binding) > > -Ewen > > On Thu, Mar 30, 2017 at 4:03 PM, Guozhang Wang wrote: > > > +1. > > > > > > On Thu, Mar 30, 2017 at 1:18 AM, Damian Guy > wrote: > > > > >

Re: [VOTE] KIP-81: Bound Fetch memory usage in the consumer

Thanks to everybody who voted and reviewed the KIP ! The vote passed with 5 binding +1s (Jason, Guozhang, Jun, Ismael, Becket) and 3 non-binding +1s (Edoardo, Rajini, Radai) On Mon, Apr 3, 2017 at 5:59 PM, Becket Qin wrote: > +1. Thanks for the KIP. > > On Mon, Apr 3,

[jira] [Commented] (KAFKA-4943) SCRAM secret's should be better protected with Zookeeper ACLs

[ https://issues.apache.org/jira/browse/KAFKA-4943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15956945#comment-15956945 ] Johan Ström commented on KAFKA-4943: Another possibly bad thing is that Kafka logs the credentials in

[jira] [Commented] (KAFKA-3455) Connect custom processors with the streams DSL

[ https://issues.apache.org/jira/browse/KAFKA-3455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15956941#comment-15956941 ] Nikki Thean commented on KAFKA-3455: Correct. > Connect custom processors with the streams DSL >

[GitHub] kafka pull request #2814: change language level from java 7 to 8

GitHub user radai-rosenblatt opened a pull request: https://github.com/apache/kafka/pull/2814 change language level from java 7 to 8 now that KIP-118 has passed, and there are no major releases coming before 0.11 Signed-off-by: radai-rosenblatt

[jira] [Commented] (KAFKA-5016) Consumer hang in poll method while rebalancing is in progress

[ https://issues.apache.org/jira/browse/KAFKA-5016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15956928#comment-15956928 ] Ismael Juma commented on KAFKA-5016: Thanks for the bug report. [~vahid], would you be interested in

[jira] [Created] (KAFKA-5016) Consumer hang in poll method while rebalancing is in progress

Domenico Di Giulio created KAFKA-5016: - Summary: Consumer hang in poll method while rebalancing is in progress Key: KAFKA-5016 URL: https://issues.apache.org/jira/browse/KAFKA-5016 Project: Kafka

[jira] [Commented] (KAFKA-5014) SSL Channel not ready but tcp is established and the server is hung will not sending metadata

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

[jira] [Updated] (KAFKA-5014) SSL Channel not ready but tcp is established and the server is hung will not sending metadata

[ https://issues.apache.org/jira/browse/KAFKA-5014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5014: --- Fix Version/s: 0.11.0.0 > SSL Channel not ready but tcp is established and the server is hung will

[jira] [Commented] (KAFKA-5014) SSL Channel not ready but tcp is established and the server is hung will not sending metadata

[ https://issues.apache.org/jira/browse/KAFKA-5014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15956917#comment-15956917 ] Ismael Juma commented on KAFKA-5014: Thanks for the bug report. Is the fix simply

[GitHub] kafka pull request #2813: KAFKA-5014: NetworkClient.leastLoadedNode should c...

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/2813 KAFKA-5014: NetworkClient.leastLoadedNode should check if channel is ready You can merge this pull request into a Git repository by running: $ git pull https://github.com/ijuma/kafka

[jira] [Created] (KAFKA-5015) SASL/SCRAM authentication failures are hidden

Johan Ström created KAFKA-5015: -- Summary: SASL/SCRAM authentication failures are hidden Key: KAFKA-5015 URL: https://issues.apache.org/jira/browse/KAFKA-5015 Project: Kafka Issue Type:

[jira] [Created] (KAFKA-5014) SSL Channel not ready but tcp is established and the server is hung will not sending metadata

Pengwei created KAFKA-5014: -- Summary: SSL Channel not ready but tcp is established and the server is hung will not sending metadata Key: KAFKA-5014 URL: https://issues.apache.org/jira/browse/KAFKA-5014

[jira] [Commented] (KAFKA-4814) ZookeeperLeaderElector not respecting zookeeper.set.acl

[ https://issues.apache.org/jira/browse/KAFKA-4814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15956846#comment-15956846 ] Ismael Juma commented on KAFKA-4814: [~baluchicken], have you made progress on this one? If not, maybe

[GitHub] kafka pull request #2812: Improve topic management instructions for Kafka St...

GitHub user miguno opened a pull request: https://github.com/apache/kafka/pull/2812 Improve topic management instructions for Kafka Streams examples You can merge this pull request into a Git repository by running: $ git pull https://github.com/miguno/kafka

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

See Changes: [ismael] MINOR: Fix flaky StateDirectoryTest [ismael] MINOR: Make ConfigDef safer by not using empty string for [ismael] MINOR: Fix multiple KafkaStreams.StreamStateListener being instantiated

Re: [DISCUSS] KIP-138: Change punctuate semantics

Hi Jay, The hybrid solution is exactly what I expect and need for our use cases when dealing with telecom data. Thanks Tianji On Wed, Apr 5, 2017 at 12:01 AM, Jay Kreps wrote: > Hey guys, > > One thing I've always found super important for this kind of design work is > to

Jenkins build is back to normal : kafka-0.10.2-jdk7 #121

See

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

See

[jira] [Updated] (KAFKA-4913) creating a window store with one segment throws division by zero error

[ https://issues.apache.org/jira/browse/KAFKA-4913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy updated KAFKA-4913: -- Priority: Major (was: Blocker) > creating a window store with one segment throws division by zero

[jira] [Updated] (KAFKA-4913) creating a window store with one segment throws division by zero error

[ https://issues.apache.org/jira/browse/KAFKA-4913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy updated KAFKA-4913: -- Fix Version/s: (was: 0.10.2.1) 0.11.0.0 > creating a window store with one

[GitHub] kafka pull request #2811: MINOR: update javadoc on ReadOnlyWindowStore

GitHub user dguy opened a pull request: https://github.com/apache/kafka/pull/2811 MINOR: update javadoc on ReadOnlyWindowStore Highlight that the range in `fetch` is inclusive of both `timeFrom` and `timeTo` You can merge this pull request into a Git repository by running: $

[GitHub] kafka pull request #2801: MINOR: Fix multiple org.apache.kafka.streams.Kafka...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2801 --- 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 #2660: MINOR: Make ConfigDef safer by not using empty str...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2660 --- 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] [Updated] (KAFKA-4935) Consider disabling record level CRC checks for message format V2

[ https://issues.apache.org/jira/browse/KAFKA-4935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4935: --- Description: With the new message format proposed in KIP-98, the record level CRC has been moved to

[jira] [Updated] (KAFKA-4935) Consider disabling record level CRC checks for message format V2

[ https://issues.apache.org/jira/browse/KAFKA-4935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4935: --- Issue Type: Sub-task (was: Improvement) Parent: KAFKA-4815 > Consider disabling record level

[jira] [Updated] (KAFKA-4935) Consider disabling record level CRC checks for message format V2

[ https://issues.apache.org/jira/browse/KAFKA-4935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4935: --- Summary: Consider disabling record level CRC checks for message format V2 (was: Disable record level

[jira] [Updated] (KAFKA-4935) Disable record level crc checks on the consumer with the KIP-98 message format

[ https://issues.apache.org/jira/browse/KAFKA-4935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4935: --- Fix Version/s: 0.11.0.0 > Disable record level crc checks on the consumer with the KIP-98 message

Re: [VOTE] KIP-122: Add Reset Consumer Group Offsets tooling

Thanks Ismael! Response inline. El mar., 4 abr. 2017 a las 17:43, Ismael Juma () escribió: Sorry for the delay Jorge. Responses inline. On Thu, Mar 23, 2017 at 5:56 PM, Jorge Esteban Quilcate Otoya < quilcate.jo...@gmail.com> wrote: > @Ismael, thanks for your feedback! > 1.

[GitHub] kafka pull request #2781: MINOR: fix flaky StateDirectoryTest

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2781 --- 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 #2777: HOTFIX: WindowedStreamPartitioner does not provide...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2777 --- 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 #2810: KAFKA-4901: Make ProduceRequest thread-safe

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/2810 KAFKA-4901: Make ProduceRequest thread-safe A more conservative version of the change for the 0.10.2 branch. Trunk commit: 1659ca1773596b. You can merge this pull request into a Git

[jira] [Commented] (KAFKA-4901) Make ProduceRequest thread-safe

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

[jira] [Commented] (KAFKA-4107) Support offset reset capability in Kafka Connect

[ https://issues.apache.org/jira/browse/KAFKA-4107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15956446#comment-15956446 ] Sönke Liebau commented on KAFKA-4107: - Is anybody actively working on this? If not I'd be willing to

[jira] [Work started] (KAFKA-4831) Extract WindowedSerde to public APIs

[ https://issues.apache.org/jira/browse/KAFKA-4831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-4831 started by Vitaly Pushkar. - > Extract WindowedSerde to public APIs >

[jira] [Assigned] (KAFKA-4831) Extract WindowedSerde to public APIs

[ https://issues.apache.org/jira/browse/KAFKA-4831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Pushkar reassigned KAFKA-4831: - Assignee: Vitaly Pushkar > Extract WindowedSerde to public APIs >

[GitHub] kafka pull request #2809: CPKAFKA-465 : Exactly once transactional producer ...

GitHub user apurvam opened a pull request: https://github.com/apache/kafka/pull/2809 CPKAFKA-465 : Exactly once transactional producer -- initial implementation The basic flow works: find coordinator, get pid, add partitions to transaction, commit/abort. Still to add:

[GitHub] kafka pull request #2809: CPKAFKA-465 : Exactly once transactional producer ...

Github user apurvam closed the pull request at: https://github.com/apache/kafka/pull/2809 --- 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