[jira] [Resolved] (KAFKA-3067) Fix producer API documentation for case when RequiredAcks > 1

[ https://issues.apache.org/jira/browse/KAFKA-3067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar Reddy resolved KAFKA-3067. Resolution: Fixed Assignee: Manikumar Reddy (was: Jun Rao) Fix Version/s:

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

See Changes: [me] KAFKA-3526: Return string instead of object in ConfigKeyInfo and -- [...truncated 2450 lines...] kafka.api.ProducerFailureHandlingTest > testNotEnoughReplicas PASSED

[jira] [Commented] (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:comment-tabpanel=15243866#comment-15243866 ] josh gruenberg commented on KAFKA-3499: --- Sure, I'll take a look later tonight. > byte[] should not

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

See Changes: [me] KAFKA-3526: Return string instead of object in ConfigKeyInfo and -- [...truncated 1595 lines...] kafka.consumer.ZookeeperConsumerConnectorTest > testConsumerDecoder PASSED

[jira] [Commented] (KAFKA-3565) Producer's throughput lower with compressed data after KIP-31/32

[ https://issues.apache.org/jira/browse/KAFKA-3565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15243862#comment-15243862 ] Ismael Juma commented on KAFKA-3565: Interesting. Good to know that there are cases where the new code

[jira] [Commented] (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:comment-tabpanel=15243856#comment-15243856 ] Guozhang Wang commented on KAFKA-3499: -- [~joshng] Would you like to take a look at the PR? > byte[]

[jira] [Commented] (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:comment-tabpanel=15243852#comment-15243852 ] ASF GitHub Bot commented on KAFKA-3499: --- GitHub user guozhangwang opened a pull request:

[GitHub] kafka pull request: KAFKA-3499: prevent array typed keys in KeyVal...

GitHub user guozhangwang opened a pull request: https://github.com/apache/kafka/pull/1229 KAFKA-3499: prevent array typed keys in KeyValueStore You can merge this pull request into a Git repository by running: $ git pull https://github.com/guozhangwang/kafka K3499

[jira] [Commented] (KAFKA-3565) Producer's throughput lower with compressed data after KIP-31/32

[ https://issues.apache.org/jira/browse/KAFKA-3565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15243850#comment-15243850 ] Jiangjie Qin commented on KAFKA-3565: - The producer performance I ran was with similar tweaks you made

[jira] [Commented] (KAFKA-3565) Producer's throughput lower with compressed data after KIP-31/32

[ https://issues.apache.org/jira/browse/KAFKA-3565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15243840#comment-15243840 ] Jiangjie Qin commented on KAFKA-3565: - [~ijuma] What is your other settings? e.g.

[jira] [Created] (KAFKA-3566) Enable VerifiableProducer and ConsoleConsumer to run with interceptors

Anna Povzner created KAFKA-3566: --- Summary: Enable VerifiableProducer and ConsoleConsumer to run with interceptors Key: KAFKA-3566 URL: https://issues.apache.org/jira/browse/KAFKA-3566 Project: Kafka

[jira] [Updated] (KAFKA-3526) REST APIs return object representation instead of string for config values, default values and recommended values

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

[GitHub] kafka pull request: KAFKA-3526: Return string instead of object in...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1200 --- 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-3526) REST APIs return object representation instead of string for config values, default values and recommended values

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

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

Jitendra, Could you post your views on existing discuss thread for KIP-48, http://mail-archives.apache.org/mod_mbox/kafka-dev/201602.mbox/%3cd2f60a7c.61f2c%25pbrahmbh...@hortonworks.com%3E ? On Fri, Apr 15, 2016 at 3:11 PM, Jitendra Pandey wrote: > > The need for a

[jira] [Commented] (KAFKA-3565) Producer's throughput lower with compressed data after KIP-31/32

[ https://issues.apache.org/jira/browse/KAFKA-3565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15243699#comment-15243699 ] Ismael Juma commented on KAFKA-3565: By the way, the results with compression include the following

[jira] [Commented] (KAFKA-3565) Producer's throughput lower with compressed data after KIP-31/32

[ https://issues.apache.org/jira/browse/KAFKA-3565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15243695#comment-15243695 ] Ismael Juma commented on KAFKA-3565: [~becket_qin], do you think you can look into this? We need to

[jira] [Created] (KAFKA-3565) Producer's throughput lower with compressed data after KIP-31/32

Ismael Juma created KAFKA-3565: -- Summary: Producer's throughput lower with compressed data after KIP-31/32 Key: KAFKA-3565 URL: https://issues.apache.org/jira/browse/KAFKA-3565 Project: Kafka

[jira] [Updated] (KAFKA-3561) Auto create through topic for KStream aggregation and join

[ https://issues.apache.org/jira/browse/KAFKA-3561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-3561: - Description: For KStream.join / aggregateByKey operations that requires the streams to be

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

The need for a large number of clients that are running all over the cluster that authenticate with Kafka brokers, is very similar to the Hadoop use case of large number of tasks running across the cluster that need authentication to Hdfs Namenode. Therefore, the delegation token approach

[GitHub] kafka pull request: MINOR: Typo fixes in ReplicaFetchMaxBytesDoc

GitHub user Erethon opened a pull request: https://github.com/apache/kafka/pull/1228 MINOR: Typo fixes in ReplicaFetchMaxBytesDoc You can merge this pull request into a Git repository by running: $ git pull https://github.com/Erethon/kafka trunk Alternatively you can review

[jira] [Created] (KAFKA-3564) Count metric always increments by 1.0

Michael Coon created KAFKA-3564: --- Summary: Count metric always increments by 1.0 Key: KAFKA-3564 URL: https://issues.apache.org/jira/browse/KAFKA-3564 Project: Kafka Issue Type: Bug

Re: [RELEASE] Anyone minds if we push the next RC another week away?

+1 On Fri, Apr 15, 2016, at 08:06 AM, Grant Henke wrote: > +1 > > On Fri, Apr 15, 2016 at 10:05 AM, Ashish Singh > wrote: > > > Good idea. Thanks! > > > > On Friday, April 15, 2016, Ismael Juma wrote: > > > > > +1 > > > > > > On Fri, Apr 15, 2016 at

[GitHub] kafka pull request: KAFKA 3421: Update docs with new connector fea...

GitHub user Ishiihara opened a pull request: https://github.com/apache/kafka/pull/1227 KAFKA 3421: Update docs with new connector features @ewencp @gwenshap Docs. I also tried to clean up some typos. However, it seems that the we don't have two words without space in between in the

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

+1 from me. Thanks. On Fri, Apr 15, 2016 at 9:16 AM, Jun Rao wrote: > Hi, Jiangjie, > > Thanks for the latest update. +1 on the KIP. > > Jun > > On Thu, Apr 14, 2016 at 2:36 PM, Becket Qin wrote: > > > Hi Jun, > > > > 11. Yes, that sounds a reasonable

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

Hi, Jiangjie, Thanks for the latest update. +1 on the KIP. Jun On Thu, Apr 14, 2016 at 2:36 PM, Becket Qin wrote: > Hi Jun, > > 11. Yes, that sounds a reasonable solution. In the latest patch I am doing > the following in order: > a. Create an empty time index for a log

Re: IncompatibleClassChangeError

Thanks. I can't copy/paste stack trace since it's on an internal system. I'll do my best to hand-type the thing in here: java.lang.IncompatiableClassChangeError at scala.collection.immutable.StringLink$class.format(StringLink.scala:318)at

[jira] [Commented] (KAFKA-3358) Only request metadata updates once we have topics or a pattern subscription

[ https://issues.apache.org/jira/browse/KAFKA-3358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15243135#comment-15243135 ] Grant Henke commented on KAFKA-3358: [~hachikuji] I think it would be a valuable patch separate from

[jira] [Commented] (KAFKA-3358) Only request metadata updates once we have topics or a pattern subscription

[ https://issues.apache.org/jira/browse/KAFKA-3358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15243134#comment-15243134 ] Ismael Juma commented on KAFKA-3358: Also, are there other places where we are using `dequeFor`

[jira] [Commented] (KAFKA-3358) Only request metadata updates once we have topics or a pattern subscription

[ https://issues.apache.org/jira/browse/KAFKA-3358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15243129#comment-15243129 ] Ismael Juma commented on KAFKA-3358: [~hachikuji], I think that's a good change so I suggest you file

[jira] [Work started] (KAFKA-3421) Update docs with new connector features

[ https://issues.apache.org/jira/browse/KAFKA-3421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-3421 started by Liquan Pei. - > Update docs with new connector features > --- >

[jira] [Commented] (KAFKA-3563) Maintain MessageAndMetadata constructor compatibility

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

[jira] [Updated] (KAFKA-3563) Maintain MessageAndMetadata constructor compatibility

[ https://issues.apache.org/jira/browse/KAFKA-3563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke updated KAFKA-3563: --- Status: Patch Available (was: Open) > Maintain MessageAndMetadata constructor compatibility >

[GitHub] kafka pull request: KAFKA-3563: Maintain MessageAndMetadata constr...

GitHub user granthenke opened a pull request: https://github.com/apache/kafka/pull/1226 KAFKA-3563: Maintain MessageAndMetadata constructor compatibility You can merge this pull request into a Git repository by running: $ git pull https://github.com/granthenke/kafka

Re: [RELEASE] Anyone minds if we push the next RC another week away?

+1 On Fri, Apr 15, 2016 at 10:05 AM, Ashish Singh wrote: > Good idea. Thanks! > > On Friday, April 15, 2016, Ismael Juma wrote: > > > +1 > > > > On Fri, Apr 15, 2016 at 4:28 AM, Gwen Shapira > > wrote: > > > > > Hi

Re: [RELEASE] Anyone minds if we push the next RC another week away?

Good idea. Thanks! On Friday, April 15, 2016, Ismael Juma wrote: > +1 > > On Fri, Apr 15, 2016 at 4:28 AM, Gwen Shapira > wrote: > > > Hi Team, > > > > As we got more time, we merrily expended the scope of all our > > in-progress KIPs :) > >

[jira] [Created] (KAFKA-3563) Maintain MessageAndMetadata constructor compatibility

Grant Henke created KAFKA-3563: -- Summary: Maintain MessageAndMetadata constructor compatibility Key: KAFKA-3563 URL: https://issues.apache.org/jira/browse/KAFKA-3563 Project: Kafka Issue Type:

Re: [VOTE] KIP-4 Metadata Schema (Round 2)

Thanks! Ismael On Fri, Apr 15, 2016 at 3:36 PM, Grant Henke wrote: > I added a row on the main KIP wiki page to indicate the metadata changes > will be in 0.10 and I also update the KIP-4 wiki too. > > Thanks, > Grant > > On Fri, Apr 15, 2016 at 9:27 AM, Ismael Juma

Re: [VOTE] KIP-4 Metadata Schema (Round 2)

I added a row on the main KIP wiki page to indicate the metadata changes will be in 0.10 and I also update the KIP-4 wiki too. Thanks, Grant On Fri, Apr 15, 2016 at 9:27 AM, Ismael Juma wrote: > Third time is a charm. :) Can you please update the wiki page below to > include

Re: [VOTE] KIP-4 Metadata Schema (Round 2)

Third time is a charm. :) Can you please update the wiki page below to include this KIP in the adopted table and 0.10.0.0 as the release? https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Improvement+Proposals I know we already have KIP-4 in that table, but I think it's useful for people

Re: [VOTE] KIP-4 Metadata Schema (Round 2)

Thanks to all who voted. The KIP-4 Metadata changes passed with +3 (binding), and +4 (non-binding). There is a patch available for review here: https://github.com/apache/kafka/pull/1095 On Tue, Apr 12, 2016 at 11:23 AM, Jason Gustafson wrote: > +1 (non-binding) > > On Mon,

Re: IncompatibleClassChangeError

Hi Michael, We would need more information to be able to help. We don't serialize scala objects and clients should be able to use different Scala versions than the broker. Do you have a stacktrace of when the exception is thrown? Ismael On Fri, Apr 15, 2016 at 2:39 PM, Michael D. Coon

IncompatibleClassChangeError

We are seeing odd behavior that we need to understand. We are getting IncompatibleClassChangeErrors and I know that's related to a Scala version mismatch. What's not clear, however, is where or why the mismatch is occurring. We know up front that there were occasions where we ran apps that had

[jira] [Commented] (KAFKA-3558) Add compression_type parameter to benchmarks in benchmark_test.py

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

[GitHub] kafka pull request: KAFKA-3558; Add compression_type parameter to ...

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/1225 KAFKA-3558; Add compression_type parameter to benchmarks in benchmark_test.py * Use a fixed `Random` seed in `EndToEndLatency.scala` for determinism * Add `compression_type` to and remove

[jira] [Commented] (KAFKA-3525) max.reserved.broker.id off-by-one error

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

[jira] [Updated] (KAFKA-3525) max.reserved.broker.id off-by-one error

[ https://issues.apache.org/jira/browse/KAFKA-3525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar Reddy updated KAFKA-3525: --- Status: Patch Available (was: Open) > max.reserved.broker.id off-by-one error >

[GitHub] kafka pull request: KAFKA-3525; getSequenceId should return 1 for ...

GitHub user omkreddy opened a pull request: https://github.com/apache/kafka/pull/1224 KAFKA-3525; getSequenceId should return 1 for first path creation You can merge this pull request into a Git repository by running: $ git pull https://github.com/omkreddy/kafka KAFKA-3525

Re: [RELEASE] Anyone minds if we push the next RC another week away?

+1 On Fri, Apr 15, 2016 at 4:28 AM, Gwen Shapira wrote: > Hi Team, > > As we got more time, we merrily expended the scope of all our > in-progress KIPs :) > > I want to be able to at least get some of them in. > > Do you feel that pushing the next RC from Apr 22 (next week)

[jira] [Created] (KAFKA-3562) Null Pointer Exception Found when delete topic and Using New Producer

Pengwei created KAFKA-3562: -- Summary: Null Pointer Exception Found when delete topic and Using New Producer Key: KAFKA-3562 URL: https://issues.apache.org/jira/browse/KAFKA-3562 Project: Kafka

[jira] [Commented] (KAFKA-3559) Task creation time taking too long in rebalance callback

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

[GitHub] kafka pull request: KAFKA-3559: lazy initialisation of state store...

GitHub user enothereska opened a pull request: https://github.com/apache/kafka/pull/1223 KAFKA-3559: lazy initialisation of state stores Instead of initialising state stores on init(), they are initialised on first access. You can merge this pull request into a Git repository by

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

See

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

See Changes: [me] KAFKA-3549: Close consumers instantiated in consumer tests -- [...truncated 5423 lines...] kafka.log.BrokerCompressionTest > testBrokerSideCompression[2] PASSED