[jira] [Resolved] (KAFKA-14942) CopyOnWriteMap implements ConcurrentMap but does not implement required default methods

[ https://issues.apache.org/jira/browse/KAFKA-14942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steven Schlansker resolved KAFKA-14942. --- Resolution: Invalid > CopyOnWriteMap implements ConcurrentMap but d

[jira] [Created] (KAFKA-14942) CopyOnWriteMap implements ConcurrentMap but does not implement required default methods

Steven Schlansker created KAFKA-14942: - Summary: CopyOnWriteMap implements ConcurrentMap but does not implement required default methods Key: KAFKA-14942 URL: https://issues.apache.org/jira/browse/KAFKA-14942

[jira] [Resolved] (KAFKA-13593) ThrottledChannelReaper slows broker shutdown by multiple seconds

[ https://issues.apache.org/jira/browse/KAFKA-13593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steven Schlansker resolved KAFKA-13593. --- Resolution: Fixed > ThrottledChannelReaper slows broker shutdown by multi

[jira] [Created] (KAFKA-13593) ThrottledChannelReaper slows broker shutdown by multiple seconds

Steven Schlansker created KAFKA-13593: - Summary: ThrottledChannelReaper slows broker shutdown by multiple seconds Key: KAFKA-13593 URL: https://issues.apache.org/jira/browse/KAFKA-13593 Project

[jira] [Created] (KAFKA-6767) OffsetCheckpoint write assumes parent directory exists

Steven Schlansker created KAFKA-6767: Summary: OffsetCheckpoint write assumes parent directory exists Key: KAFKA-6767 URL: https://issues.apache.org/jira/browse/KAFKA-6767 Project: Kafka

[jira] [Commented] (KAFKA-4829) Improve logging of StreamTask commits

[ https://issues.apache.org/jira/browse/KAFKA-4829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16050793#comment-16050793 ] Steven Schlansker commented on KAFKA-4829: -- This is talking about application logs; the link

[jira] [Comment Edited] (KAFKA-4829) Improve logging of StreamTask commits

[ https://issues.apache.org/jira/browse/KAFKA-4829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16050793#comment-16050793 ] Steven Schlansker edited comment on KAFKA-4829 at 6/15/17 5:10 PM

Re: [DISCUSS] KIP-156 Add option "dry run" to Streams application reset tool

> On May 8, 2017, at 11:14 AM, BigData dev wrote: > > Hi All, > I want to start a discussion on this simple KIP for Kafka Streams reset > tool (kafka-streams-application-reset.sh). > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=69410150 I've not

[jira] [Commented] (KAFKA-1313) Support adding replicas to existing topic partitions via kafka-topics tool without manually setting broker assignments

[ https://issues.apache.org/jira/browse/KAFKA-1313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15993414#comment-15993414 ] Steven Schlansker commented on KAFKA-1313: -- I started using Kafka Streams recently. I did

Re: [VOTE] 0.10.2.1 RC0

> On Apr 7, 2017, at 5:12 PM, Gwen Shapira wrote: > > Hello Kafka users, developers and client-developers, > > This is the first candidate for the release of Apache Kafka 0.10.2.1. This > is a bug fix release and it includes fixes and improvements from 24 JIRAs > (including

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

> On Mar 13, 2017, at 12:30 PM, Matthias J. Sax wrote: > > Jay, > > thanks for your feedback > >> What if instead we called it KStreamsBuilder? > > That's the current name and I personally think it's not the best one. > The main reason why I don't like KStreamsBuilder

[jira] [Updated] (KAFKA-4829) Improve logging of StreamTask commits

[ https://issues.apache.org/jira/browse/KAFKA-4829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steven Schlansker updated KAFKA-4829: - Description: Currently I see this every commit interval: {code} 2017-02-28T21:27:16.659Z

[jira] [Created] (KAFKA-4829) Improve logging of StreamTask commits

Steven Schlansker created KAFKA-4829: Summary: Improve logging of StreamTask commits Key: KAFKA-4829 URL: https://issues.apache.org/jira/browse/KAFKA-4829 Project: Kafka Issue Type

[jira] [Updated] (KAFKA-4829) Improve logging of StreamTask commits

[ https://issues.apache.org/jira/browse/KAFKA-4829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steven Schlansker updated KAFKA-4829: - Description: Currently I see this every commit interval: {code} 2017-02-28T21:27:16.659Z

[jira] [Commented] (KAFKA-4787) KafkaStreams close() is not reentrant

[ https://issues.apache.org/jira/browse/KAFKA-4787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15879336#comment-15879336 ] Steven Schlansker commented on KAFKA-4787: -- I'm not sure I understand why that should behave

[jira] [Commented] (KAFKA-4787) KafkaStreams close() is not reentrant

[ https://issues.apache.org/jira/browse/KAFKA-4787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15879019#comment-15879019 ] Steven Schlansker commented on KAFKA-4787: -- A simple solution could simply have further close

[jira] [Created] (KAFKA-4787) KafkaStreams close() is not reentrant

Steven Schlansker created KAFKA-4787: Summary: KafkaStreams close() is not reentrant Key: KAFKA-4787 URL: https://issues.apache.org/jira/browse/KAFKA-4787 Project: Kafka Issue Type

Re: KIP-121 [VOTE]: Add KStream peek method

Oops, sorry, a number of votes were sent only to -dev and not to -user and so I missed those in the email I just sent. The actual count is more like +8 > On Feb 15, 2017, at 12:24 PM, Steven Schlansker <sschlans...@opentable.com> > wrote: > > From reading the bylaws it's

Re: KIP-121 [VOTE]: Add KStream peek method

14, 2017, at 3:36 PM, Zakee <kzak...@netzero.net> wrote: > > +1 > > -Zakee >> On Feb 14, 2017, at 1:56 PM, Jay Kreps <j...@confluent.io> wrote: >> >> +1 >> >> Nice improvement. >> >> -Jay >> >> On Tue, Feb 14, 201

Re: KIP-121 [VOTE]: Add KStream peek method

2/8/17 4:51 PM, Gwen Shapira wrote: >> +1 (binding) >> >> On Wed, Feb 8, 2017 at 4:45 PM, Steven Schlansker >> <sschlans...@opentable.com> wrote: >>> Hi everyone, >>> >>> Thank you for constructive feedback on KIP-121, >>> KStre

KIP-121 [VOTE]: Add KStream peek method

Hi everyone, Thank you for constructive feedback on KIP-121, KStream.peek(ForeachAction) ; it seems like it is time to call a vote which I hope will pass easily :) https://cwiki.apache.org/confluence/display/KAFKA/KIP-121%3A+Add+KStream+peek+method I believe the PR attached is already in

Re: KIP-121 [Discuss]: Add KStream peek method

no Thereska <eno.there...@gmail.com> >>>> wrote: >>>>>>> >>>>>>>> Hi, >>>>>>>> >>>>>>>> I like the proposal, thank you. I have found it frustrating myself >>>> not to >>

Re: KIP-121 [Discuss]: Add KStream peek method

gt;>> >>>> On Mon, Feb 6, 2017 at 5:48 PM, Matthias J. Sax <matth...@confluent.io >>> >>> wrote: >>>>> Steven, >>>>> >>>>> Thanks for your KIP. I move this discussion to dev mailing list -- >> KIPs >&g

Request Wiki edit permission for stevenschlansker

Hi dev@, I recently signed up for the Kafka Wiki as 'stevenschlansker' and would like to contribute a KIP. May I please have edit access to do so? Thanks! signature.asc Description: Message signed with OpenPGP using GPGMail

[jira] [Updated] (KAFKA-4726) ValueMapper should have (read) access to key

[ https://issues.apache.org/jira/browse/KAFKA-4726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steven Schlansker updated KAFKA-4726: - Description: {{ValueMapper}} should have read-only access to the key for the value

[jira] [Created] (KAFKA-4726) ValueMapper should have (read) access to key

Steven Schlansker created KAFKA-4726: Summary: ValueMapper should have (read) access to key Key: KAFKA-4726 URL: https://issues.apache.org/jira/browse/KAFKA-4726 Project: Kafka Issue

[jira] [Commented] (KAFKA-4722) StreamThread should allow customization of thread prefix

[ https://issues.apache.org/jira/browse/KAFKA-4722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15850243#comment-15850243 ] Steven Schlansker commented on KAFKA-4722: -- That would be perfect, thanks :) > StreamThr

[jira] [Commented] (KAFKA-4722) StreamThread should allow customization of thread prefix

[ https://issues.apache.org/jira/browse/KAFKA-4722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15849098#comment-15849098 ] Steven Schlansker commented on KAFKA-4722: -- I have multiple different functional sections of my

[jira] [Created] (KAFKA-4722) StreamThread should allow customization of thread prefix

Steven Schlansker created KAFKA-4722: Summary: StreamThread should allow customization of thread prefix Key: KAFKA-4722 URL: https://issues.apache.org/jira/browse/KAFKA-4722 Project: Kafka

[jira] [Created] (KAFKA-4721) KafkaStreams (and possibly others) should inherit Closeable

Steven Schlansker created KAFKA-4721: Summary: KafkaStreams (and possibly others) should inherit Closeable Key: KAFKA-4721 URL: https://issues.apache.org/jira/browse/KAFKA-4721 Project: Kafka

[jira] [Created] (KAFKA-4720) Add KStream.peek(ForeachAction<K,V>)

Steven Schlansker created KAFKA-4720: Summary: Add KStream.peek(ForeachAction<K,V>) Key: KAFKA-4720 URL: https://issues.apache.org/jira/browse/KAFKA-4720 Project: Kafka Issue Typ

[jira] [Created] (KAFKA-3921) Periodic refresh of metadata causes spurious log messages

Steven Schlansker created KAFKA-3921: Summary: Periodic refresh of metadata causes spurious log messages Key: KAFKA-3921 URL: https://issues.apache.org/jira/browse/KAFKA-3921 Project: Kafka

Re: No longer supporting Java 6, if? when?

Java 6 has been End of Life since Feb 2013. Java 7 (and 8, but unfortunately that's too new still) has very compelling features which can make development a lot easier. The sooner more projects drop Java 6 the better, in my opinion :) On Nov 5, 2014, at 7:45 PM, Worthy LaFollette