Re: Kafka Mailing List Filters

This is super helpful. Thanks Grant! On Wed, Apr 6, 2016 at 8:47 PM, James Cheng wrote: > Thanks Grant! These are awesome! I can actually see stuff now! :) > > -James > > > On Apr 3, 2016, at 9:41 PM, Grant Henke wrote: > > > > The Kafka development mailing list can be a lot to keep up with. To

Re: Kafka Mailing List Filters

Thanks Grant! These are awesome! I can actually see stuff now! :) -James > On Apr 3, 2016, at 9:41 PM, Grant Henke wrote: > > The Kafka development mailing list can be a lot to keep up with. To cope, I > have created a few filters to separate the most important communication > from the noise. I

[jira] [Work started] (KAFKA-3521) Better handling NPEs in Streams DSL implementation

[ https://issues.apache.org/jira/browse/KAFKA-3521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-3521 started by Guozhang Wang. > Better handling NPEs in Streams DSL implementation > --

[jira] [Work started] (KAFKA-3505) Set curRecord in punctuate() functions

[ https://issues.apache.org/jira/browse/KAFKA-3505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-3505 started by Guozhang Wang. > Set curRecord in punctuate() functions > --

[jira] [Commented] (KAFKA-3521) Better handling NPEs in Streams DSL implementation

[ https://issues.apache.org/jira/browse/KAFKA-3521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15229550#comment-15229550 ] ASF GitHub Bot commented on KAFKA-3521: --- GitHub user guozhangwang opened a pull requ

[GitHub] kafka pull request: KAFKA-3521: validate null keys in Streams DSL ...

GitHub user guozhangwang opened a pull request: https://github.com/apache/kafka/pull/1197 KAFKA-3521: validate null keys in Streams DSL implementations You can merge this pull request into a Git repository by running: $ git pull https://github.com/guozhangwang/kafka K3521 Alt

[jira] [Created] (KAFKA-3523) Capture org.apache.kafka.clients.consumer.CommitFailedException in UncaughtExceptionHandler

Guozhang Wang created KAFKA-3523: Summary: Capture org.apache.kafka.clients.consumer.CommitFailedException in UncaughtExceptionHandler Key: KAFKA-3523 URL: https://issues.apache.org/jira/browse/KAFKA-3523

[jira] [Commented] (KAFKA-3262) Make KafkaStreams debugging friendly

[ https://issues.apache.org/jira/browse/KAFKA-3262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15229508#comment-15229508 ] Guozhang Wang commented on KAFKA-3262: -- One more thing that we have observed: current

[jira] [Commented] (KAFKA-3513) Transient failure of OffsetValidationTest

[ https://issues.apache.org/jira/browse/KAFKA-3513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15229436#comment-15229436 ] Ewen Cheslack-Postava commented on KAFKA-3513: -- Yeah, minor logging improveme

[VOTE] KIP-33 - Add a time based log index

Hi all, I updated KIP-33 based on the initial implementation. Per discussion on yesterday's KIP hangout, I would like to initiate the new vote thread for KIP-33. The KIP wiki: https://cwiki.apache.org/confluence/display/KAFKA/KIP-33+-+Add+a+time+based+log+index Here is a brief summary of the KIP

Re: [VOTE] KIP-52: Kafka Connect Control APIs

Minor note: I've changed the restart API to be blocking as discussed in the other thread. -Jason On Tue, Apr 5, 2016 at 9:02 PM, Guozhang Wang wrote: > +1 > > On Tue, Apr 5, 2016 at 8:06 PM, Neha Narkhede wrote: > > > +1 > > > > On Tue, Apr 5, 2016 at 7:53 PM, Jay Kreps wrote: > > > > > +1 >

Re: [DISCUSS] KIP-52 - Add Connector Control APIs

Hey Ismael, thanks for the comments. I've updated the wiki: https://cwiki.apache.org/confluence/display/KAFKA/KIP-52%3A+Connector+Control+APIs . -Jason On Wed, Apr 6, 2016 at 4:53 PM, Ismael Juma wrote: > Hi Jason, > > The suggested changes make sense. I think it's also worth clarifying the > d

[jira] [Commented] (KAFKA-3522) Consider adding version information into rocksDB storage format

[ https://issues.apache.org/jira/browse/KAFKA-3522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15229388#comment-15229388 ] Jay Kreps commented on KAFKA-3522: -- I think you could potentially just write some version

[GitHub] kafka pull request: KAFKA-1614: Partition log directory name and s...

GitHub user xdralex opened a pull request: https://github.com/apache/kafka/pull/1196 KAFKA-1614: Partition log directory name and segments information exposed via JMX This is an updated version of https://issues.apache.org/jira/browse/KAFKA-1614 patch which was made for 0.8.1.1 ve

[jira] [Commented] (KAFKA-1614) Partition log directory name and segments information exposed via JMX

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

Re: [DISCUSS] KIP-52 - Add Connector Control APIs

Hi Jason, The suggested changes make sense. I think it's also worth clarifying the documentation for the endpoints whose behaviour will remain the same. Ismael On Wed, Apr 6, 2016 at 8:39 PM, Jason Gustafson wrote: > Hey Ismael, > > The intent is only to indicate that we've accepted the reques

[jira] [Created] (KAFKA-3522) Consider adding version information into rocksDB storage format

Guozhang Wang created KAFKA-3522: Summary: Consider adding version information into rocksDB storage format Key: KAFKA-3522 URL: https://issues.apache.org/jira/browse/KAFKA-3522 Project: Kafka

[jira] [Commented] (KAFKA-3513) Transient failure of OffsetValidationTest

[ https://issues.apache.org/jira/browse/KAFKA-3513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15229269#comment-15229269 ] Jason Gustafson commented on KAFKA-3513: [~ewencp] Took a look at this, but no luc

[jira] [Created] (KAFKA-3521) Better handling NPEs in Streams DSL implementation

Guozhang Wang created KAFKA-3521: Summary: Better handling NPEs in Streams DSL implementation Key: KAFKA-3521 URL: https://issues.apache.org/jira/browse/KAFKA-3521 Project: Kafka Issue Type:

[jira] [Commented] (KAFKA-3520) System tests of config validate and list connectors REST APIs

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

[jira] [Updated] (KAFKA-3520) System tests of config validate and list connectors REST APIs

[ https://issues.apache.org/jira/browse/KAFKA-3520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liquan Pei updated KAFKA-3520: -- Status: Patch Available (was: In Progress) > System tests of config validate and list connectors REST A

[GitHub] kafka pull request: KAFKA-3520: Add system tests for REST APIs of ...

GitHub user Ishiihara opened a pull request: https://github.com/apache/kafka/pull/1195 KAFKA-3520: Add system tests for REST APIs of list connector plugins and config validation @ewen @granders Ready for review. You can merge this pull request into a Git repository by running:

[jira] [Work started] (KAFKA-3520) System tests of config validate and list connectors REST APIs

[ https://issues.apache.org/jira/browse/KAFKA-3520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-3520 started by Liquan Pei. - > System tests of config validate and list connectors REST APIs > -

[jira] [Created] (KAFKA-3520) System tests of config validate and list connectors REST APIs

Liquan Pei created KAFKA-3520: - Summary: System tests of config validate and list connectors REST APIs Key: KAFKA-3520 URL: https://issues.apache.org/jira/browse/KAFKA-3520 Project: Kafka Issue

Tell us how you're using Kafka and what you'd like to see in the future

Folks, We'd like to hear from community members about how you are using Kafka today, and what sort of features you'd like to see in the future. We put together this survey to gather your feedback, which should take only a few minutes to complet

Re: KStreams Group Rebalance Commit Error

Hi Michael, Your issue seems like a more general one with the new Kafka Consumer regarding unexpected rebalances: as for Kafka Streams, it's committing behavior is synchronous, i.e. triggering "consumer.commitSync" of the underlying new Kafka Consumer, which will fail if there is an ongoing rebala

[jira] [Commented] (KAFKA-3337) Extract selector as a separate groupBy operator for KTable aggregations

[ https://issues.apache.org/jira/browse/KAFKA-3337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15229181#comment-15229181 ] Guozhang Wang commented on KAFKA-3337: -- [~mjsax] The pros of this approach is that 1)

[jira] [Updated] (KAFKA-2575) inconsistant offset count in replication-offset-checkpoint during lead election leads to huge exceptions

[ https://issues.apache.org/jira/browse/KAFKA-2575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-2575: - Component/s: (was: kafka streams) > inconsistant offset count in replication-offset-checkpoint

[jira] [Updated] (KAFKA-3184) Add Checkpoint for In-memory State Store

[ https://issues.apache.org/jira/browse/KAFKA-3184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-3184: - Labels: user-experience (was: ) > Add Checkpoint for In-memory State Store >

[jira] [Updated] (KAFKA-3183) Add metrics for persistent store caching layer

[ https://issues.apache.org/jira/browse/KAFKA-3183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-3183: - Labels: user-experience (was: ) > Add metrics for persistent store caching layer > --

[jira] [Updated] (KAFKA-3101) Optimize Aggregation Outputs

[ https://issues.apache.org/jira/browse/KAFKA-3101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-3101: - Labels: semantics (was: ) > Optimize Aggregation Outputs > > >

[jira] [Updated] (KAFKA-3338) Add print and writeAsText functions to the Streams DSL

[ https://issues.apache.org/jira/browse/KAFKA-3338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-3338: - Labels: api newbie++ (was: newbie++) > Add print and writeAsText functions to the Streams DSL > -

[jira] [Updated] (KAFKA-3337) Extract selector as a separate groupBy operator for KTable aggregations

[ https://issues.apache.org/jira/browse/KAFKA-3337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-3337: - Labels: api newbie++ (was: api-change newbie++) > Extract selector as a separate groupBy operator

[jira] [Updated] (KAFKA-3372) Trailing space in Kafka ConsumerConfig

[ https://issues.apache.org/jira/browse/KAFKA-3372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-3372: - Component/s: (was: kafka streams) > Trailing space in Kafka ConsumerConfig > -

[jira] [Updated] (KAFKA-3439) Document possible exception thrown in public APIs

[ https://issues.apache.org/jira/browse/KAFKA-3439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-3439: - Labels: api docs (was: ) > Document possible exception thrown in public APIs > --

[jira] [Updated] (KAFKA-3429) Remove Serdes needed for repartitioning in KTable stateful operations

[ https://issues.apache.org/jira/browse/KAFKA-3429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-3429: - Labels: api newbie++ (was: newbie++) > Remove Serdes needed for repartitioning in KTable stateful

[jira] [Updated] (KAFKA-3430) Allow users to set key in KTable.toStream() and KStream

[ https://issues.apache.org/jira/browse/KAFKA-3430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-3430: - Labels: api (was: ) > Allow users to set key in KTable.toStream() and KStream > -

[jira] [Updated] (KAFKA-3443) Support regex topics in addSource() and stream()

[ https://issues.apache.org/jira/browse/KAFKA-3443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-3443: - Labels: api (was: ) > Support regex topics in addSource() and stream() >

[jira] [Updated] (KAFKA-3452) Support session windows besides time interval windows

[ https://issues.apache.org/jira/browse/KAFKA-3452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-3452: - Labels: api (was: ) > Support session windows besides time interval windows > ---

[jira] [Updated] (KAFKA-3440) Add Javadoc for KTable (changelog stream) and KStream (record stream)

[ https://issues.apache.org/jira/browse/KAFKA-3440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-3440: - Labels: docs (was: ) > Add Javadoc for KTable (changelog stream) and KStream (record stream) > --

[jira] [Updated] (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 ] Guozhang Wang updated KAFKA-3455: - Labels: user-experience (was: ) > Connect custom processors with the streams DSL > --

[jira] [Updated] (KAFKA-3466) consumer was stuck , and offset can not be moved

[ https://issues.apache.org/jira/browse/KAFKA-3466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-3466: - Component/s: (was: kafka streams) > consumer was stuck , and offset can not be moved > --

[jira] [Updated] (KAFKA-3478) Finer Stream Flow Control

[ https://issues.apache.org/jira/browse/KAFKA-3478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-3478: - Labels: user-experience (was: ) > Finer Stream Flow Control > - > >

[jira] [Updated] (KAFKA-3497) Streams ProcessorContext should support forward() based on child name

[ https://issues.apache.org/jira/browse/KAFKA-3497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-3497: - Labels: api (was: ) > Streams ProcessorContext should support forward() based on child name > ---

[jira] [Updated] (KAFKA-3504) Changelog partition configured to enable log compaction

[ https://issues.apache.org/jira/browse/KAFKA-3504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-3504: - Labels: user-experience (was: ) > Changelog partition configured to enable log compaction > -

[jira] [Updated] (KAFKA-3499) byte[] should not be used as Map key nor Set member

[ https://issues.apache.org/jira/browse/KAFKA-3499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-3499: - Labels: user-experience (was: ) > byte[] should not be used as Map key nor Set member > -

[jira] [Updated] (KAFKA-3505) Set curRecord in punctuate() functions

[ https://issues.apache.org/jira/browse/KAFKA-3505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-3505: - Labels: user-experience (was: ) > Set curRecord in punctuate() functions > --

[jira] [Updated] (KAFKA-3511) Provide built-in aggregators sum() and avg() in Kafka Streams DSL

[ https://issues.apache.org/jira/browse/KAFKA-3511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-3511: - Labels: api newbie (was: newbie) > Provide built-in aggregators sum() and avg() in Kafka Streams

[jira] [Updated] (KAFKA-3514) Stream timestamp computation needs some further thoughts

[ https://issues.apache.org/jira/browse/KAFKA-3514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-3514: - Labels: semantics (was: time) > Stream timestamp computation needs some further thoughts > --

[jira] [Updated] (KAFKA-3512) Add a foreach() operator in Kafka Streams DSL

[ https://issues.apache.org/jira/browse/KAFKA-3512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-3512: - Labels: api (was: ) > Add a foreach() operator in Kafka Streams DSL > ---

[jira] [Updated] (KAFKA-3514) Stream timestamp computation needs some further thoughts

[ https://issues.apache.org/jira/browse/KAFKA-3514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-3514: - Labels: time (was: ) > Stream timestamp computation needs some further thoughts > ---

[jira] [Created] (KAFKA-3519) Refactor Transformer templates to return the same strong-typed value.

Guozhang Wang created KAFKA-3519: Summary: Refactor Transformer templates to return the same strong-typed value. Key: KAFKA-3519 URL: https://issues.apache.org/jira/browse/KAFKA-3519 Project: Kafka

[jira] [Updated] (KAFKA-3185) Allow users to cleanup internal data

[ https://issues.apache.org/jira/browse/KAFKA-3185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neha Narkhede updated KAFKA-3185: - Labels: developer-experience (was: ) > Allow users to cleanup internal data > ---

[jira] [Updated] (KAFKA-3262) Make KafkaStreams debugging friendly

[ https://issues.apache.org/jira/browse/KAFKA-3262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neha Narkhede updated KAFKA-3262: - Labels: developer-experience (was: ) > Make KafkaStreams debugging friendly > ---

Re: [DISCUSS] KIP-52 - Add Connector Control APIs

Hey Ismael, The intent is only to indicate that we've accepted the request, so the no-op case has no separate response code in the current proposal. The question is whether that is sufficient? For pause/resume, you can verify the effect using the status endpoint which seems OK, but restart is tric

[jira] [Updated] (KAFKA-3337) Extract selector as a separate groupBy operator for KTable aggregations

[ https://issues.apache.org/jira/browse/KAFKA-3337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neha Narkhede updated KAFKA-3337: - Labels: api-change newbie++ (was: newbie++) > Extract selector as a separate groupBy operator for

Re: [DISCUSS] KIP-43: Kafka SASL enhancements

2016-04-06 19:16 GMT+02:00 Rajini Sivaram : > Magnus, > > I have not looked at your proposal in detail yet, > Please do :) > but I have a few comments: > >1. We need to support SSL and SASL_SSL within the same broker (for >instance, to support certificate-based authentication for replic

[jira] [Created] (KAFKA-3518) Transient failure in ReplicationTest.test_replication_with_broker_failure with ConsumerTimeoutException

Ewen Cheslack-Postava created KAFKA-3518: Summary: Transient failure in ReplicationTest.test_replication_with_broker_failure with ConsumerTimeoutException Key: KAFKA-3518 URL: https://issues.apache.org/ji

[jira] [Comment Edited] (KAFKA-3494) mbeans overwritten with identical clients on a single jvm

[ https://issues.apache.org/jira/browse/KAFKA-3494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15228754#comment-15228754 ] Onur Karaman edited comment on KAFKA-3494 at 4/6/16 5:58 PM: -

[jira] [Commented] (KAFKA-3494) mbeans overwritten with identical clients on a single jvm

[ https://issues.apache.org/jira/browse/KAFKA-3494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15228754#comment-15228754 ] Onur Karaman commented on KAFKA-3494: - bq. I think we have collisions with more than j

[jira] [Commented] (KAFKA-3494) mbeans overwritten with identical clients on a single jvm

[ https://issues.apache.org/jira/browse/KAFKA-3494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15228733#comment-15228733 ] Joel Koshy commented on KAFKA-3494: --- I'm not sure that the second suggested solution in

[jira] [Created] (KAFKA-3517) Document configuration of SASL/PLAIN and multiple mechanisms

Rajini Sivaram created KAFKA-3517: - Summary: Document configuration of SASL/PLAIN and multiple mechanisms Key: KAFKA-3517 URL: https://issues.apache.org/jira/browse/KAFKA-3517 Project: Kafka

Re: [DISCUSS] KIP-43: Kafka SASL enhancements

Magnus, I have not looked at your proposal in detail yet, but I have a few comments: 1. We need to support SSL and SASL_SSL within the same broker (for instance, to support certificate-based authentication for replication and SASL for external connections). At the moment, there is a one

[jira] [Created] (KAFKA-3516) Metrics settings in server.properties cause ClassCastException

Scott Kruger created KAFKA-3516: --- Summary: Metrics settings in server.properties cause ClassCastException Key: KAFKA-3516 URL: https://issues.apache.org/jira/browse/KAFKA-3516 Project: Kafka I

Re: [DISCUSS] KIP-50 - Enhance Authorizer interface to be aware of supported Principal Types

I see value in minimizing breaking changes and I do not oppose the idea of increasing scope of KIP-50 to move auth interface to java. As authorizer implementations do not really need to depend on Kafka core, I would suggest that we keep authorizer interface and its components in a separate package

Re: [DISCUSS] KIP-50 - Enhance Authorizer interface to be aware of supported Principal Types

I understand. My thinking is that since this is a major release, if we are going to break in anyway we should do it now. Otherwise we will need to wait until 0.11. The work in adding standard exceptions and an alternative Java interface should be able to be done in a compatible manner (deprecating

Re: [DISCUSS] KIP-50 - Enhance Authorizer interface to be aware of supported Principal Types

It is small, but breaks binary compatibility. Ismael On Wed, Apr 6, 2016 at 5:20 PM, Grant Henke wrote: > KIP-50 as defined is very small. I don't see any harm in putting it in as > is and then tackling the follow up work. > > > On Wed, Apr 6, 2016 at 11:16 AM, Ismael Juma wrote: > > > Thanks

Re: [DISCUSS] KIP-50 - Enhance Authorizer interface to be aware of supported Principal Types

> > The follow-up question is where these classes should live. We have the > common package in clients for common code. However, if something is > exclusively used by the broker, we could add it under core/src/main/java > instead. There are pros and cons for each approach, so I was wondering if > s

Re: [DISCUSS] KIP-50 - Enhance Authorizer interface to be aware of supported Principal Types

KIP-50 as defined is very small. I don't see any harm in putting it in as is and then tackling the follow up work. On Wed, Apr 6, 2016 at 11:16 AM, Ismael Juma wrote: > Thanks Grant. I wonder if KIP-50 should just be done as part of this work. > > Ismael > > On Wed, Apr 6, 2016 at 5:12 PM, Gran

Re: [DISCUSS] KIP-50 - Enhance Authorizer interface to be aware of supported Principal Types

Thanks Grant. I wonder if KIP-50 should just be done as part of this work. Ismael On Wed, Apr 6, 2016 at 5:12 PM, Grant Henke wrote: > My work with KIP-4 found that many of the Scala classes used in the > Authorizer interface are needed in the Clients package when adding the > various ACL reque

Re: [DISCUSS] KIP-50 - Enhance Authorizer interface to be aware of supported Principal Types

Hi Jay, Thanks for the explanation. My take is that the main benefit in keeping pluggable broker interfaces in Java is that implementors don't have to include the Scala library (and don't have to choose a Scala version, for example). I think this is a strong enough reason on its own. I am less co

Re: [DISCUSS] KIP-50 - Enhance Authorizer interface to be aware of supported Principal Types

My work with KIP-4 found that many of the Scala classes used in the Authorizer interface are needed in the Clients package when adding the various ACL requests and responses. I also found that we don't have standard Exceptions defined for the authorizer interface. This means that when I add the Aut

Re: [DISCUSS] KIP-50 - Enhance Authorizer interface to be aware of supported Principal Types

Hey Ismael, Yeah I think this is a minor cleanliness thing. Since this is kind of a power user interface I don't feel strongly either way. My motivation with Scala is just that we've tried to move to having the public interfaces be Java, and as a group we definitely struggled a lot with understan

[jira] [Commented] (KAFKA-3497) Streams ProcessorContext should support forward() based on child name

[ https://issues.apache.org/jira/browse/KAFKA-3497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15228451#comment-15228451 ] ASF GitHub Bot commented on KAFKA-3497: --- GitHub user enothereska opened a pull reque

[GitHub] kafka pull request: KAFKA-3497: Streams ProcessorContext should su...

GitHub user enothereska opened a pull request: https://github.com/apache/kafka/pull/1194 KAFKA-3497: Streams ProcessorContext should support forward() based on child name You can merge this pull request into a Git repository by running: $ git pull https://github.com/enotheres

[jira] [Work started] (KAFKA-3497) Streams ProcessorContext should support forward() based on child name

[ https://issues.apache.org/jira/browse/KAFKA-3497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-3497 started by Eno Thereska. --- > Streams ProcessorContext should support forward() based on child name > -

[jira] [Assigned] (KAFKA-3497) Streams ProcessorContext should support forward() based on child name

[ https://issues.apache.org/jira/browse/KAFKA-3497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska reassigned KAFKA-3497: --- Assignee: Eno Thereska > Streams ProcessorContext should support forward() based on child nam

[GitHub] kafka pull request: KAFKA-3512: Added foreach operator

GitHub user enothereska opened a pull request: https://github.com/apache/kafka/pull/1193 KAFKA-3512: Added foreach operator @miguno @guozhangwang please have a look if you can. You can merge this pull request into a Git repository by running: $ git pull https://github.com/enoth

[jira] [Commented] (KAFKA-3512) Add a foreach() operator in Kafka Streams DSL

[ https://issues.apache.org/jira/browse/KAFKA-3512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15228259#comment-15228259 ] ASF GitHub Bot commented on KAFKA-3512: --- GitHub user enothereska opened a pull reque

KStreams Group Rebalance Commit Error

All,    I'm getting CommitFailedExceptions on a small prototype I built using kafkaStreams. I'm not using the DSL, but the TopologyBuilder with several processors chained together with a sink in between a few of them. When I try committing through the ProcessorContext, I see exceptions being thr

Re: [DISCUSS] KIP-43: Kafka SASL enhancements

Engineers, sorry to stir up some dust on this KIP but following yesterday's discussion on the KIP call I'm a bit concerned about the way the SASL handshake protocol is diverging even more from the main Kafka protocol. The SASL handshake is already its own special protocol and the latest addition o

[jira] [Work started] (KAFKA-3512) Add a foreach() operator in Kafka Streams DSL

[ https://issues.apache.org/jira/browse/KAFKA-3512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-3512 started by Eno Thereska. --- > Add a foreach() operator in Kafka Streams DSL > -

[jira] [Assigned] (KAFKA-3337) Extract selector as a separate groupBy operator for KTable aggregations

[ https://issues.apache.org/jira/browse/KAFKA-3337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax reassigned KAFKA-3337: -- Assignee: Matthias J. Sax > Extract selector as a separate groupBy operator for KTable

[jira] [Assigned] (KAFKA-3512) Add a foreach() operator in Kafka Streams DSL

[ https://issues.apache.org/jira/browse/KAFKA-3512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska reassigned KAFKA-3512: --- Assignee: Eno Thereska > Add a foreach() operator in Kafka Streams DSL >