[jira] [Resolved] (KAFKA-3005) delete kafka topic without delete.topic.enable=true

[ https://issues.apache.org/jira/browse/KAFKA-3005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar Reddy resolved KAFKA-3005. Resolution: Not A Problem Your approach is error prone. Use rolling restart to set

[jira] [Resolved] (KAFKA-1058) Change the patch review tool to use the reviewboard python client

[ https://issues.apache.org/jira/browse/KAFKA-1058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar Reddy resolved KAFKA-1058. Resolution: Won't Fix Kafka code contribution process is moved to Github PR process. >

[jira] [Resolved] (KAFKA-119) Avoid duplicated code in ProducerPerformance

[ https://issues.apache.org/jira/browse/KAFKA-119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar Reddy resolved KAFKA-119. --- Resolution: Won't Fix ProducerPerformance.scala is deprecated. New ProducerPerformance tool

[jira] [Commented] (KAFKA-3573) JSON (de)serialization for kafka-client

[ https://issues.apache.org/jira/browse/KAFKA-3573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15245148#comment-15245148 ] Guozhang Wang commented on KAFKA-3573: -- We were working on moving the serdes from connect to common:

Re: kafka streaming: passing config string to Processor

Hello, I think Kafka Streams is better treated as one approach in streaming processing systems for a variety of customers. For example, say if you already have a YARN cluster, and you have a dedicated team operating it and many teams wants to use this for their various streaming jobs, then

[jira] [Commented] (KAFKA-3429) Remove Serdes needed for repartitioning in KTable stateful operations

[ https://issues.apache.org/jira/browse/KAFKA-3429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15245142#comment-15245142 ] Guozhang Wang commented on KAFKA-3429: -- The {{originalSerde}} is used to materialize the KTable that

[jira] [Comment Edited] (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=15245007#comment-15245007 ] Ismael Juma edited comment on KAFKA-3565 at 4/18/16 12:29 AM: -- Becket, 1.

[jira] [Comment Edited] (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=15245007#comment-15245007 ] Ismael Juma edited comment on KAFKA-3565 at 4/18/16 12:30 AM: -- Becket, 1.

[jira] [Comment Edited] (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=15245007#comment-15245007 ] Ismael Juma edited comment on KAFKA-3565 at 4/18/16 12:29 AM: -- Becket, 1.

[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=15245007#comment-15245007 ] Ismael Juma commented on KAFKA-3565: Becket, 1. Yes, the non-compressed throughput change is

[jira] [Updated] (KAFKA-3554) Generate actual data with specific compression ratio in the ProducerPerformance tool.

[ https://issues.apache.org/jira/browse/KAFKA-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-3554: Description: Currently the ProducerPerformance always generate the payload with same bytes. This

[jira] [Updated] (KAFKA-3554) Generate actual data with specific compression ratio and add multi-thread support in the ProducerPerformance tool.

[ https://issues.apache.org/jira/browse/KAFKA-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-3554: Summary: Generate actual data with specific compression ratio and add multi-thread support in the

[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=15244946#comment-15244946 ] Jiangjie Qin commented on KAFKA-3565: - [~ijuma] A few comments: 1. The performance improvement

[jira] [Commented] (KAFKA-3573) JSON (de)serialization for kafka-client

[ https://issues.apache.org/jira/browse/KAFKA-3573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15244831#comment-15244831 ] Igor Stepanov commented on KAFKA-3573: -- Good point, found your code here:

Re: kafka streaming: passing config string to Processor

Thanks for the answer. But is it correct in this case to use yahoo streaming benchmark to compare Kafka, Flink and Storm? Or Kafka streaming processor is for other category of customers? Best regards 2016-04-17 16:48 GMT+02:00 Matthias J. Sax : > KafkaStreams works quite

Re: KTable.count(...)

Hi Damin, I am new to KStreams as well, so my answer might not be 100% precise. In KTable, the same key is treated as updates instead of events. Thus aggregation on the same key will do some de-dup. The docs for the tech preview contains some explanation on this behavior:

[jira] [Commented] (KAFKA-3429) Remove Serdes needed for repartitioning in KTable stateful operations

[ https://issues.apache.org/jira/browse/KAFKA-3429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15244771#comment-15244771 ] Matthias J. Sax commented on KAFKA-3429: [~guozhang] I am a little confused here:

[jira] [Commented] (KAFKA-3573) JSON (de)serialization for kafka-client

[ https://issues.apache.org/jira/browse/KAFKA-3573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15244768#comment-15244768 ] Liquan Pei commented on KAFKA-3573: --- Thanks for working on this. Currently, there is a JSON

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

+1 On Sat, Apr 16, 2016 at 10:25 PM, Gwen Shapira wrote: > +1 > > On Fri, Apr 15, 2016 at 9:37 AM, Guozhang Wang wrote: > > +1 from me. Thanks. > > > > On Fri, Apr 15, 2016 at 9:16 AM, Jun Rao wrote: > > > >> Hi, Jiangjie, > >> > >>

[jira] [Assigned] (KAFKA-3101) Optimize Aggregation Outputs

[ https://issues.apache.org/jira/browse/KAFKA-3101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Bejeck reassigned KAFKA-3101: -- Assignee: Bill Bejeck > Optimize Aggregation Outputs > > >

KTable.count(...)

Hi, I'm slightly confused by KTable.count(..). The javadoc says: Count number of records of this stream by the selected key into a new instance of {@link KTable}. So.. if i send 5 records with the same key to the input topic, as per below final KafkaProducer producer = new

[jira] [Assigned] (KAFKA-3429) Remove Serdes needed for repartitioning in KTable stateful operations

[ https://issues.apache.org/jira/browse/KAFKA-3429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax reassigned KAFKA-3429: -- Assignee: Matthias J. Sax > Remove Serdes needed for repartitioning in KTable stateful

[jira] [Updated] (KAFKA-3574) Add missing @returns tags for JavaDoc

[ https://issues.apache.org/jira/browse/KAFKA-3574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-3574: --- Issue Type: Sub-task (was: Improvement) Parent: KAFKA-2590 > Add missing @returns

[jira] [Created] (KAFKA-3574) Add missing @returns tags for JavaDoc

Matthias J. Sax created KAFKA-3574: -- Summary: Add missing @returns tags for JavaDoc Key: KAFKA-3574 URL: https://issues.apache.org/jira/browse/KAFKA-3574 Project: Kafka Issue Type:

Re: kafka streaming: passing config string to Processor

KafkaStreams works quite different than other systems like Flink/Storm. It is not a system but a library. If you start a KafkaStreams application, it runs locally. Scaling/Parallelism comes into place if you start the same application on multiple nodes. For this, Kafka's parallelization model is

[GitHub] kafka pull request: KAFKA-3337: [WIP] Extract selector as a separa...

GitHub user mjsax opened a pull request: https://github.com/apache/kafka/pull/1231 KAFKA-3337: [WIP] Extract selector as a separate groupBy operator for KTable aggregations You can merge this pull request into a Git repository by running: $ git pull

[jira] [Commented] (KAFKA-3337) Extract selector as a separate groupBy operator for KTable aggregations

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

[jira] [Created] (KAFKA-3573) JSON (de)serialization for kafka-client

Igor Stepanov created KAFKA-3573: Summary: JSON (de)serialization for kafka-client Key: KAFKA-3573 URL: https://issues.apache.org/jira/browse/KAFKA-3573 Project: Kafka Issue Type: New

Re: kafka streaming: passing config string to Processor

Ok... Is it really perform distribution of the field to several instances of a cluster? I expected to see some way via ProcessorContext... But may be this is result of the Flink's experience... Thanks 2016-04-17 12:38 GMT+02:00 Matthias J. Sax : > I guess the simplest way

Re: kafka streaming: passing config string to Processor

I guess the simplest way would be to use a constructor parameter: > public static class CampaignProcessor implements > ProcessorSupplier> > { > private final String jedis_server; > > public CampaignProcessor(String jedisServer) { >

[jira] [Updated] (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 ] Liquan Pei updated KAFKA-3421: -- Status: Patch Available (was: In Progress) > Update docs with new connector features >

[jira] [Created] (KAFKA-3572) Metrics of topics still exist when they have been deleted

Eric Huang created KAFKA-3572: - Summary: Metrics of topics still exist when they have been deleted Key: KAFKA-3572 URL: https://issues.apache.org/jira/browse/KAFKA-3572 Project: Kafka Issue

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

See Changes: [wangguoz] KAFKA-3430: Allow users to set key in KTable.toStream and in KStream. -- [...truncated 2485 lines...] kafka.api.ProducerFailureHandlingTest > testNotEnoughReplicas