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

See Changes: [cshapi] KAFKA-3454: add Kafka Streams web docs [me] KAFKA-3316: Add REST API for listing connector plugins -- [...truncated 2863 lines...] kafka.log.CleanerTest > testCleaningWit

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

See Changes: [me] KAFKA-3316: Add REST API for listing connector plugins -- [...truncated 1627 lines...] kafka.log.LogTest > testTruncateTo PASSED kafka.log.LogTest > testCleanShutdownFile PASS

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

See Changes: [cshapi] KAFKA-3454: add Kafka Streams web docs -- [...truncated 1626 lines...] kafka.log.OffsetIndexTest > randomLookupTest PASSED kafka.log.OffsetIndexTest > testReopen PASSED k

[jira] [Commented] (KAFKA-3469) kafka-topics lock down znodes with user principal when zk security is enabled.

[ https://issues.apache.org/jira/browse/KAFKA-3469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15212647#comment-15212647 ] Ashish K Singh commented on KAFKA-3469: --- One option to avoid this is to use a config

[jira] [Created] (KAFKA-3469) kafka-topics lock down znodes with user principal when zk security is enabled.

Ashish K Singh created KAFKA-3469: - Summary: kafka-topics lock down znodes with user principal when zk security is enabled. Key: KAFKA-3469 URL: https://issues.apache.org/jira/browse/KAFKA-3469 Projec

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

See

[GitHub] kafka pull request: KAFKA-3316: Add REST API for listing connector...

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

[jira] [Commented] (KAFKA-3316) Add Connect REST API to list available connector classes

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

[jira] [Updated] (KAFKA-3316) Add Connect REST API to list available connector classes

[ https://issues.apache.org/jira/browse/KAFKA-3316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-3316: - Resolution: Fixed Fix Version/s: 0.10.1.0 Status: Resolved (was:

Build failed in Jenkins: kafka-0.10.0-jdk7 #16

See Changes: [wangguoz] KAFKA-3449: Rename filterOut() to filterNot() to achieve better -- [...truncated 2503 lines...] kafka.coordinator.GroupCoordinatorResponseTest > testLeaveGroupWrongCoordi

Re: [VOTE] KIP-51 - List Connectors REST API

Thanks for voting everyone, this passes with 4 binding +1s and 11 +1s total. On Wed, Mar 23, 2016 at 11:37 AM, Andrew Schofield < andrew_schofield_j...@outlook.com> wrote: > +1 (non-binding) > > +1 for re-evaluating the KIP process. This one went through very quickly, > but they can drag on somet

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

See Changes: [wangguoz] KAFKA-3449: Rename filterOut() to filterNot() to achieve better -- [...truncated 1625 lines...] kafka.log.LogTest > testTruncateTo PASSED kafka.log.LogTest > testCleanSh

[jira] [Commented] (KAFKA-3454) Add Kafka Streams section in documentation

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

[jira] [Resolved] (KAFKA-3454) Add Kafka Streams section in documentation

[ https://issues.apache.org/jira/browse/KAFKA-3454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira resolved KAFKA-3454. - Resolution: Fixed Issue resolved by pull request 1127 [https://github.com/apache/kafka/pull/1127]

[GitHub] kafka pull request: KAFKA-3454: add Kafka Streams web docs

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

[jira] [Commented] (KAFKA-3456) In-house KafkaMetric misreports metrics when periodically observed

[ https://issues.apache.org/jira/browse/KAFKA-3456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15212514#comment-15212514 ] Aditya Auradkar commented on KAFKA-3456: Accidentally changed the thread title to

[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: - Affects Version/s: (was: 0.9.0.1) 0.10.0.1 > Connect custom processors

Build failed in Jenkins: kafka-0.10.0-jdk7 #15

See Changes: [cshapi] KAFKA-3463: change default receive buffer size for consumer to 64K -- [...truncated 3118 lines...] kafka.log.BrokerCompressionTest > testBrokerSideCompression[17] PASSED k

[jira] [Updated] (KAFKA-3456) bihtfbucbcceinvujekclljidcuf

[ https://issues.apache.org/jira/browse/KAFKA-3456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aditya Auradkar updated KAFKA-3456: --- Summary: bihtfbucbcceinvujekclljidcuf (was: In-house KafkaMetric misreports metrics when peri

[jira] [Updated] (KAFKA-3456) In-house KafkaMetric misreports metrics when periodically observed

[ https://issues.apache.org/jira/browse/KAFKA-3456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aditya Auradkar updated KAFKA-3456: --- Summary: In-house KafkaMetric misreports metrics when periodically observed (was: bihtfbucbcc

[GitHub] kafka pull request: MINOR: change initial value of Min stat to Dou...

GitHub user zackdever opened a pull request: https://github.com/apache/kafka/pull/1143 MINOR: change initial value of Min stat to Double.MAX_VALUE (not MIN) this is consistent with the Max stat implementation. You can merge this pull request into a Git repository by running: $

[jira] [Commented] (KAFKA-3449) Rename filterOut() to filterNot() to achieve better terminology

[ https://issues.apache.org/jira/browse/KAFKA-3449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15212485#comment-15212485 ] Guozhang Wang commented on KAFKA-3449: -- [~ancosen] I have added you to the contributo

[jira] [Commented] (KAFKA-3449) Rename filterOut() to filterNot() to achieve better terminology

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

[jira] [Resolved] (KAFKA-3449) Rename filterOut() to filterNot() to achieve better terminology

[ https://issues.apache.org/jira/browse/KAFKA-3449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-3449. -- Resolution: Fixed Fix Version/s: (was: 0.10.0.1) 0.10.0.0 Issue re

[GitHub] kafka pull request: KAFKA-3449: Rename filterOut() to filterNot() ...

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

[jira] [Updated] (KAFKA-3449) Rename filterOut() to filterNot() to achieve better terminology

[ https://issues.apache.org/jira/browse/KAFKA-3449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-3449: - Assignee: Andrea Cosentino > Rename filterOut() to filterNot() to achieve better terminology > ---

Re: KStream/KTable prioritization/initial offset

Hello Greg, You can pass underlying client configs for consumer and producer as well into StreamsConfig, e.g.: props.put(ConsumerConfig.AUTO_OFFSET_RESET_CONFIG, "earliest"); As for your case, since ConsumerConfig.AUTO_OFFSET_REST_CONFIG takes universal effects on all topics that do not have co

Re: Kafka Connect ++ Kafka Streams

I am thinking maybe we can even consider pulling the project as a whole into examples instead of adding the connector and streams implementation separately into Kafka Connect and Kafka Streams if Michal is interested to filing a PR: currently the examples folder only contains consumer / producer de

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

See Changes: [cshapi] KAFKA-3463: change default receive buffer size for consumer to 64K -- [...truncated 1596 lines...] kafka.log.LogTest > testIndexResizingAtTruncation PASSED kafka.log.LogT

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

See Changes: [cshapi] KAFKA-3463: change default receive buffer size for consumer to 64K -- [...truncated 1634 lines...] kafka.log.LogTest > testTruncateTo PASSED kafka.log.LogTest > testCleanSh

Re: KStream/KTable prioritization/initial offset

Hey Jay, thanks -- the timestamp alignment makes sense and clears up why prioritization isn't needed, thanks. It sounds like the one thing I still don't understand is how we can tell Kafka Streams to start reading from the latest or earliest offset for a given source. I might be thinking about thi

[jira] [Work started] (KAFKA-3436) Speed up controlled shutdown.

[ https://issues.apache.org/jira/browse/KAFKA-3436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-3436 started by Jiangjie Qin. --- > Speed up controlled shutdown. > - > >

[jira] [Commented] (KAFKA-2511) KIP-31 & KIP-32: message format change + adding timestamp to messages

[ https://issues.apache.org/jira/browse/KAFKA-2511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15212350#comment-15212350 ] Jiangjie Qin commented on KAFKA-2511: - Not yet. KIP-33 solves that. > KIP-31 & KIP-32

[jira] [Commented] (KAFKA-3463) Change default consumer receive buffer size to 64K

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

[GitHub] kafka pull request: KAFKA-3463: change default receive buffer size...

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

[jira] [Resolved] (KAFKA-3463) Change default consumer receive buffer size to 64K

[ https://issues.apache.org/jira/browse/KAFKA-3463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira resolved KAFKA-3463. - Resolution: Fixed Issue resolved by pull request 1140 [https://github.com/apache/kafka/pull/1140]

[jira] [Commented] (KAFKA-3449) Rename filterOut() to filterNot() to achieve better terminology

[ https://issues.apache.org/jira/browse/KAFKA-3449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15212285#comment-15212285 ] Guozhang Wang commented on KAFKA-3449: -- Thanks [~ancosen] for your patch! [~yasuhiro.

[jira] [Updated] (KAFKA-3449) Rename filterOut() to filterNot() to achieve better terminology

[ https://issues.apache.org/jira/browse/KAFKA-3449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-3449: - Reviewer: Yasuhiro Matsuda > Rename filterOut() to filterNot() to achieve better terminology > ---

Re: KStream/KTable prioritization/initial offset

Hey Greg, I think the use case you have is that you have some derived state and you want to make sure it is fully populated before any of the input streams are populated. There would be two ways to accomplish this: (1) have a changelog that captures the state, (2) reprocess the input to recreate t

Re: KStream/KTable prioritization/initial offset

That's great. Is there anything I can do to force that particular topic to start at the earliest message every time the job is started? On Mar 25, 2016 10:20 AM, "Yasuhiro Matsuda" wrote: > It may not be ideal, but there is a way to prioritize particular topics. It > is to set the record timestam

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

See Changes: [cshapi] KAFKA-3460: Remove old 0.7 KafkaMigrationTool -- [...truncated 1623 lines...] kafka.log.LogTest > testTruncateTo PASSED kafka.log.LogTest > testCleanShutdownFile PASSED k

Build failed in Jenkins: kafka-0.10.0-jdk7 #14

See Changes: [cshapi] KAFKA-3460: Remove old 0.7 KafkaMigrationTool -- [...truncated 1556 lines...] kafka.consumer.ZookeeperConsumerConnectorTest > testConsumerDecoder PASSED kafka.consumer.Zoo

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

See Changes: [cshapi] KAFKA-3460: Remove old 0.7 KafkaMigrationTool -- [...truncated 1579 lines...] kafka.log.LogTest > testIndexRebuild PASSED kafka.log.LogTest > testLogRolls PASSED kafka.l

[jira] [Commented] (KAFKA-2511) KIP-31 & KIP-32: message format change + adding timestamp to messages

[ https://issues.apache.org/jira/browse/KAFKA-2511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15212155#comment-15212155 ] Xavier Léauté commented on KAFKA-2511: -- I believe this fixes https://issues.apache.or

Re: KStream/KTable prioritization/initial offset

It may not be ideal, but there is a way to prioritize particular topics. It is to set the record timestamps to zero. This can be done by using a custom TimestampExtractor. Kafka Streams tries to synchronize multiple streams using the extracted timestamps. So, records with the timestamp 0 have great

[jira] [Updated] (KAFKA-3460) Remove old 0.7 KafkaMigrationTool

[ https://issues.apache.org/jira/browse/KAFKA-3460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-3460: Resolution: Fixed Status: Resolved (was: Patch Available) Issue resolved by pull request 11

[jira] [Commented] (KAFKA-3460) Remove old 0.7 KafkaMigrationTool

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

[GitHub] kafka pull request: KAFKA-3460: Remove old 0.7 KafkaMigrationTool

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

[jira] [Commented] (KAFKA-2998) New Consumer should not retry indefinitely if no broker is available

[ https://issues.apache.org/jira/browse/KAFKA-2998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15212084#comment-15212084 ] Grant Henke commented on KAFKA-2998: [~hachikuji] I opened KAFKA-3468 before finding t

[jira] [Created] (KAFKA-3468) Java clients never fail when bootstrap uses incorrect port

Grant Henke created KAFKA-3468: -- Summary: Java clients never fail when bootstrap uses incorrect port Key: KAFKA-3468 URL: https://issues.apache.org/jira/browse/KAFKA-3468 Project: Kafka Issue Ty

Problem with kafka doFlush method

Hi, I have created Confluent Connect (http://docs.confluent.io/2.0.1/connect/?) sink and source tasks. While working in standalone mode there are no errrors or exceptions. But, when i start tasks in distributed mode i get NullPointerException while OffsetStorageWriter is executing doFlush()

[jira] [Commented] (KAFKA-1490) remove gradlew initial setup output from source distribution

[ https://issues.apache.org/jira/browse/KAFKA-1490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15212025#comment-15212025 ] Konstantin Boudnik commented on KAFKA-1490: --- I came across this long closed issu

Re: Kafka Connect ++ Kafka Streams

Michal -- This is really cool. Mind submitting a pull request? Also, would you like your IRC connector to be featured on the Kafka Connector Hub ? On Fri, Mar 25, 2016 at 9:08 AM, Michal Hariš wrote: > So I had a go and hacked it up here: ConnectEmbedded.java > <

[jira] [Resolved] (KAFKA-3467) can't run streams-smoke-test.sh from binary distribution

[ https://issues.apache.org/jira/browse/KAFKA-3467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-3467. -- Resolution: Fixed > can't run streams-smoke-test.sh from binary distribution >

[jira] [Commented] (KAFKA-3467) can't run streams-smoke-test.sh from binary distribution

[ https://issues.apache.org/jira/browse/KAFKA-3467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15212003#comment-15212003 ] Guozhang Wang commented on KAFKA-3467: -- I think `bin/streams-smoke-test.sh` has been

Re: Kafka Connect ++ Kafka Streams

So I had a go and hacked it up here: ConnectEmbedded.java And this is how the wikipedia demo looks with it: hello-kafka-streams

[jira] [Created] (KAFKA-3467) can't run streams-smoke-test.sh from binary distribution

Jun Rao created KAFKA-3467: -- Summary: can't run streams-smoke-test.sh from binary distribution Key: KAFKA-3467 URL: https://issues.apache.org/jira/browse/KAFKA-3467 Project: Kafka Issue Type: Impro

[jira] [Commented] (KAFKA-3398) avoid just sending to one partition when record key is empty string

[ https://issues.apache.org/jira/browse/KAFKA-3398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15211789#comment-15211789 ] ASF GitHub Bot commented on KAFKA-3398: --- Github user vesense closed the pull request

[GitHub] kafka pull request: KAFKA-3398: avoid just sending to one partitio...

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

[jira] [Resolved] (KAFKA-3398) avoid just sending to one partition when record key is empty string

[ https://issues.apache.org/jira/browse/KAFKA-3398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xin Wang resolved KAFKA-3398. - Resolution: Not A Problem > avoid just sending to one partition when record key is empty string >

[jira] [Commented] (KAFKA-3456) In-house KafkaMetric misreports metrics when periodically observed

[ https://issues.apache.org/jira/browse/KAFKA-3456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15211669#comment-15211669 ] The Data Lorax commented on KAFKA-3456: --- I see your point here Jay. But surely in ge

Broker hangs all of a sudden.

Hi All, This really looks like a bug to me. I'm running Kafka 2.11-0.9.0.1. Running 2 brokers, 3 consumers. On a day to day basis, everything is working smoothly. All of a sudden, out of nowhere one of the brokers hangs and the producers lack to send messages to it, since it is the leader of some

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

chao created KAFKA-3466: --- Summary: consumer was stuck , and offset can not be moved Key: KAFKA-3466 URL: https://issues.apache.org/jira/browse/KAFKA-3466 Project: Kafka Issue Type: Bug Compo