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

See

[jira] [Updated] (KAFKA-4882) Remove internal converter configuration from example property files

[ https://issues.apache.org/jira/browse/KAFKA-4882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mitch Seymour updated KAFKA-4882: - Status: Patch Available (was: Open) First patch.. Not too sure what version to attach this to :\

[jira] [Commented] (KAFKA-4882) Remove internal converter configuration from example property files

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

[GitHub] kafka pull request #2675: KAFKA-4882: Remove internal converter configuratio...

GitHub user mitch-seymour opened a pull request: https://github.com/apache/kafka/pull/2675 KAFKA-4882: Remove internal converter configuration from example property files Connect works best with the default JSON converters, and exposing the internal converter config tempts users

[jira] [Assigned] (KAFKA-4882) Remove internal converter configuration from example property files

[ https://issues.apache.org/jira/browse/KAFKA-4882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mitch Seymour reassigned KAFKA-4882: Assignee: Mitch Seymour > Remove internal converter configuration from example property

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

See

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

See Changes: [wangguoz] KAFKA-4738: Remove generic type of class ClientState -- [...truncated 849.89 KB...] org.apache.kafka.streams.KafkaStreamsTest >

[jira] [Commented] (KAFKA-4574) Transient failure in ZooKeeperSecurityUpgradeTest.test_zk_security_upgrade with security_protocol = SASL_PLAINTEXT, SSL

[ https://issues.apache.org/jira/browse/KAFKA-4574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15905989#comment-15905989 ] Apurva Mehta commented on KAFKA-4574: - I posted all the information I could glean from the logs. The

[jira] [Commented] (KAFKA-4574) Transient failure in ZooKeeperSecurityUpgradeTest.test_zk_security_upgrade with security_protocol = SASL_PLAINTEXT, SSL

[ https://issues.apache.org/jira/browse/KAFKA-4574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15905983#comment-15905983 ] Apurva Mehta commented on KAFKA-4574: - Here is everything from the state change logs. {noformat}

[GitHub] kafka pull request #2671: MINOR: incorrect javadoc formatting

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2671 --- 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-4574) Transient failure in ZooKeeperSecurityUpgradeTest.test_zk_security_upgrade with security_protocol = SASL_PLAINTEXT, SSL

[ https://issues.apache.org/jira/browse/KAFKA-4574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15905939#comment-15905939 ] Apurva Mehta commented on KAFKA-4574: - Here are all the leader changes for this partition across all

[jira] [Commented] (KAFKA-4858) Long topic names created using old kafka-topics.sh can prevent newer brokers from joining any ISRs

[ https://issues.apache.org/jira/browse/KAFKA-4858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15905927#comment-15905927 ] Vahid Hashemian commented on KAFKA-4858: [~jeffwidman] Well, assuming we are using an old client

[jira] [Commented] (KAFKA-4858) Long topic names created using old kafka-topics.sh can prevent newer brokers from joining any ISRs

[ https://issues.apache.org/jira/browse/KAFKA-4858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15905917#comment-15905917 ] Jeff Widman commented on KAFKA-4858: I saw the PR ignores those topics... is this a silent failure?

Re: [DISCUSS] KIP-82 - Add Record Headers

Hi Ismael, Yes, it makes sense to do benchmark. My concern was based on the observation in KAFKA-3994 where we saw GC problem when creating new lists in the purgatory. Thanks, Jiangjie (Becket) Qin On Fri, Mar 10, 2017 at 8:54 AM, Ismael Juma wrote: > Hi Becket, > > Sorry

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

See

[GitHub] kafka pull request #2674: MINOR: Fix a documentation typo

GitHub user vahidhashemian opened a pull request: https://github.com/apache/kafka/pull/2674 MINOR: Fix a documentation typo You can merge this pull request into a Git repository by running: $ git pull https://github.com/vahidhashemian/kafka minor/fix_typos_1703 Alternatively

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

See Changes: [wangguoz] MINOR: increase RocksDb parallelism -- [...truncated 159.05 KB...] kafka.log.LogTest > testCorruptIndexRebuild STARTED kafka.log.LogTest >

[jira] [Commented] (KAFKA-4574) Transient failure in ZooKeeperSecurityUpgradeTest.test_zk_security_upgrade with security_protocol = SASL_PLAINTEXT, SSL

[ https://issues.apache.org/jira/browse/KAFKA-4574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15905837#comment-15905837 ] Apurva Mehta commented on KAFKA-4574: - >From the server logs, we see that the logs were truncated to

[jira] [Commented] (KAFKA-4858) Long topic names created using old kafka-topics.sh can prevent newer brokers from joining any ISRs

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

[GitHub] kafka pull request #2673: KAFKA-4858: Broker should ignore long topic names

GitHub user vahidhashemian opened a pull request: https://github.com/apache/kafka/pull/2673 KAFKA-4858: Broker should ignore long topic names Starting from the 0.10.0.0 release topics names of over 249 characters are not allowed (`kafka-topics.sh` would disallow the creation).

[jira] [Commented] (KAFKA-4574) Transient failure in ZooKeeperSecurityUpgradeTest.test_zk_security_upgrade with security_protocol = SASL_PLAINTEXT, SSL

[ https://issues.apache.org/jira/browse/KAFKA-4574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15905778#comment-15905778 ] Apurva Mehta commented on KAFKA-4574: - It appears than different messages wound up at the same offset:

[jira] [Commented] (KAFKA-4657) Improve test coverage of CompositeReadOnlyWindowStore

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

[GitHub] kafka pull request #2672: KAFKA-4657: Improve test coverage of CompositeRead...

GitHub user adyach opened a pull request: https://github.com/apache/kafka/pull/2672 KAFKA-4657: Improve test coverage of CompositeReadOnlyWindowStore This commmit brings improved test coverage for window store fetch method and WindowStoreIterator You can merge this pull request

[GitHub] kafka pull request #2663: MINOR: increase RocksDb parallelism

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2663 --- 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-120: Cleanup Kafka Streams builder API

One more question here: 3. with TopologyDescription, do we still want to keep the `KafkaStream.toString()` function? I think it may still have some advantage such that it contains tasks information after `KafkaStream#start()` has been called, but much of it is duplicate with the

[GitHub] kafka pull request #2671: MINOR: incorrect javadoc formatting

GitHub user acoburn opened a pull request: https://github.com/apache/kafka/pull/2671 MINOR: incorrect javadoc formatting When wrapped in a `{@code ...}` block, `` are not formatted as `<>`. For instance, see the formatting of the example in

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

Hello Florian, As for programmatically discover monitoring data by piping metrics into a dedicated topic. I think you can actually use a KafkaMetricsReporter which pipes the polled metric values into a pre-defined topic (note that in Kafka the MetricsReporter is simply an interface and users can

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

+dev as well. -- Forwarded message -- From: Guozhang Wang Date: Thu, Mar 9, 2017 at 11:20 PM Subject: Re: [DISCUSS] KIP-120: Cleanup Kafka Streams builder API To: "us...@kafka.apache.org" Thanks Matthias, the updated KIP lgtm

Re: [DISCUSS] KIP-125: ZookeeperConsumerConnector to KafkaConsumer Migration and Rollback

I forgot to mention that in that above idea, the "coordination.migration.mode" config would default to "auto". On Fri, Mar 10, 2017 at 1:08 AM, Onur Karaman wrote: > Hey Jason. > > Thanks for the comments! > > Regarding 1: I've been considering something like this

[jira] [Created] (KAFKA-4884) __consumer_offsets topic processing consuming all resources

Tom Coupland created KAFKA-4884: --- Summary: __consumer_offsets topic processing consuming all resources Key: KAFKA-4884 URL: https://issues.apache.org/jira/browse/KAFKA-4884 Project: Kafka

[jira] [Updated] (KAFKA-4738) Remove generic type of class ClientState

[ https://issues.apache.org/jira/browse/KAFKA-4738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-4738: - Resolution: Fixed Fix Version/s: 0.11.0.0 Status: Resolved (was: Patch

[jira] [Commented] (KAFKA-4738) Remove generic type of class ClientState

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

[GitHub] kafka pull request #2616: KAFKA-4738: Remove generic type of class ClientSta...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2616 --- 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] [Created] (KAFKA-4883) invalid client sasl.jaas.config triggers NullPointerException

Xavier Léauté created KAFKA-4883: Summary: invalid client sasl.jaas.config triggers NullPointerException Key: KAFKA-4883 URL: https://issues.apache.org/jira/browse/KAFKA-4883 Project: Kafka

[jira] [Updated] (KAFKA-4883) invalid client sasl.jaas.config triggers NullPointerException

[ https://issues.apache.org/jira/browse/KAFKA-4883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xavier Léauté updated KAFKA-4883: - Priority: Minor (was: Major) > invalid client sasl.jaas.config triggers NullPointerException >

[jira] [Created] (KAFKA-4882) Remove internal converter configuration from example property files

Gwen Shapira created KAFKA-4882: --- Summary: Remove internal converter configuration from example property files Key: KAFKA-4882 URL: https://issues.apache.org/jira/browse/KAFKA-4882 Project: Kafka

[VOTE] KIP-117: Add a public AdminClient API for Kafka admin operations

Hi all, I'd like to start voting on KIP-117 (https://cwiki.apache.org/confluence/display/KAFKA/KIP-117%3A+Add+a+public+AdminClient+API+for+Kafka+admin+operations ). The discussion thread can be found here: https://www.mail-archive.com/dev@kafka.apache.org/msg65697.html best, Colin

[jira] [Commented] (KAFKA-4835) Allow users control over repartitioning

[ https://issues.apache.org/jira/browse/KAFKA-4835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15905515#comment-15905515 ] Matthias J. Sax commented on KAFKA-4835: If you use a custom partitioner that is solely based on

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

Hey Ismael, Thanks for your comments. Please see my reply below. On Fri, Mar 10, 2017 at 9:12 AM, Ismael Juma wrote: > Hi Dong, > > Thanks for the updates, they look good. A couple of comments below. > > On Tue, Mar 7, 2017 at 7:30 PM, Dong Lin wrote: >

[GitHub] kafka pull request #2670: MINOR: updated incorrect JavaDocs for joins

GitHub user mjsax opened a pull request: https://github.com/apache/kafka/pull/2670 MINOR: updated incorrect JavaDocs for joins You can merge this pull request into a Git repository by running: $ git pull https://github.com/mjsax/kafka fixJavaDocsRepartitioning Alternatively

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

See Changes: [wangguoz] MINOR: KStream: fix typo in javadoc -- [...truncated 922.23 KB...] org.apache.kafka.connect.runtime.WorkerSinkTaskThreadedTest > testRewind PASSED

Re: [VOTE] KIP-107: Add purgeDataBefore() API in AdminClient

Hey Jason, Just to clarify, are you, together with Ismael and Jeff, suggesting that the new request should be named PurgeRecordsRequest instead of PurgeRequest? The advantage of PurgeRecordsRequest is the name itself is more explicit about what it does. The disadvantage of PurgeRecordsRequest is

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

Thanks Jason for the feedback! Yes it makes sense to always use the MemoryPool is we can. I've updated the KIP with the suggestion On Fri, Mar 10, 2017 at 1:18 AM, Jason Gustafson wrote: > Just a minor comment. The KIP suggests that coordinator responses are > always

[jira] [Commented] (KAFKA-4877) Expose TimestampType in Producer RecordMetadata

[ https://issues.apache.org/jira/browse/KAFKA-4877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15905444#comment-15905444 ] Jason Gustafson commented on KAFKA-4877: Yeah, I didn't have a specific use case in mind, but

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

Hi Dong, Thanks for the updates, they look good. A couple of comments below. On Tue, Mar 7, 2017 at 7:30 PM, Dong Lin wrote: > > > > > 3. Another point regarding operational procedures, with a large enough > > cluster, disk failures may not be that uncommon. It may be worth

Re: Wiki permission

Have left some comments on the PR. Guozhang On Fri, Mar 10, 2017 at 8:17 AM, Marc Juchli wrote: > Hi Guozhang, > > Ok, I was initially confused as someone mentioned in the comment of > KAFKA-4772 that such a KIP is required there. > I therefore tackled both issues at the same

Re: [DISCUSS] KIP-82 - Add Record Headers

Hi Becket, Sorry for the delay and thanks for your comments. Comments inline. On Wed, Mar 1, 2017 at 8:59 PM, Becket Qin wrote: > > The difference is that the user chooses the value type. They are free to > > choose a mutable or immutable type. A generic interceptor

Re: Wiki permission

Hi Guozhang, Ok, I was initially confused as someone mentioned in the comment of KAFKA-4772 that such a KIP is required there. I therefore tackled both issues at the same time and prepared a KIP and created PR to discuss this. However, since the KIP slows things down I guess its smarter to solve

[GitHub] kafka pull request #2668: MINOR: KStream: fix typo in javadoc

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2668 --- 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: Wiki permission

KAFKA-4830 though, would require a KIP. On Fri, Mar 10, 2017 at 7:47 AM, Guozhang Wang wrote: > Hi Marc, > > I have added you for wiki access. On the other hand KAFKA-4772 would not > require a KIP as it does not change any public APIs, it just clean up the > internal

Re: Wiki permission

Hi Marc, I have added you for wiki access. On the other hand KAFKA-4772 would not require a KIP as it does not change any public APIs, it just clean up the internal implementations of these public APIs. Guozhang On Fri, Mar 10, 2017 at 7:10 AM, Marc Juchli wrote: > Hi all,

Kafka design query

Hi Experts, I am new to Kafka and programming world. Just want to know that if i want to pull messages from another comupter to kafka cluster, for example if i have computer A - source and Computer B which is having kafka setup then to pull the messages from computer A where i need to run the

Re: Kafka design query

Also if it is computer A then do i need to install Kafka on Computer A too. On Fri, Mar 10, 2017 at 4:27 PM, amit tomar wrote: > Hi Experts, > > I am new to Kafka and programming world. Just want to know that if i want > to pull messages from another comupter to kafka

Wiki permission

Hi all, I am preparing a KIP for KAFKA-4772. May I have permissions to create a child page of the KIP page? Username: mjuchli Thanks and regards, Marc

[jira] [Commented] (KAFKA-4772) Exploit #peek to implement #print() and other methods

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

[GitHub] kafka pull request #2669: KAFKA-4772: [WIP] Use peek to implement print

GitHub user backender opened a pull request: https://github.com/apache/kafka/pull/2669 KAFKA-4772: [WIP] Use peek to implement print **PROPOSAL/DISCUSSION FOR KIP-132.** Tackles [KAFKA-4772](https://issues.apache.org/jira/browse/KAFKA-4772) and

Re: Wiki edit permission

Hi all, I am preparing a KIP for KAFKA-4720. May I have permissions to create a child page of the KIP page? Thanks and regards, Marc On Tue, Mar 7, 2017 at 4:17 PM Molnár Bálint wrote: > Thanks, Guozhang:) > > 2017-03-07 16:03 GMT+01:00 Guozhang Wang

[GitHub] kafka pull request #2668: MINOR: KStream: fix typo in javadoc

GitHub user miguno opened a pull request: https://github.com/apache/kafka/pull/2668 MINOR: KStream: fix typo in javadoc You can merge this pull request into a Git repository by running: $ git pull https://github.com/miguno/kafka trunk-kstream-javadoc-typo Alternatively you

[GitHub] kafka pull request #2667: MINOR: Used in-built TimeUnit conversion function

GitHub user Kamal15 opened a pull request: https://github.com/apache/kafka/pull/2667 MINOR: Used in-built TimeUnit conversion function You can merge this pull request into a Git repository by running: $ git pull https://github.com/Kamal15/kafka timeunit Alternatively you can

[GitHub] kafka pull request #2666: MINOR: Used in-built TimeUnit conversion function

Github user Kamal15 closed the pull request at: https://github.com/apache/kafka/pull/2666 --- 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 #2666: MINOR: Used in-built TimeUnit conversion function

GitHub user Kamal15 opened a pull request: https://github.com/apache/kafka/pull/2666 MINOR: Used in-built TimeUnit conversion function You can merge this pull request into a Git repository by running: $ git pull https://github.com/Kamal15/kafka trunk Alternatively you can

[jira] [Resolved] (KAFKA-4880) Add KTable/GlobalKTable Join to Streams

[ https://issues.apache.org/jira/browse/KAFKA-4880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy resolved KAFKA-4880. --- Resolution: Duplicate > Add KTable/GlobalKTable Join to Streams >

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

Hi Matthias, Thanks for the response. I agree with you regarding the use of PartitionGrouper to reduce the number of tasks. It would be good to have an idea of any additional load on the brokers as we increase the number of tasks and therefore producers. Thanks, Damian On Wed, 8 Mar 2017 at

[jira] [Comment Edited] (KAFKA-4790) Kafka cannot recover after a disk full

[ https://issues.apache.org/jira/browse/KAFKA-4790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15904333#comment-15904333 ] Pengwei edited comment on KAFKA-4790 at 3/10/17 10:54 AM: -- [~junrao] If KIP-98

[jira] [Updated] (KAFKA-4790) Kafka cannot recover after a disk full

[ https://issues.apache.org/jira/browse/KAFKA-4790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4790: --- Fix Version/s: 0.11.0.0 > Kafka cannot recover after a disk full >

[jira] [Resolved] (KAFKA-3990) Kafka New Producer may raise an OutOfMemoryError

[ https://issues.apache.org/jira/browse/KAFKA-3990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-3990. -- Resolution: Duplicate > Kafka New Producer may raise an OutOfMemoryError >

[jira] [Resolved] (KAFKA-3391) Kafka to ZK timeout

[ https://issues.apache.org/jira/browse/KAFKA-3391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-3391. -- Resolution: Not A Problem Please reopen if the issue still exists. > Kafka to ZK timeout >

[jira] [Resolved] (KAFKA-1436) Idempotent Producer / Duplicate Detection

[ https://issues.apache.org/jira/browse/KAFKA-1436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-1436. -- Resolution: Duplicate > Idempotent Producer / Duplicate Detection >

[jira] [Resolved] (KAFKA-639) RESTful proxy

[ https://issues.apache.org/jira/browse/KAFKA-639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-639. - Resolution: Duplicate > RESTful proxy > - > > Key: KAFKA-639 >

[jira] [Commented] (KAFKA-4835) Allow users control over repartitioning

[ https://issues.apache.org/jira/browse/KAFKA-4835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15904785#comment-15904785 ] Michal Borowiecki commented on KAFKA-4835: -- Yes, that's the case. Message key is a concatenation

[jira] [Resolved] (KAFKA-4807) Kafka broker fail over bug in zookeeper

[ https://issues.apache.org/jira/browse/KAFKA-4807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-4807. -- Resolution: Duplicate > Kafka broker fail over bug in zookeeper >

[jira] [Created] (KAFKA-4881) Add internal leave.group.on.close config to consumer

Damian Guy created KAFKA-4881: - Summary: Add internal leave.group.on.close config to consumer Key: KAFKA-4881 URL: https://issues.apache.org/jira/browse/KAFKA-4881 Project: Kafka Issue Type:

Re: [DISCUSS] KIP-125: ZookeeperConsumerConnector to KafkaConsumer Migration and Rollback

Hey Jason. Thanks for the comments! Regarding 1: I've been considering something like this for a while now. KIP-122 has a similar issue and I brought up some hacks in that discussion to work around it (http://markmail.org/message/kk4ng74riejidify). While solving this problem would help loosen

[jira] [Commented] (KAFKA-4880) Add KTable/GlobalKTable Join to Streams

[ https://issues.apache.org/jira/browse/KAFKA-4880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15904745#comment-15904745 ] Michael Noll commented on KAFKA-4880: - FWIW, I wonder how much interest there actually is for this

[jira] [Created] (KAFKA-4880) Add KTable/GlobalKTable Join to Streams

Damian Guy created KAFKA-4880: - Summary: Add KTable/GlobalKTable Join to Streams Key: KAFKA-4880 URL: https://issues.apache.org/jira/browse/KAFKA-4880 Project: Kafka Issue Type: New Feature

[jira] [Commented] (KAFKA-4835) Allow users control over repartitioning

[ https://issues.apache.org/jira/browse/KAFKA-4835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15904709#comment-15904709 ] Michael Noll commented on KAFKA-4835: - Just to clarify: {quote} However, in our case I know that both