[jira] [Commented] (KAFKA-2330) Vagrantfile sets global configs instead of per-provider override configs

[ https://issues.apache.org/jira/browse/KAFKA-2330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14623651#comment-14623651 ] Ewen Cheslack-Postava commented on KAFKA-2330: -- Created reviewboard https://r

[jira] [Updated] (KAFKA-2330) Vagrantfile sets global configs instead of per-provider override configs

[ https://issues.apache.org/jira/browse/KAFKA-2330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-2330: - Attachment: KAFKA-2330.patch > Vagrantfile sets global configs instead of per-prov

[jira] [Updated] (KAFKA-2330) Vagrantfile sets global configs instead of per-provider override configs

[ https://issues.apache.org/jira/browse/KAFKA-2330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-2330: - Status: Patch Available (was: Open) > Vagrantfile sets global configs instead of

Review Request 36427: Patch for KAFKA-2330

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/36427/ --- Review request for kafka. Bugs: KAFKA-2330 https://issues.apache.org/jira/b

[jira] [Created] (KAFKA-2330) Vagrantfile sets global configs instead of per-provider override configs

Ewen Cheslack-Postava created KAFKA-2330: Summary: Vagrantfile sets global configs instead of per-provider override configs Key: KAFKA-2330 URL: https://issues.apache.org/jira/browse/KAFKA-2330

[jira] [Commented] (KAFKA-2123) Make new consumer offset commit API use callback + future

[ https://issues.apache.org/jira/browse/KAFKA-2123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14623637#comment-14623637 ] Jason Gustafson commented on KAFKA-2123: Updated reviewboard https://reviews.apach

Re: Review Request 36333: Patch for KAFKA-2123

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/36333/ --- (Updated July 12, 2015, 12:34 a.m.) Review request for kafka. Bugs: KAFKA-212

[jira] [Updated] (KAFKA-2123) Make new consumer offset commit API use callback + future

[ https://issues.apache.org/jira/browse/KAFKA-2123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-2123: --- Attachment: KAFKA-2123_2015-07-11_17:33:59.patch > Make new consumer offset commit API use cal

[jira] [Updated] (KAFKA-2329) Consumers balance fails when multiple consumers are started simultaneously.

[ https://issues.apache.org/jira/browse/KAFKA-2329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ze'ev Eli Klapow updated KAFKA-2329: Labels: consumer patch (was: patch) > Consumers balance fails when multiple consumers are s

[jira] [Updated] (KAFKA-2329) Consumers balance fails when multiple consumers are started simultaneously.

[ https://issues.apache.org/jira/browse/KAFKA-2329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ze'ev Eli Klapow updated KAFKA-2329: Attachment: zookeeper-consumer-connector-epoch-node.patch > Consumers balance fails when mul

[jira] [Updated] (KAFKA-2329) Consumers balance fails when multiple consumers are started simultaneously.

[ https://issues.apache.org/jira/browse/KAFKA-2329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ze'ev Eli Klapow updated KAFKA-2329: Status: Patch Available (was: Open) > Consumers balance fails when multiple consumers are s

[jira] [Created] (KAFKA-2329) Consumers balance fails when multiple consumers are started simultaneously.

Ze'ev Eli Klapow created KAFKA-2329: --- Summary: Consumers balance fails when multiple consumers are started simultaneously. Key: KAFKA-2329 URL: https://issues.apache.org/jira/browse/KAFKA-2329 Proje

Re: [Discussion] Limitations on topic names

I tend to agree with this as a compromise at this point. The reality is that this is technical debt that has built up in the project, and it does not go away by documenting it, and it will only get worse. As pointed out, eliminating either character at this point is going to cause problems for

Re: [Discussion] Limitations on topic names

On Sat, Jul 11, 2015 at 12:54 AM, Ewen Cheslack-Postava wrote: > On Fri, Jul 10, 2015 at 4:41 PM, Gwen Shapira wrote: > >> Yeah, I have an actual customer who ran into this. Unfortunately, >> inconsistencies in the way things are named are pretty common - just >> look at Kafka's many CLI options.

Re: [Discussion] Limitations on topic names

For resolving the metrics conflicts, we can alternatively let Kafka to replace "." with double underscores "__" if that is the primary reason for topic name restrictions. Guozhang On Sat, Jul 11, 2015 at 12:54 AM, Ewen Cheslack-Postava wrote: > On Fri, Jul 10, 2015 at 4:41 PM, Gwen Shapira > w

Re: developers list

Please look at this page: it's self service. http://kafka.apache.org/contact.html Guozhang On Fri, Jul 10, 2015 at 8:34 PM, venkateshwara reddy gowru < vrgo...@gmail.com> wrote: > add me to the developers list please > > -- > Thanks & Regards > Venkateshwara Reddy Gowru > Java Developer > Phone

developers list

add me to the developers list please -- Thanks & Regards Venkateshwara Reddy Gowru Java Developer Phone: 832-284-1559

Re: [Discussion] Limitations on topic names

On Fri, Jul 10, 2015 at 4:41 PM, Gwen Shapira wrote: > Yeah, I have an actual customer who ran into this. Unfortunately, > inconsistencies in the way things are named are pretty common - just > look at Kafka's many CLI options. > > I don't think that supporting both and pointing at the docs with

Re: Review Request 36333: Patch for KAFKA-2123

> On July 9, 2015, 1:42 a.m., Guozhang Wang wrote: > > clients/src/main/java/org/apache/kafka/clients/consumer/KafkaConsumer.java, > > line 775 > > > > > > I think KAFKA-1894 is already fixed in this patch + KAFKA-2