[jira] [Resolved] (KAFKA-4953) Global Store: cast exception when initialising with in-memory logged state store

[ https://issues.apache.org/jira/browse/KAFKA-4953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy resolved KAFKA-4953. --- Resolution: Fixed fixed by KAFKA-5045 > Global Store: cast exception when initialis

[jira] [Resolved] (KAFKA-4270) ClassCast for Agregation

[ https://issues.apache.org/jira/browse/KAFKA-4270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy resolved KAFKA-4270. --- Resolution: Cannot Reproduce Closing this as haven't been able to reproduce and no further

Re: [DISCUSS]: KIP-161: streams record processing exception handlers

d punt the > storage one to later. > > Eno > > > On 26 May 2017, at 16:59, Damian Guy <damian@gmail.com> wrote: > > > > Eno, > > > > Under what circumstances would you get a deserialization exception from > the > > state store? I can

Re: [DISCUSS]: KIP-161: streams record processing exception handlers

Eno, Under what circumstances would you get a deserialization exception from the state store? I can only think of the case where someone has provided a bad deserializer to a method that creates a state store. In which case it would be a user error and probably should just abort? Thanks, Damian

Re: KIP-162: Enable topic deletion by default

+1 Also agree with what Ismael said. On Fri, 26 May 2017 at 15:26 Ismael Juma wrote: > Thanks for the KIP, sounds good to me. One comment: not sure we need to add > the config to server.properties. Do we expect people to change this > default? > > On Fri, May 26, 2017 at 3:03

[jira] [Updated] (KAFKA-5308) TC should handle UNSUPPORTED_FOR_MESSAGE_FORMAT in WriteTxnMarker response

[ https://issues.apache.org/jira/browse/KAFKA-5308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy updated KAFKA-5308: -- Status: Patch Available (was: Open) > TC should handle UNSUPPORTED_FOR_MESSAGE_FOR

Re: GlobalKTable limitations

We did originally think of allowing `filter`, `map` etc on a GlobalKTable, though it would have been slightly different to what you are suggesting, i.e., we'd materialize the topic as a Store and then provide views on top of that. They'd also be global, but not materialized as physical state

Re: [Vote] KIP-150 - Kafka-Streams Cogroup

Also, +1 for the KIP On Wed, 24 May 2017 at 08:57 Damian Guy <damian@gmail.com> wrote: > +1 to what Xavier said > > On Wed, 24 May 2017 at 06:45 Xavier Léauté <xav...@confluent.io> wrote: > >> I don't think we should wait for entries from each stream

Re: [Vote] KIP-150 - Kafka-Streams Cogroup

+1 to what Xavier said On Wed, 24 May 2017 at 06:45 Xavier Léauté wrote: > I don't think we should wait for entries from each stream, since that might > limit the usefulness of the cogroup operator. There are instances where it > can be useful to compute something based on

[jira] [Commented] (KAFKA-5308) TC should handle UNSUPPORTED_FOR_MESSAGE_FORMAT in WriteTxnMarker response

[ https://issues.apache.org/jira/browse/KAFKA-5308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16021295#comment-16021295 ] Damian Guy commented on KAFKA-5308: --- [~hachikuji] i think this may not be possible once https

[jira] [Assigned] (KAFKA-5308) TC should handle UNSUPPORTED_FOR_MESSAGE_FORMAT in WriteTxnMarker response

[ https://issues.apache.org/jira/browse/KAFKA-5308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy reassigned KAFKA-5308: - Assignee: Damian Guy > TC should handle UNSUPPORTED_FOR_MESSAGE_FORMAT in WriteTxnMar

[jira] [Updated] (KAFKA-5260) Producer should not send AbortTxn unless transaction has actually begun

[ https://issues.apache.org/jira/browse/KAFKA-5260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy updated KAFKA-5260: -- Status: Patch Available (was: Open) > Producer should not send AbortTxn unless transaction

[jira] [Updated] (KAFKA-5279) TransactionCoordinator must expire transactionalIds

[ https://issues.apache.org/jira/browse/KAFKA-5279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy updated KAFKA-5279: -- Status: Patch Available (was: Open) > TransactionCoordinator must expire transactional

[jira] [Assigned] (KAFKA-5154) Kafka Streams throws NPE during rebalance

[ https://issues.apache.org/jira/browse/KAFKA-5154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy reassigned KAFKA-5154: - Assignee: Damian Guy (was: Matthias J. Sax) > Kafka Streams throws NPE during rebala

Re: [DISCUSS]: KIP-149: Enabling key access in ValueTransformer, ValueMapper, and ValueJoiner

gt; > >>> Instead of overriding the *init(ProcessorContext p)* and* close()* > > >> methods > > >>> in every Rich function with empty body like: > > >>> > > >>> @Override > > >>> void init(ProcessorConte

[jira] [Created] (KAFKA-5288) Failure in org.apache.kafka.streams.integration.ResetIntegrationTest.testReprocessingFromScratchAfterResetWithoutIntermediateUserTopic

Damian Guy created KAFKA-5288: - Summary: Failure in org.apache.kafka.streams.integration.ResetIntegrationTest.testReprocessingFromScratchAfterResetWithoutIntermediateUserTopic Key: KAFKA-5288 URL: https

[jira] [Reopened] (KAFKA-5063) Flaky ResetIntegrationTest.testReprocessingFromScratchAfterResetWithIntermediateUserTopic

[ https://issues.apache.org/jira/browse/KAFKA-5063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy reopened KAFKA-5063: --- > Flaky > ResetIntegrationTest.testReprocessingFromScratchAfterResetWithIntermediateUse

[jira] [Commented] (KAFKA-5063) Flaky ResetIntegrationTest.testReprocessingFromScratchAfterResetWithIntermediateUserTopic

[ https://issues.apache.org/jira/browse/KAFKA-5063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16017058#comment-16017058 ] Damian Guy commented on KAFKA-5063: --- Another instance of this failure: {noformat

[jira] [Commented] (KAFKA-5256) Non-checkpointed state stores should be deleted before restore

[ https://issues.apache.org/jira/browse/KAFKA-5256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16015805#comment-16015805 ] Damian Guy commented on KAFKA-5256: --- >From 0.11.0 onwards we will always have a checkpoint unl

[jira] [Commented] (KAFKA-5154) Kafka Streams throws NPE during rebalance

[ https://issues.apache.org/jira/browse/KAFKA-5154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16015615#comment-16015615 ] Damian Guy commented on KAFKA-5154: --- [~Lukas Gemela] Thanks for attaching the full logs. [~mjsax

[jira] [Updated] (KAFKA-5154) Kafka Streams throws NPE during rebalance

[ https://issues.apache.org/jira/browse/KAFKA-5154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy updated KAFKA-5154: -- Attachment: 5154_problem.log > Kafka Streams throws NPE during rebala

Re: Reg: [VOTE] KIP 157 - Add consumer config options to streams reset tool

+1 On Wed, 17 May 2017 at 05:40 Ewen Cheslack-Postava wrote: > +1 (binding) > > I mentioned this in the PR that triggered this: > > > KIP is accurate, though this is one of those things that we should > probably get a KIP for a standard set of config options across all tools

Re: [DISCUSS] KIP-150 - Kafka-Streams Cogroup

m? I just think that because it > is created from a KGroupedStream we should keep a similar name format. > > On May 16, 2017 9:23 AM, "Damian Guy" <damian@gmail.com> wrote: > > Hi Kyle, > > Can you put the code examples etc in {code} blocks to make it easier to

Re: [DISCUSS] KIP-150 - Kafka-Streams Cogroup

morrow is feature freeze deadline ( > > https://cwiki.apache.org/confluence/display/KAFKA/Release+Plan+0.11.0.0 > < > > https://cwiki.apache.org/confluence/display/KAFKA/Release+Plan+0.11.0.0 > >) > > so people are busier than usual. Stay tuned. > > > > Eno > >

[jira] [Commented] (KAFKA-5241) GlobalKTable does not checkpoint offsets after restoring state

[ https://issues.apache.org/jira/browse/KAFKA-5241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16012270#comment-16012270 ] Damian Guy commented on KAFKA-5241: --- [~twbecker] Probably worth filing another JIRA

Re: [DISCUSS]: KIP-149: Enabling key access in ValueTransformer, ValueMapper, and ValueJoiner

wondering, if you question the `RichFunction` approach in > general? Or if you suggest to either extend the scope of this KIP to > include this---or maybe better, do another KIP for it and delay this KIP > until the other one is done? > > > -Matthias > > On 5/15/17 2:35 AM, Da

Re: [DISCUSS]: KIP-149: Enabling key access in ValueTransformer, ValueMapper, and ValueJoiner

Thanks for the KIP. I'm not convinced on the `RichFunction` approach. Do we really want to give every DSL method access to the `ProcessorContext` ? It has a bunch of methods on it that seem in-appropriate for some of the DSL methods, i.e, `register`, `getStateStore`, `forward`, `schedule` etc. It

[jira] [Created] (KAFKA-5219) Move transaction expiration logic and scheduling to the Transaction Manager

Damian Guy created KAFKA-5219: - Summary: Move transaction expiration logic and scheduling to the Transaction Manager Key: KAFKA-5219 URL: https://issues.apache.org/jira/browse/KAFKA-5219 Project: Kafka

[jira] [Assigned] (KAFKA-5129) TransactionCoordinator - Add ACL check for each request

[ https://issues.apache.org/jira/browse/KAFKA-5129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy reassigned KAFKA-5129: - Assignee: Damian Guy > TransactionCoordinator - Add ACL check for each requ

[jira] [Updated] (KAFKA-5168) Cleanup delayed produce purgatory during partition emmigration

[ https://issues.apache.org/jira/browse/KAFKA-5168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy updated KAFKA-5168: -- Resolution: Not A Problem Status: Resolved (was: Patch Available) This is already handled

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

Thanks Michael - LGTM On Fri, 5 May 2017 at 12:04 Michal Borowiecki wrote: > I shall move all alternatives other than the main proposal into the > Rejected Alternatives section and if I hear any objections, I'll move those > back up and we'll discuss further. > >

Re: [DISCUSS] KIP-150 - Kafka-Streams Cogroup

> > repartitions an error is thrown. Is there some name that someone can > > > recommend or should I leave the null and allow it to fall back to the > > > KGroupedStream.name? > > > > > > Should this be expanded to handle grouped tables? This would be pr

Re: [DISCUSS] KIP-150 - Kafka-Streams Cogroup

Hi Kyle, Thanks for the KIP. I apologize that i haven't had the chance to look at the KIP yet, but will schedule some time to look into it tomorrow. For the implementation, can you raise a PR against kafka trunk and mark it as WIP? It will be easier to review what you have done. Thanks, Damian

[jira] [Updated] (KAFKA-5168) Cleanup delayed produce purgatory during partition emmigration

[ https://issues.apache.org/jira/browse/KAFKA-5168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy updated KAFKA-5168: -- Status: Patch Available (was: Open) > Cleanup delayed produce purgatory during partition emmigrat

[jira] [Updated] (KAFKA-5059) Implement Transactional Coordinator

[ https://issues.apache.org/jira/browse/KAFKA-5059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy updated KAFKA-5059: -- Fix Version/s: 0.11.0.0 > Implement Transactional Coordina

[jira] [Created] (KAFKA-5168) Cleanup delayed produce purgatory during partition emmigration

Damian Guy created KAFKA-5168: - Summary: Cleanup delayed produce purgatory during partition emmigration Key: KAFKA-5168 URL: https://issues.apache.org/jira/browse/KAFKA-5168 Project: Kafka

[jira] [Updated] (KAFKA-5131) WriteTxnMarkers and complete commit/abort on partition immigration

[ https://issues.apache.org/jira/browse/KAFKA-5131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy updated KAFKA-5131: -- Status: Patch Available (was: Open) > WriteTxnMarkers and complete commit/abort on partit

[jira] [Updated] (KAFKA-5132) Abort long running transactions

[ https://issues.apache.org/jira/browse/KAFKA-5132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy updated KAFKA-5132: -- Status: Patch Available (was: Open) > Abort long running transacti

[jira] [Assigned] (KAFKA-5131) WriteTxnMarkers and complete commit/abort on partition immigration

[ https://issues.apache.org/jira/browse/KAFKA-5131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy reassigned KAFKA-5131: - Assignee: Damian Guy > WriteTxnMarkers and complete commit/abort on partition immigrat

[jira] [Work started] (KAFKA-5136) Move coordinatorEpoch from WriteTxnMarkerRequest to TxnMarkerEntry

[ https://issues.apache.org/jira/browse/KAFKA-5136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-5136 started by Damian Guy. - > Move coordinatorEpoch from WriteTxnMarkerRequest to TxnMarkerEn

[jira] [Created] (KAFKA-5136) Move coordinatorEpoch from WriteTxnMarkerRequest to TxnMarkerEntry

Damian Guy created KAFKA-5136: - Summary: Move coordinatorEpoch from WriteTxnMarkerRequest to TxnMarkerEntry Key: KAFKA-5136 URL: https://issues.apache.org/jira/browse/KAFKA-5136 Project: Kafka

Re: Re: Time synchronization between streams

mall > in > > window will change from V1 to V2, before Kafka Streams will receive VT1. > > > > I.e. state stores actions of Kafka Streams will be like this: > > > > join_left_side_store.put ( K1-W1, V1 ) > > join_left_side_store.put ( K1-W1, V2 ) > > join_rig

[jira] [Assigned] (KAFKA-5132) Abort long running transactions

[ https://issues.apache.org/jira/browse/KAFKA-5132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy reassigned KAFKA-5132: - Assignee: Damian Guy > Abort long running transacti

[jira] [Commented] (KAFKA-5132) Abort long running transactions

[ https://issues.apache.org/jira/browse/KAFKA-5132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15986183#comment-15986183 ] Damian Guy commented on KAFKA-5132: --- Hi [~umesh9...@gmail.com] thanks for offering to help. In this case

[jira] [Created] (KAFKA-5132) Abort long running transactions

Damian Guy created KAFKA-5132: - Summary: Abort long running transactions Key: KAFKA-5132 URL: https://issues.apache.org/jira/browse/KAFKA-5132 Project: Kafka Issue Type: Sub-task

[jira] [Created] (KAFKA-5131) WriteTxnMarkers and complete commit/abort on partition immigration

Damian Guy created KAFKA-5131: - Summary: WriteTxnMarkers and complete commit/abort on partition immigration Key: KAFKA-5131 URL: https://issues.apache.org/jira/browse/KAFKA-5131 Project: Kafka

[jira] [Updated] (KAFKA-5129) TransactionCoordinator - Add ACL check for each request

[ https://issues.apache.org/jira/browse/KAFKA-5129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy updated KAFKA-5129: -- Issue Type: Sub-task (was: Bug) Parent: KAFKA-5059 > TransactionCoordinator - Add ACL ch

[jira] [Created] (KAFKA-5130) Change InterBrokerSendThread to use a Queue per broker

Damian Guy created KAFKA-5130: - Summary: Change InterBrokerSendThread to use a Queue per broker Key: KAFKA-5130 URL: https://issues.apache.org/jira/browse/KAFKA-5130 Project: Kafka Issue Type

[jira] [Updated] (KAFKA-5128) TransactionCoordinator - Check inter broker protocol and message format and raise errors if incompatible

[ https://issues.apache.org/jira/browse/KAFKA-5128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy updated KAFKA-5128: -- Issue Type: Sub-task (was: Bug) Parent: KAFKA-5059 > TransactionCoordinator - Check in

[jira] [Created] (KAFKA-5129) TransactionCoordinator - Add ACL check for each request

Damian Guy created KAFKA-5129: - Summary: TransactionCoordinator - Add ACL check for each request Key: KAFKA-5129 URL: https://issues.apache.org/jira/browse/KAFKA-5129 Project: Kafka Issue Type

[jira] [Created] (KAFKA-5128) TransactionCoordinator - Check inter broker protocol and message format and raise errors if incompatible

Damian Guy created KAFKA-5128: - Summary: TransactionCoordinator - Check inter broker protocol and message format and raise errors if incompatible Key: KAFKA-5128 URL: https://issues.apache.org/jira/browse/KAFKA-5128

Re: [ANNOUNCE] New committer: Rajini Sivaram

Congrats On Tue, 25 Apr 2017 at 09:57, Mickael Maison wrote: > Congratulation Rajini ! > Great news > > On Tue, Apr 25, 2017 at 8:54 AM, Edoardo Comar wrote: > > Congratulations Rajini !!! > > Well deserved > >

[jira] [Commented] (KAFKA-4593) Task migration during rebalance callback process could lead the obsoleted task's IllegalStateException

[ https://issues.apache.org/jira/browse/KAFKA-4593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15982470#comment-15982470 ] Damian Guy commented on KAFKA-4593: --- Is this even possible? I.e, thread A would have the lock

Re: [VOTE] KIP-114: KTable state stores and improved semantics

+1 On Fri, 21 Apr 2017 at 19:21 Sriram Subramanian wrote: > +1 > > On Fri, Apr 21, 2017 at 11:06 AM, Guozhang Wang > wrote: > > > +1 > > > > On Fri, Apr 21, 2017 at 10:52 AM, Bill Bejeck wrote: > > > > > +1 > > > On Fri, Apr 21, 2017

[jira] [Created] (KAFKA-5113) Tidy up usage of Errors.INVALID_FETCH_SIZE and InvalidFetchSizeException

Damian Guy created KAFKA-5113: - Summary: Tidy up usage of Errors.INVALID_FETCH_SIZE and InvalidFetchSizeException Key: KAFKA-5113 URL: https://issues.apache.org/jira/browse/KAFKA-5113 Project: Kafka

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

+1 On Fri, 21 Apr 2017 at 09:06 Eno Thereska wrote: > +1 (non-binding) > > Thanks > Eno > > > On 21 Apr 2017, at 05:58, Guozhang Wang wrote: > > > > +1. Thanks a lot for the KIP! > > > > Guozhang > > > > On Wed, Apr 5, 2017 at 1:57 PM, Florian

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

is way it's consistent between Processor and Transformer. > > > BTW, looking at this I found a glitch in the javadoc and put a comment > there: > > https://github.com/apache/kafka/pull/2413/files#r112634612 > > and PR: https://github.com/apache/kafka/pull/2884 > > Cheers, >

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

Hi Michal, Thanks for the KIP. I'd like to propose a bit more of a radical change to the API. 1. deprecate the punctuate method on Processor 2. create a new Functional Interface just for Punctuation, something like: interface Punctuator { void punctuate(long timestamp) } 3. add a new schedule

Re: [DISCUSS] KIP 141 - ProducerRecordBuilder Interface

Hi Stephane, Thanks for the KIP. Overall it looks ok, though i think the builder should enforce the required parameters by supplying them via the constructor, i.e, public ProducerRecordBuilder(String topic, V value) You can then remove the withValue and withTopic methods I also think

[jira] [Created] (KAFKA-5095) ThreadCacheTest.cacheOverheadsSmallValues fails intermittently

Damian Guy created KAFKA-5095: - Summary: ThreadCacheTest.cacheOverheadsSmallValues fails intermittently Key: KAFKA-5095 URL: https://issues.apache.org/jira/browse/KAFKA-5095 Project: Kafka

[jira] [Updated] (KAFKA-5059) Implement Transactional Coordinator

[ https://issues.apache.org/jira/browse/KAFKA-5059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy updated KAFKA-5059: -- Description: This covers the implementation of the transaction coordinator to support transactions

[jira] [Created] (KAFKA-5059) Implement Transactional Coordinator

Damian Guy created KAFKA-5059: - Summary: Implement Transactional Coordinator Key: KAFKA-5059 URL: https://issues.apache.org/jira/browse/KAFKA-5059 Project: Kafka Issue Type: New Feature

[jira] [Created] (KAFKA-5058) Add a sensor to KafkaStreams to track records that have been dropped due to having a null key

Damian Guy created KAFKA-5058: - Summary: Add a sensor to KafkaStreams to track records that have been dropped due to having a null key Key: KAFKA-5058 URL: https://issues.apache.org/jira/browse/KAFKA-5058

Re: [DISCUSS] KIP-114: KTable materialization and improved semantics

d clarify what we'd do in such a > >> case. For example, if the user did not specify a store name for > >> `KTable#filter` -- would it be queryable? If so, would this imply we'd > >> always materialize the state store, or...? > > > > I'll clarify in the KI

[jira] [Assigned] (KAFKA-5054) ChangeLoggingKeyValueByteStore delete and putIfAbsent should be synchronized

[ https://issues.apache.org/jira/browse/KAFKA-5054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy reassigned KAFKA-5054: - Assignee: Damian Guy > ChangeLoggingKeyValueByteStore delete and putIfAbsent sho

[jira] [Created] (KAFKA-5054) ChangeLoggingKeyValueByteStore delete and putIfAbsent should be synchronized

Damian Guy created KAFKA-5054: - Summary: ChangeLoggingKeyValueByteStore delete and putIfAbsent should be synchronized Key: KAFKA-5054 URL: https://issues.apache.org/jira/browse/KAFKA-5054 Project: Kafka

Re: [VOTE] KIP-134: Delay initial consumer group rebalance

t; > On Thu, Apr 6, 2017 at 2:51 AM, Damian Guy <damian@gmail.com> wrote: > > > Thanks all, the Vote is now closed and the KIP has been accepted with 9 > +1s > > > > 3 binding:: > > Guozhang, > > Jason, > > Ismael > > > > 6

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

; you mentioned > >> > currently > >> > > > we > >> > > > > only expose the state of the process but not the > >> finer grained > >> > > per-t

Re: [DISCUSS] KIP-114: KTable materialization and improved semantics

> >>>>>>>>> behind the scene, to e.g. Damian suggested "queryableStore(String > >>>>>>>>> storeName)", > >>>>>>>>> which returns a QueryableStateStore, and can replace

[jira] [Updated] (KAFKA-5047) NullPointerException while using GlobalKTable in KafkaStreams

[ https://issues.apache.org/jira/browse/KAFKA-5047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy updated KAFKA-5047: -- Status: Patch Available (was: Open) > NullPointerException while using GlobalKTable in KafkaStre

[jira] [Assigned] (KAFKA-5047) NullPointerException while using GlobalKTable in KafkaStreams

[ https://issues.apache.org/jira/browse/KAFKA-5047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy reassigned KAFKA-5047: - Assignee: Damian Guy > NullPointerException while using GlobalKTable in KafkaStre

Re: [VOTE] KIP-134: Delay initial consumer group rebalance

...@gmail.com> > > wrote: > > > > > > > >> +1(non-binding) > > > >> > > > >> On Thu, Mar 30, 2017 at 1:30 PM, Eno Thereska < > eno.there...@gmail.com > > > > > > >> wrote: > > > >&

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

[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

Re: [VOTE] KIP-134: Delay initial consumer group rebalance

lly skip past it due to a > > potential misunderstanding. > > > > On Mon, Apr 3, 2017 at 8:10 AM, Bill Bejeck <bbej...@gmail.com> wrote: > > > > > +1 (non-binding) > > > > > > On Mon, Apr 3, 2017 at 9:53 AM, Mathieu Fenniak < > > >

Re: [VOTE] KIP-134: Delay initial consumer group rebalance

gt; Damian, could you create a new thread for the voting process? > > > > > > > > > > > > Thanks! > > > > > > > > > > > > Guozhang > > > > > > > > > > > > On Thu, Mar 30, 2017 at 10:33 AM, Bill Bejeck <bbej...

Re: [VOTE] KIP-134: Delay initial consumer group rebalance

gmail.com> wrote: > > > +1(non-binding) > > > > On Thu, Mar 30, 2017 at 1:30 PM, Eno Thereska <eno.there...@gmail.com> > > wrote: > > > > > +1 (non binding) > > > > > > Thanks > > > Eno > > > > On 30 Mar 2017, at

[jira] [Assigned] (KAFKA-4937) Batch resetting offsets in Streams' StoreChangelogReader

[ https://issues.apache.org/jira/browse/KAFKA-4937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy reassigned KAFKA-4937: - Assignee: Damian Guy > Batch resetting offsets in Streams' StoreChangelogRea

[jira] [Updated] (KAFKA-4965) set internal.leave.group.on.close to false in KafkaStreams

[ https://issues.apache.org/jira/browse/KAFKA-4965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy updated KAFKA-4965: -- Status: Patch Available (was: In Progress) > set internal.leave.group.on.close to fa

[VOTE] KIP-134: Delay initial consumer group rebalance

Hi All, I'd like to start the voting thread on KIP-134: https://cwiki.apache.org/confluence/display/KAFKA/KIP-134%3A+Delay+initial+consumer+group+rebalance Thanks, Damian

[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: -- Status: Patch Available (was: Open) > creating a window store with one segment throws division by z

[jira] [Assigned] (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 reassigned KAFKA-4913: - Assignee: Damian Guy > creating a window store with one segment throws division by zero er

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

Thanks Matthias. +1 On Thu, 23 Mar 2017 at 22:40 Matthias J. Sax wrote: > Hi, > > I would like to start the VOTE on KIP-120: > > https://cwiki.apache.org/confluence/display/KAFKA/KIP-120%3A+Cleanup+Kafka+Streams+builder+API > > If you have further comments, please reply

Re: [DISCUSS] KIP-134: Delay initial consumer group rebalance

y they arrived within 1 sec, then "resetting clock" will cause the whole > delay to be no more than 1 + 3 = 4 secs; while extending it will cause it > to be 1 + 3 * 10 = 31 secs? > > > > Guozhang > > > On Wed, Mar 29, 2017 at 3:04 PM, Guozhang Wang <wangg

[jira] [Commented] (KAFKA-4969) State-store workload-aware StreamsPartitionAssignor

[ https://issues.apache.org/jira/browse/KAFKA-4969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15947575#comment-15947575 ] Damian Guy commented on KAFKA-4969: --- This also needs to take into account task stickyness, i.e., see

[jira] [Resolved] (KAFKA-4963) Global Store: startup recovery process skipping processor

[ https://issues.apache.org/jira/browse/KAFKA-4963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy resolved KAFKA-4963. --- Resolution: Not A Problem as [~mjsax] stated in his comment this is by design. If you want to do any

[jira] [Commented] (KAFKA-4963) Global Store: startup recovery process skipping processor

[ https://issues.apache.org/jira/browse/KAFKA-4963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15946730#comment-15946730 ] Damian Guy commented on KAFKA-4963: --- [~mjsax] what you have said is correct. This ticket can be closed

Re: [VOTE] KIP-129: Kafka Streams Exactly-Once Semantics

Thanks Matthias +1 On Wed, 29 Mar 2017 at 07:34 Eno Thereska wrote: > +1 (non-binding) > > Thanks Matthias, > Eno > > On 20 Mar 2017, at 18:27, Matthias J. Sax wrote: > > > > Hi, > > > > I would like to start the vote for KIP-129. Of course, feel

Re: [DISCUSS] KIP-134: Delay initial consumer group rebalance

fine to > > me. It matches the default consumer heartbeat interval, which controls > > typical rebalance latency, so there's some consistency there. > > > > Also, one minor comment: I guess the actual delay for each group will be > > the minimum of the group's reb

Re: [DISCUSS] KIP-134: Delay initial consumer group rebalance

ower the default value given the new approach. > > Ismael > > On Tue, Mar 28, 2017 at 9:53 AM, Damian Guy <damian@gmail.com> wrote: > > > All, > > I'd like to get this back to the original discussion about Delaying > initial > > consumer group rebalance.

Re: [DISCUSS] KIP-134: Delay initial consumer group rebalance

on that? Doing something similar on leave is valid, but i'd prefer to consider it separately from this. Thanks, Damian On Tue, 28 Mar 2017 at 09:48 Damian Guy <damian@gmail.com> wrote: > Matthias, > > Yes i know. > > Thanks, > Damian > > On Mon, 27 Mar 2017 at 18:17 Matthias

Re: [DISCUSS] KIP-134: Delay initial consumer group rebalance

uld be > able to distinguish both cases easily, and apply the delay only if it > received the LeaveGroupRequest but not if a consumer times out. > > Does this make sense? > > -Matthias > > On 3/27/17 1:56 AM, Damian Guy wrote: > > @Becket > > > > Thanks for

[jira] [Updated] (KAFKA-4965) set internal.leave.group.on.close to false in KafkaStreams

[ https://issues.apache.org/jira/browse/KAFKA-4965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy updated KAFKA-4965: -- Summary: set internal.leave.group.on.close to false in KafkaStreams (was: set leave.group.on.close

[jira] [Work started] (KAFKA-4965) set leave.group.on.close to false in KafkaStreams

[ https://issues.apache.org/jira/browse/KAFKA-4965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-4965 started by Damian Guy. - > set leave.group.on.close to false in KafkaStre

[jira] [Created] (KAFKA-4965) set leave.group.on.close to false in KafkaStreams

Damian Guy created KAFKA-4965: - Summary: set leave.group.on.close to false in KafkaStreams Key: KAFKA-4965 URL: https://issues.apache.org/jira/browse/KAFKA-4965 Project: Kafka Issue Type

Re: [DISCUSS] KIP-134: Delay initial consumer group rebalance

ood point on extending the delay > > when > > >> a new consumer joins a group (we actually did something similar to > batch > > >> ISR change propagation). For example, let's say on the broker side, we > > will > > >> always delay 2 seconds each time we s

Re: [DISCUSS] KIP-134: Delay initial consumer group rebalance

g scenarios? If a consumer group has > > 10 instanced and should be scaled up to 20, it would make sense to do > > this with a single rebalance, too. Thus, I am wondering, if it would > > make sense to apply this delay each time a new consumer joins group, > > even if th

Re: [DISCUSS] KIP-134: Delay initial consumer group rebalance

will always force > the > > coordinator to wait that long. By doing this we do not need to bump up > the > > protocol either. > > > > > > Guozhang > > > > On Thu, Mar 23, 2017 at 5:49 AM, Damian Guy <damian@gmail.com> > wrote: > >

Re: [DISCUSS] KIP-134: Delay initial consumer group rebalance

it makes > sense), so it would be good to get a bit more detail. > > Thanks, > Ismael > > On Thu, Mar 23, 2017 at 12:24 PM, Damian Guy <damian@gmail.com> wrote: > > > Hi All, > > > > I've prepared a KIP to add a configurable delay to the initial cons

[DISCUSS] KIP-134: Delay initial consumer group rebalance

Hi All, I've prepared a KIP to add a configurable delay to the initial consumer group rebalance. Please have look here: https://cwiki.apache.org/confluence/display/KAFKA/KIP-134%3A+Delay+initial+consumer+group+rebalance Thanks, Damian BTW, i apologize if this appears twice. Seems the first one

<    1   2   3   4   5   6   7   8   >