[GitHub] kafka pull request #1570: KAFKA-3914: Global discovery of state stores

Github user dguy closed the pull request at: https://github.com/apache/kafka/pull/1570 --- 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-3914) Global discovery of state stores

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

[jira] [Commented] (KAFKA-3914) Global discovery of state stores

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

[jira] [Commented] (KAFKA-3360) Add a protocol page/section to the official Kafka documentation

[ https://issues.apache.org/jira/browse/KAFKA-3360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15356947#comment-15356947 ] Petr Novotnik commented on KAFKA-3360: -- I'm sorry, but I also cannot find a better place to ask for

Re: Use Kafka 0.9.0.1 or 0.10.0.0 with Zookeeper 3.5

Thanks Flavio Your last statement is the key here. What we really need is to secure connections between Kafka and zk and between zk nodes. Our understanding so far is that zk 3.5 will allow us to do that so we want to understand what we need to do in Kafka side in order to use TLS connections to

[jira] [Resolved] (KAFKA-3761) Controller has RunningAsBroker instead of RunningAsController state

[ https://issues.apache.org/jira/browse/KAFKA-3761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-3761. Resolution: Fixed > Controller has RunningAsBroker instead of RunningAsController state >

[jira] [Updated] (KAFKA-3761) Controller has RunningAsBroker instead of RunningAsController state

[ https://issues.apache.org/jira/browse/KAFKA-3761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3761: --- Fix Version/s: 0.10.1.0 > Controller has RunningAsBroker instead of RunningAsController state >

Re: KTable.filter usage, memory consumption and materialized view semantics

Guozhang, my latest commit would propose that semantics of your JIRA case 2 be changed a little to suppress nulls when not sendingOldValues and not materializing. When a table T2 is created first from another table T1 and the filter does not match for the key k from T1, the invalid key k does not

[jira] [Commented] (KAFKA-3919) Broker faills to start after ungraceful shutdown due to non-monotonically incrementing offsets in logs

[ https://issues.apache.org/jira/browse/KAFKA-3919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15356679#comment-15356679 ] Andy Coates commented on KAFKA-3919: [~ijuma] - duplicate submission not intentional, (Jira timed out

[GitHub] kafka pull request #1576: KAFKA-3914: Global discovery of state stores

GitHub user dguy opened a pull request: https://github.com/apache/kafka/pull/1576 KAFKA-3914: Global discovery of state stores @guozhangwang @enothereska @mjsax @miguno please take a look. A few things that need to be clarified 1. I've added

Re: [DISCUSS] KIP-60 - Make Java client class loading more flexible

Since this is a small change, I will start vote on this tomorrow if there are no objections. The code has been tested with OSGi, so it does work and the approach is flexible enough to work in other environments too. On Mon, May 9, 2016 at 1:37 PM, Rajini Sivaram

[jira] [Commented] (KAFKA-1981) Make log compaction point configurable

[ https://issues.apache.org/jira/browse/KAFKA-1981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15357222#comment-15357222 ] Eric Wasserman commented on KAFKA-1981: --- [~junrao] could you please take a look at the pull request

[jira] [Comment Edited] (KAFKA-3103) Transient Failure in kafka.integration.PlaintextTopicMetadataTest.testIsrAfterBrokerShutDownAndJoinsBack

[ https://issues.apache.org/jira/browse/KAFKA-3103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15357538#comment-15357538 ] Guozhang Wang edited comment on KAFKA-3103 at 6/30/16 5:47 PM: --- And another

[jira] [Commented] (KAFKA-3103) Transient Failure in kafka.integration.PlaintextTopicMetadataTest.testIsrAfterBrokerShutDownAndJoinsBack

[ https://issues.apache.org/jira/browse/KAFKA-3103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15357538#comment-15357538 ] Guozhang Wang commented on KAFKA-3103: -- And another case of this case as well:

[jira] [Comment Edited] (KAFKA-3103) Transient Failure in kafka.integration.PlaintextTopicMetadataTest.testIsrAfterBrokerShutDownAndJoinsBack

[ https://issues.apache.org/jira/browse/KAFKA-3103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15357538#comment-15357538 ] Guozhang Wang edited comment on KAFKA-3103 at 6/30/16 5:47 PM: --- And another

[jira] [Commented] (KAFKA-3877) Gradle compiler daemon exits with non-zero exit code while running LogOffsetTest

[ https://issues.apache.org/jira/browse/KAFKA-3877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15357533#comment-15357533 ] Guozhang Wang commented on KAFKA-3877: -- I saw a slightly different failure on the same test case,

[GitHub] kafka pull request #1575: hotfix: check join window boundaries

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1575 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Updated] (KAFKA-3663) Proposal for a kafka broker command - kafka-brokers.sh

[ https://issues.apache.org/jira/browse/KAFKA-3663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayesh Thakrar updated KAFKA-3663: -- Status: Patch Available (was: Open) Pull request - https://github.com/apache/kafka/pull/1539

[GitHub] kafka pull request #1573: hotfix: check join window boundaries

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1573 --- 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-3740) Add configs for RocksDBStores

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

[GitHub] kafka pull request #1553: KAFKA-3740: Add configs for RocksDBStore

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1553 --- 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: KTable.filter usage, memory consumption and materialized view semantics

Hmm, I'm not sure if we can optimize this case as well. Following your example: KTable T1 = builder.table("source-topic"); KTable T2 = table.filter(value > 2); And suppose the "source-topic" is piping the messages to T1 as: {a: 3}, {b: 5}, {a: 1}... When {a: 3} is passed from T1 to T2, the

[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

[GitHub] kafka pull request #1555: MINOR: Fix ambiguous log message in RecordCollecto...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1555 --- 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-3922) Add a copy-constructor to AbstractStream

Florian Hussonnois created KAFKA-3922: - Summary: Add a copy-constructor to AbstractStream Key: KAFKA-3922 URL: https://issues.apache.org/jira/browse/KAFKA-3922 Project: Kafka Issue Type:

Re: Issue? With java Producer (v9)

Hi, just curious if I'm reporting this potential bug to the wrong list.. should I post it somewhere else? > On Jun 28, 2016, at 3:00 PM, Fumo, Vincent wrote: > > Hello. I've posted a similar email to the users group but haven't had much > luck determining if what I'm

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

See

[jira] [Commented] (KAFKA-3705) Support non-key joining in KTable

[ https://issues.apache.org/jira/browse/KAFKA-3705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15357696#comment-15357696 ] Guozhang Wang commented on KAFKA-3705: -- Yeah this clarifies a lot. I see that you are not trying to

Can I get a code review on my PR for KAFKA-3809? "Auto-generate documentation for topic-level configuration"

Hi Kafka devs, Can I get a code review on my pull request for https://issues.apache.org/jira/browse/KAFKA-3809? The code has been waiting for review for about a week. I think I clicked everything correctly in JIRA/Github to mark it ready for review, but it’s possible I missed something.

[jira] [Comment Edited] (KAFKA-3360) Add a protocol page/section to the official Kafka documentation

[ https://issues.apache.org/jira/browse/KAFKA-3360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15356947#comment-15356947 ] Petr Novotnik edited comment on KAFKA-3360 at 6/30/16 8:56 PM: --- I'm sorry,

[jira] [Resolved] (KAFKA-3846) Connect record types should include timestamps

[ https://issues.apache.org/jira/browse/KAFKA-3846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava resolved KAFKA-3846. -- Resolution: Fixed Issue resolved by pull request 1537

[GitHub] kafka pull request #1537: KAFKA-3846: KIP-65: include timestamp in Connect r...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1537 --- 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-3846) Connect record types should include timestamps

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

[jira] [Assigned] (KAFKA-3887) StreamBounceTest.test_bounce and StreamSmokeTest.test_streams failing

[ https://issues.apache.org/jira/browse/KAFKA-3887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang reassigned KAFKA-3887: Assignee: Guozhang Wang (was: Eno Thereska) > StreamBounceTest.test_bounce and

Re: [DISCUSS] KIP-48 Support for delegation tokens as an authentication mechanism

Parth, Thanks for the reply. It makes sense to only allow the renewal by users that authenticated using *non* delegation token mechanism. Then, should we make the renewal a list? For example, in the case of rest proxy, it will be useful for every instance of rest proxy to be able to renew the

[jira] [Commented] (KAFKA-3915) LogCleaner IO buffers do not account for potential size difference due to message format change

[ https://issues.apache.org/jira/browse/KAFKA-3915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15357996#comment-15357996 ] Jun Rao commented on KAFKA-3915: Yes, we could choose to only keep the old message format if converting a

[jira] [Commented] (KAFKA-3904) File descriptor leaking (Too many open files) for long running stream process

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

[GitHub] kafka pull request #1563: KAFKA-3904: File descriptor leaking (Too many open...

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

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

See Changes: [me] KAFKA-3846: KIP-65: include timestamp in Connect record types -- [...truncated 6647 lines...] kafka.message.ByteBufferMessageSetTest > testValidBytes PASSED

[jira] [Commented] (KAFKA-2857) ConsumerGroupCommand throws GroupCoordinatorNotAvailableException when describing a non-existent group before the offset topic is created

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

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

See Changes: [me] KAFKA-3846: KIP-65: include timestamp in Connect record types -- [...truncated 4557 lines...] kafka.server.LogRecoveryTest > testHWCheckpointNoFailuresMultipleLogSegments

Re: [VOTE] KIP-55: Secure quotas for authenticated users

Rajini, The latest wiki looks good to me. Perhaps you want to ask other people to also take a look and then we can start the voting. Thanks, Jun On Tue, Jun 28, 2016 at 6:27 AM, Rajini Sivaram < rajinisiva...@googlemail.com> wrote: > Jun, > > Thank you for the review. I have changed all

[jira] [Commented] (KAFKA-3904) File descriptor leaking (Too many open files) for long running stream process

[ https://issues.apache.org/jira/browse/KAFKA-3904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15358038#comment-15358038 ] Henry Cai commented on KAFKA-3904: -- This is a dup of KAFKA-3619 > File descriptor leaking (Too many open

[jira] [Resolved] (KAFKA-3904) File descriptor leaking (Too many open files) for long running stream process

[ https://issues.apache.org/jira/browse/KAFKA-3904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Henry Cai resolved KAFKA-3904. -- Resolution: Duplicate Dup of KAFKA-3619 > File descriptor leaking (Too many open files) for long

[jira] [Commented] (KAFKA-2857) ConsumerGroupCommand throws GroupCoordinatorNotAvailableException when describing a non-existent group before the offset topic is created

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

[GitHub] kafka pull request #1548: KAFKA-2857 ConsumerGroupCommand throws GroupCoordi...

GitHub user imandhan reopened a pull request: https://github.com/apache/kafka/pull/1548 KAFKA-2857 ConsumerGroupCommand throws GroupCoordinatorNotAvailableException when describing a non-existent group before the offset topic is created Added a check to make sure different cases

[GitHub] kafka pull request #1548: KAFKA-2857 ConsumerGroupCommand throws GroupCoordi...

Github user imandhan closed the pull request at: https://github.com/apache/kafka/pull/1548 --- 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-3854) Subsequent regex subscription calls fail

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

[GitHub] kafka pull request #1577: KAFKA-3794: added stream / table names as prefix t...

GitHub user bbejeck opened a pull request: https://github.com/apache/kafka/pull/1577 KAFKA-3794: added stream / table names as prefix to functions that pr… …int to the console. You can merge this pull request into a Git repository by running: $ git pull

[jira] [Commented] (KAFKA-3794) Add Stream / Table prefix in print functions

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

[GitHub] kafka pull request #1566: MINOR: bug fixes to ducktape services

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1566 --- 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-3854) Subsequent regex subscription calls fail

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

[GitHub] kafka pull request #1572: KAFKA-3854: Fix issues with new consumer's subsequ...

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

[GitHub] kafka pull request #1572: KAFKA-3854: Fix issues with new consumer's subsequ...

GitHub user vahidhashemian reopened a pull request: https://github.com/apache/kafka/pull/1572 KAFKA-3854: Fix issues with new consumer's subsequent regex (pattern) subscriptions This patch fixes two issues: 1. Subsequent regex subscriptions fail with the new consumer. 2.

[jira] [Resolved] (KAFKA-3918) Broker faills to start after ungraceful shutdown due to non-monotonically incrementing offsets in logs

[ https://issues.apache.org/jira/browse/KAFKA-3918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Coates resolved KAFKA-3918. Resolution: Duplicate > Broker faills to start after ungraceful shutdown due to non-monotonically