[jira] [Updated] (KAFKA-4822) Kafka producer implementation without additional threads and control of when data is sent to kafka (similar to sync producer of 0.8.)

[ https://issues.apache.org/jira/browse/KAFKA-4822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giri updated KAFKA-4822: Summary: Kafka producer implementation without additional threads and control of when data is sent to kafka

[jira] [Updated] (KAFKA-4822) Kafka producer implementation without additional threads and control of when data is sent to kafka, similar to sync producer of 0.8.

[ https://issues.apache.org/jira/browse/KAFKA-4822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giri updated KAFKA-4822: Summary: Kafka producer implementation without additional threads and control of when data is sent to kafka,

[jira] [Commented] (KAFKA-4092) retention.bytes should not be allowed to be less than segment.bytes

[ https://issues.apache.org/jira/browse/KAFKA-4092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15891667#comment-15891667 ] Ewen Cheslack-Postava commented on KAFKA-4092: -- [~ijuma] Since this is still marked for a

Re: [DISCUSS] KIP-128: Add ByteArrayConverter for Kafka Connect

Yeah, you are right, it is best not to make converters actively break the data structures :) On Wed, Mar 1, 2017 at 4:55 PM, Ewen Cheslack-Postava wrote: > Guozhang, > > I'm fine w/ adjusting if people want to, but it ends up being more code > since we also need to convert

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

See Changes: [wangguoz] KAFKA-4677 Follow Up: add optimization to StickyTaskAssignor for rolling [wangguoz] MINOR: improve MinTimestampTrackerTest and fix NPE when null element

Re: [VOTE] KIP-119: Drop Support for Scala 2.10 in Kafka 0.11

+1 On Tue, Feb 28, 2017 at 2:40 AM, Ismael Juma wrote: > Hi everyone, > > Since the few who responded in the discuss thread were in favour and there > were no objections, I would like to initiate the voting process for > KIP-119: Drop Support for Scala 2.10 in Kafka 0.11: > >

Re: [VOTE] KIP-119: Drop Support for Scala 2.10 in Kafka 0.11

Hi Becket, I think there's a misunderstanding. Scala 2.11 has been the recommended version since Kafka 0.9.0.0 as you can see in the downloads page: https://kafka.apache.org/downloads Scala 2.10 is the default build version for the same reason that we recommend people to build with Java 7 when

Re: [DISCUSS] KIP-117: Add a public AdministrativeClient API for Kafka admin operations

On Wed, Mar 1, 2017, at 15:52, radai wrote: > quick comment on the request objects: > > i see "abstract class NewTopic" and "class NewTopicWithReplication" and " > NewTopicWithReplicaAssignments" > > 1. since the result object is called CreateTopicResults should these be > called *Request? Hi

Re: [VOTE] KIP-107: Add purgeDataBefore() API in AdminClient

Thanks for the update. The changes sound reasonable. On Wed, Mar 1, 2017 at 1:57 PM, Dong Lin wrote: > Hi all, > > I have updated the KIP to include a script that allows user to purge data > by providing a map from partition to offset. I think this script may be >

Re: [VOTE] KIP-119: Drop Support for Scala 2.10 in Kafka 0.11

Hey Ismael, Sorry for being late on this KIP. At LinkedIn we are still in the progress or migrating from Scala 2.10 to 2.11. I am not sure how many other existing Kafka users are still on Scala 2.10. But given that until now the default Scala version is still 2.10.6, I feel it is a little too

[jira] [Comment Edited] (KAFKA-4396) Seeing offsets not resetting even when reset policy is configured explicitly

[ https://issues.apache.org/jira/browse/KAFKA-4396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15891428#comment-15891428 ] Helena Edelson edited comment on KAFKA-4396 at 3/2/17 1:39 AM: --- I ran into

[jira] [Commented] (KAFKA-4396) Seeing offsets not resetting even when reset policy is configured explicitly

[ https://issues.apache.org/jira/browse/KAFKA-4396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15891428#comment-15891428 ] Helena Edelson commented on KAFKA-4396: --- I ran into this as well. Re-deploying with a new consumer

Re: [DISCUSS] KIP-128: Add ByteArrayConverter for Kafka Connect

Guozhang, I'm fine w/ adjusting if people want to, but it ends up being more code since we also need to convert SerializationExceptions to DataExceptions and the only thing the toConnectData method even does is specific to Connect (adding the SchemaAndValue). Gwen -- isn't that an SMT?

Re: [DISCUSS] 0.10.3.0/0.11.0.0 release planning

+1 Thanks Ismael for volunteering to run the next time based release. On Wed, Mar 1, 2017 at 4:51 PM, Ismael Juma wrote: > Thanks everyone for the feedback. Since everyone was in favour and we had > covered this particular case in the time-based release plan[1], I went >

Re: [DISCUSS] 0.10.3.0/0.11.0.0 release planning

Thanks everyone for the feedback. Since everyone was in favour and we had covered this particular case in the time-based release plan[1], I went ahead and updated the wiki page to specify the next version as 0.11.0.0. I'll update JIRA versions and the KIP page soon. Ismael [1] "We change the

Re: [VOTE] KIP-119: Drop Support for Scala 2.10 in Kafka 0.11

+1 (non-binding) On Wed, Mar 1, 2017 at 4:41 PM, Ewen Cheslack-Postava wrote: > +1 (binding) > > -Ewen > > On Wed, Mar 1, 2017 at 4:56 AM, Jozef.koval > wrote: > > > +1 (non-binding) > > > > Jozef > > > > P.S. I volunteer to help with this KIP. > >

Re: [VOTE] KIP-119: Drop Support for Scala 2.10 in Kafka 0.11

+1 (binding) -Ewen On Wed, Mar 1, 2017 at 4:56 AM, Jozef.koval wrote: > +1 (non-binding) > > Jozef > > P.S. I volunteer to help with this KIP. > > > Sent from [ProtonMail](https://protonmail.ch), encrypted email based in > Switzerland. > > > > Original

[jira] [Commented] (KAFKA-2729) Cached zkVersion not equal to that in zookeeper, broker not recovering.

[ https://issues.apache.org/jira/browse/KAFKA-2729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15891355#comment-15891355 ] mjuarez commented on KAFKA-2729: We are also running into this problem in our staging cluster, running

Re: [DISCUSS] KIP-117: Add a public AdministrativeClient API for Kafka admin operations

quick comment on the request objects: i see "abstract class NewTopic" and "class NewTopicWithReplication" and " NewTopicWithReplicaAssignments" 1. since the result object is called CreateTopicResults should these be called *Request? 2. this seems like a suboptimal approach to me. imagine we add

Re: [DISCUSS] KIP 130: Expose states of active tasks to KafkaStreams public API

Hi Matthias, First, I will answer to your last question. The main reason to have both TaskState#assignment and TaskState#consumedOffsetsByPartition is that tasks have no consumed offsets until at least one message is consumed for each partition even if previous offsets exist for the consumer

[GitHub] kafka pull request #2603: MINOR: Minor reduce unnecessary calls to time.mill...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2603 --- 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: [DISCUSS] KIP-124: Request rate quotas

That makes sense. I didn't see that this field already existed in some of the replies-- good clarification. best, On Wed, Mar 1, 2017, at 05:41, Rajini Sivaram wrote: > Colin, > > Thank you for the feedback. Since we are reusing the existing > throttle_time_ms field for produce/fetch

[jira] [Commented] (KAFKA-4828) ProcessorTopologyTestDriver does not work when using .through()

[ https://issues.apache.org/jira/browse/KAFKA-4828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15891151#comment-15891151 ] Matthias J. Sax commented on KAFKA-4828: I am not sure if the JIRA title and error message

Re: [DISCUSS] KIP-112: Handle disk failure for JBOD

Hey Jun, Do you think it is OK to keep the existing wire protocol in the KIP? I am wondering if we can initiate vote for this KIP. Thanks, Dong On Tue, Feb 28, 2017 at 2:41 PM, Dong Lin wrote: > Hey Jun, > > I just realized that StopReplicaRequest itself doesn't specify

Re: [DISCUSS] KIP-117: Add a public AdministrativeClient API for Kafka admin operations

Hi all, Thanks for commenting, everyone. Does anyone have more questions or comments, or should we vote? The latest proposal is up at https://cwiki.apache.org/confluence/display/KAFKA/KIP-117%3A+Add+a+public+AdminClient+API+for+Kafka+admin+operations best, Colin On Thu, Feb 16, 2017, at

Re: [DISCUSS] KIP-128: Add ByteArrayConverter for Kafka Connect

Hi Ewen, Thanks for the KIP, I think it will be useful :) I'm just wondering if we can add support not just for bytes schema, but also for a struct that contains bytes? I'm thinking of the scenario of using a connector to grab BLOBs out of a DB - I think you end up with this structure if you use

Re: [VOTE] KIP-107: Add purgeDataBefore() API in AdminClient

Hi all, I have updated the KIP to include a script that allows user to purge data by providing a map from partition to offset. I think this script may be convenience and useful, e.g., if user simply wants to purge all data of given partitions from command line. I am wondering if anyone object

Re: [DISCUSS] KIP 130: Expose states of active tasks to KafkaStreams public API

Thanks for the KIP. I am wondering a little bit, why you need to expose this information. Can you describe some use cases? Would it be worth to unify this new API with KafkaStreams#state() to get the overall state of an application without the need to call two different methods? Not sure how

[jira] [Commented] (KAFKA-4706) Unify StreamsKafkaClient instances

[ https://issues.apache.org/jira/browse/KAFKA-4706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15891048#comment-15891048 ] Matthias J. Sax commented on KAFKA-4706: Yes. > Unify StreamsKafkaClient instances >

[jira] [Commented] (KAFKA-4677) Avoid unnecessary task movement across threads during rebalance

[ https://issues.apache.org/jira/browse/KAFKA-4677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15891031#comment-15891031 ] Matthias J. Sax commented on KAFKA-4677: Streams used it's own partition assigner implementation

Re: [DISCUSS] KIP-82 - Add Record Headers

Hi Ismael, Thanks for the reply. Please see the comments inline. On Wed, Mar 1, 2017 at 6:47 AM, Ismael Juma wrote: > Hi Becket, > > Thanks for sharing your thoughts. More inline. > > On Wed, Mar 1, 2017 at 2:54 AM, Becket Qin wrote: > > > As you can

[GitHub] kafka pull request #2625: KAFKA:4623- Change default unclean.leader.election...

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

[jira] [Issue Comment Deleted] (KAFKA-4623) Change Default unclean.leader.election.enabled from True to False

[ https://issues.apache.org/jira/browse/KAFKA-4623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sharad updated KAFKA-4623: -- Comment: was deleted (was: https://github.com/apache/kafka/pull/2470) > Change Default

[jira] [Commented] (KAFKA-4623) Change Default unclean.leader.election.enabled from True to False

[ https://issues.apache.org/jira/browse/KAFKA-4623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15891025#comment-15891025 ] Sharad commented on KAFKA-4623: --- Rebased. PR submitted: https://github.com/apache/kafka/pull/2625 > Change

[jira] [Commented] (KAFKA-4706) Unify StreamsKafkaClient instances

[ https://issues.apache.org/jira/browse/KAFKA-4706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15890965#comment-15890965 ] Sharad commented on KAFKA-4706: --- [~mjsax] Need a bit of review of the solution. Is it ok if I use

[GitHub] kafka pull request #2611: MINOR: improve MinTimestampTrackerTest and fix NPE...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2611 --- 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-4677) Avoid unnecessary task movement across threads during rebalance

[ https://issues.apache.org/jira/browse/KAFKA-4677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15890935#comment-15890935 ] Jeff Widman commented on KAFKA-4677: Is KIP-54 related since it also implements a sticky partition

[jira] [Created] (KAFKA-4831) Extract WindowedSerde to public APIs

Guozhang Wang created KAFKA-4831: Summary: Extract WindowedSerde to public APIs Key: KAFKA-4831 URL: https://issues.apache.org/jira/browse/KAFKA-4831 Project: Kafka Issue Type: Bug

[GitHub] kafka pull request #2625: KAFKA:4623- Change default unclean.leader.election...

GitHub user sharad-develop opened a pull request: https://github.com/apache/kafka/pull/2625 KAFKA:4623- Change default unclean.leader.election.enabled from True to False KAFKA:4623- Change default unclean.leader.election.enabled from True to False You can merge this pull request

[jira] [Created] (KAFKA-4830) Augment KStream.print() to allow users pass in extra parameters in the printed string

Guozhang Wang created KAFKA-4830: Summary: Augment KStream.print() to allow users pass in extra parameters in the printed string Key: KAFKA-4830 URL: https://issues.apache.org/jira/browse/KAFKA-4830

[jira] [Commented] (KAFKA-4829) Improve logging of StreamTask commits

[ https://issues.apache.org/jira/browse/KAFKA-4829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15890917#comment-15890917 ] Guozhang Wang commented on KAFKA-4829: -- I'd like to expand the scope of this JIRA a bit to make a

Re: groupBy without auto-repartition topics for Kafka Streams

It should be: groupBy -> always trigger repartitioning groupByKey -> maybe trigger repartitioning And there will not be two repartitioning topics. The repartitioning will be done by the groupBy/groupByKey operation, and thus, in the aggregation step we know that data is correctly partitioned and

[jira] [Updated] (KAFKA-4829) Improve logging of StreamTask commits

[ https://issues.apache.org/jira/browse/KAFKA-4829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-4829: - Labels: user-experience (was: ) > Improve logging of StreamTask commits >

[jira] [Updated] (KAFKA-4829) Improve logging of StreamTask commits

[ https://issues.apache.org/jira/browse/KAFKA-4829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steven Schlansker updated KAFKA-4829: - Description: Currently I see this every commit interval: {code} 2017-02-28T21:27:16.659Z

[jira] [Created] (KAFKA-4829) Improve logging of StreamTask commits

Steven Schlansker created KAFKA-4829: Summary: Improve logging of StreamTask commits Key: KAFKA-4829 URL: https://issues.apache.org/jira/browse/KAFKA-4829 Project: Kafka Issue Type:

[jira] [Updated] (KAFKA-4829) Improve logging of StreamTask commits

[ https://issues.apache.org/jira/browse/KAFKA-4829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steven Schlansker updated KAFKA-4829: - Description: Currently I see this every commit interval: {code} 2017-02-28T21:27:16.659Z

Re: groupBy without auto-repartition topics for Kafka Streams

FYI: The difference between `groupBy` (may trigger re-partitioning) vs. `groupByKey` (does not trigger re-partitioning) also applies to: - `map` vs. `mapValues` - `flatMap` vs. `flatMapValues` On Wed, Mar 1, 2017 at 8:15 PM, Damian Guy wrote: > If you use

[jira] [Commented] (KAFKA-4677) Avoid unnecessary task movement across threads during rebalance

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

[GitHub] kafka pull request #2609: KAFKA-4677: [Follow Up] add optimization to Sticky...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2609 --- 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-4743) Add a tool to Reset Consumer Group Offsets

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

[GitHub] kafka pull request #2624: KAFKA-4743: Add Reset Consumer Group Offsets tooli...

GitHub user jeqo opened a pull request: https://github.com/apache/kafka/pull/2624 KAFKA-4743: Add Reset Consumer Group Offsets tooling [KIP-122] You can merge this pull request into a Git repository by running: $ git pull https://github.com/jeqo/kafka

[jira] [Updated] (KAFKA-4743) Add a tool to Reset Consumer Group Offsets

[ https://issues.apache.org/jira/browse/KAFKA-4743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jorge Quilcate updated KAFKA-4743: -- Description: Add an external tool to reset Consumer Group offsets, and achieve rewind over the

Re: groupBy without auto-repartition topics for Kafka Streams

If you use stream.groupByKey() then there will be no repartitioning as long as there have been no key changing operations preceding it, i.e, map, selectKey, flatMap, transform. If you use stream.groupBy(...) then we see it as a key changing operation, hence we need to repartition the data. On

groupBy without auto-repartition topics for Kafka Streams

Hi there, I wonder if it makes sense to give the option to disable auto repartitioning while doing groupBy. I understand with https://issues.apache.org/jira/browse/KAFKA-3561, an internal topic for repartition will be automatically created and synced to brokers, which is useful when aggregation

Re: [DISCUSS] KIP-82 - Add Record Headers

@michael: i used void because im used to java beans. thinking about it, i dont see much use for returning false from adding a header: if the headers are in read-only you should probably thrown an IllegalStateException because lets face it, 99% of users dont check return values. returning "this"

[jira] [Created] (KAFKA-4828) ProcessorTopologyTestDriver does not work when using .through()

Hamidreza Afzali created KAFKA-4828: --- Summary: ProcessorTopologyTestDriver does not work when using .through() Key: KAFKA-4828 URL: https://issues.apache.org/jira/browse/KAFKA-4828 Project: Kafka

[jira] [Updated] (KAFKA-4827) Kafka connect: Escape special characters in connector name

[ https://issues.apache.org/jira/browse/KAFKA-4827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aymeric Bouvet updated KAFKA-4827: -- Description: When creating a connector, if the connector name (and possibly other properties)

[jira] [Updated] (KAFKA-4827) Kafka connect: error with special characters in connector name

[ https://issues.apache.org/jira/browse/KAFKA-4827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aymeric Bouvet updated KAFKA-4827: -- Summary: Kafka connect: error with special characters in connector name (was: Kafka connect:

[jira] [Updated] (KAFKA-4826) Fix some findbugs warnings in Kafka Streams

[ https://issues.apache.org/jira/browse/KAFKA-4826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-4826: --- Component/s: streams > Fix some findbugs warnings in Kafka Streams >

[jira] [Created] (KAFKA-4827) Kafka connect: Escape special characters in connector name

Aymeric Bouvet created KAFKA-4827: - Summary: Kafka connect: Escape special characters in connector name Key: KAFKA-4827 URL: https://issues.apache.org/jira/browse/KAFKA-4827 Project: Kafka

[jira] [Commented] (KAFKA-3686) Kafka producer is not fault tolerant

[ https://issues.apache.org/jira/browse/KAFKA-3686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15890746#comment-15890746 ] Xu Zhang commented on KAFKA-3686: - Any update there? I think we have the same issue. > Kafka producer is

[jira] [Commented] (KAFKA-4826) Fix some findbugs warnings in Kafka Streams

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

[GitHub] kafka pull request #2623: KAFKA-4826. Fix some findbugs warnings in Kafka St...

GitHub user cmccabe opened a pull request: https://github.com/apache/kafka/pull/2623 KAFKA-4826. Fix some findbugs warnings in Kafka Streams You can merge this pull request into a Git repository by running: $ git pull https://github.com/cmccabe/kafka KAFKA-4826 Alternatively

[jira] [Created] (KAFKA-4826) Fix some findbugs warnings in Kafka Streams

Colin P. McCabe created KAFKA-4826: -- Summary: Fix some findbugs warnings in Kafka Streams Key: KAFKA-4826 URL: https://issues.apache.org/jira/browse/KAFKA-4826 Project: Kafka Issue Type:

[jira] [Commented] (KAFKA-4823) Creating Kafka Producer on application running on Java 1.6

[ https://issues.apache.org/jira/browse/KAFKA-4823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15890699#comment-15890699 ] Aneesh commented on KAFKA-4823: --- [~ijuma] Kafka 0.8.2.0 worked for me.I did go through REST proxy , but

[jira] [Commented] (KAFKA-4825) Likely Data Loss in ReassignPartitionsTest System Test

[ https://issues.apache.org/jira/browse/KAFKA-4825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15890661#comment-15890661 ] Ben Stopford commented on KAFKA-4825: - This could be a result of KIP-101

[jira] [Updated] (KAFKA-4823) Creating Kafka Producer on application running on Java 1.6

[ https://issues.apache.org/jira/browse/KAFKA-4823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-4823: - Component/s: (was: KafkaConnect) > Creating Kafka Producer on application

Re: [VOTE] KIP-107: Add purgeDataBefore() API in AdminClient

Hi Ismael, I actually mean log_start_offset. I realized that it is a better name after I start implementation because "logStartOffset" is already used in Log.scala and LogCleanerManager.scala. So I changed it from log_begin_offset to log_start_offset in the patch. But I forgot to update the KIP

[jira] [Created] (KAFKA-4825) Likely Data Loss in ReassignPartitionsTest System Test

Ben Stopford created KAFKA-4825: --- Summary: Likely Data Loss in ReassignPartitionsTest System Test Key: KAFKA-4825 URL: https://issues.apache.org/jira/browse/KAFKA-4825 Project: Kafka Issue

[jira] [Commented] (KAFKA-4092) retention.bytes should not be allowed to be less than segment.bytes

[ https://issues.apache.org/jira/browse/KAFKA-4092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15890540#comment-15890540 ] Andrew Olson commented on KAFKA-4092: - Note that this Jira is being reverted in 0.10.2.1 (see

[jira] [Commented] (KAFKA-4823) Creating Kafka Producer on application running on Java 1.6

[ https://issues.apache.org/jira/browse/KAFKA-4823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15890422#comment-15890422 ] Aneesh commented on KAFKA-4823: --- [~bernie huang] I use JDK1.6 to compile my app jar,still it fails >

[jira] [Resolved] (KAFKA-4824) add unique identifier to clientId

[ https://issues.apache.org/jira/browse/KAFKA-4824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clemens Valiente resolved KAFKA-4824. - Resolution: Duplicate > add unique identifier to clientId >

[jira] [Closed] (KAFKA-4824) add unique identifier to clientId

[ https://issues.apache.org/jira/browse/KAFKA-4824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clemens Valiente closed KAFKA-4824. --- > add unique identifier to clientId > - > > Key:

[jira] [Commented] (KAFKA-4824) add unique identifier to clientId

[ https://issues.apache.org/jira/browse/KAFKA-4824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15890387#comment-15890387 ] Clemens Valiente commented on KAFKA-4824: - duplicate of KAFKA-4117 > add unique identifier to

[jira] [Assigned] (KAFKA-4824) add unique identifier to clientId

[ https://issues.apache.org/jira/browse/KAFKA-4824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clemens Valiente reassigned KAFKA-4824: --- Assignee: Clemens Valiente > add unique identifier to clientId >

[jira] [Created] (KAFKA-4824) add unique identifier to clientId

Clemens Valiente created KAFKA-4824: --- Summary: add unique identifier to clientId Key: KAFKA-4824 URL: https://issues.apache.org/jira/browse/KAFKA-4824 Project: Kafka Issue Type:

[jira] [Commented] (KAFKA-4823) Creating Kafka Producer on application running on Java 1.6

[ https://issues.apache.org/jira/browse/KAFKA-4823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15890350#comment-15890350 ] Aneesh commented on KAFKA-4823: --- [~bernie huang] if I use jdk 1.7 to package my jar file, this application

Re: [DISCUSS] KIP-82 - Add Record Headers

Hi Becket, Thanks for sharing your thoughts. More inline. On Wed, Mar 1, 2017 at 2:54 AM, Becket Qin wrote: > As you can imagine if the ProducerRecord has a value as a List and the > Interceptor.onSend() can actually add an element to the List. If the > producer.send() is

[jira] [Commented] (KAFKA-4823) Creating Kafka Producer on application running on Java 1.6

[ https://issues.apache.org/jira/browse/KAFKA-4823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15890242#comment-15890242 ] bernie huang commented on KAFKA-4823: - Do you use jdk1.7 package your application jar file,and use

Re: [VOTE] KIP-107: Add purgeDataBefore() API in AdminClient

Hi Dong, When you say "logStartOffset", do you mean "log_begin_offset "? I could only find the latter in the KIP. If so, would log_start_offset be a better name? Ismael On Tue, Feb 28, 2017 at 4:26 AM, Dong Lin wrote: > Hi Jun and everyone, > > I would like to change the

[jira] [Commented] (KAFKA-4631) Refresh consumer metadata more frequently for unknown subscribed topics

[ https://issues.apache.org/jira/browse/KAFKA-4631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15890234#comment-15890234 ] Rajini Sivaram commented on KAFKA-4631: --- The attached PR solves the issue in the second failure in

Re: [VOTE] KIP-123: Allow per stream/table timestamp extractor

+1 (non-binding) Thanks for the KIP! On Wed, Mar 1, 2017 at 1:49 PM, Bill Bejeck wrote: > +1 > > Thanks > Bill > > On Wed, Mar 1, 2017 at 5:06 AM, Eno Thereska > wrote: > > > +1 (non binding). > > > > Thanks > > Eno > > > On 28 Feb 2017, at 17:22,

[jira] [Commented] (KAFKA-4631) Refresh consumer metadata more frequently for unknown subscribed topics

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

[GitHub] kafka pull request #2622: KAFKA-4631: Request metadata in consumer if topic/...

GitHub user rajinisivaram opened a pull request: https://github.com/apache/kafka/pull/2622 KAFKA-4631: Request metadata in consumer if topic/partitions unavailable If leader node of one more more partitions in a consumer subscription are temporarily unavailable, request metadata

[jira] [Commented] (KAFKA-4779) Failure in kafka/tests/kafkatest/tests/core/security_rolling_upgrade_test.py

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

[GitHub] kafka pull request #2608: KAFKA-4779: Request metadata in consumer if partit...

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

Re: [DISCUSS] KIP-124: Request rate quotas

Colin, Thank you for the feedback. Since we are reusing the existing throttle_time_ms field for produce/fetch responses, changing this to microseconds would be a breaking change. Since we don't currently plan to throttle at sub-millisecond intervals, perhaps it makes sense to keep the value

[jira] [Commented] (KAFKA-4822) Kafka producer implementation without additional threads, similar to sync producer of 0.8.

[ https://issues.apache.org/jira/browse/KAFKA-4822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15890172#comment-15890172 ] Ismael Juma commented on KAFKA-4822: The data is sent as soon as possible by default (linger.ms=0), so

[jira] [Comment Edited] (KAFKA-4822) Kafka producer implementation without additional threads, similar to sync producer of 0.8.

[ https://issues.apache.org/jira/browse/KAFKA-4822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15890172#comment-15890172 ] Ismael Juma edited comment on KAFKA-4822 at 3/1/17 1:38 PM: The data is sent

Re: [DISCUSS] KIP 130: Expose states of active tasks to KafkaStreams public API

Hi Eno, Yes, but the state() method only returns the global state of the KafkaStream application (ie: CREATED, RUNNING, REBALANCING, PENDING_SHUTDOWN, NOT_RUNNING). An alternative to this KIP would be to change this method to return more information instead of adding a new method. 2017-03-01

[jira] [Commented] (KAFKA-4822) Kafka producer implementation without additional threads, similar to sync producer of 0.8.

[ https://issues.apache.org/jira/browse/KAFKA-4822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15890139#comment-15890139 ] Giri commented on KAFKA-4822: - A producer implementation with finer control will be helpful in the above like

[jira] [Commented] (KAFKA-4822) Kafka producer implementation without additional threads, similar to sync producer of 0.8.

[ https://issues.apache.org/jira/browse/KAFKA-4822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15890130#comment-15890130 ] Giri commented on KAFKA-4822: - i understand that the sync can be achieved by the above workaround, but still

Re: [VOTE] KIP-119: Drop Support for Scala 2.10 in Kafka 0.11

+1 (non-binding) Jozef P.S. I volunteer to help with this KIP. Sent from [ProtonMail](https://protonmail.ch), encrypted email based in Switzerland. Original Message Subject: Re: [VOTE] KIP-119: Drop Support for Scala 2.10 in Kafka 0.11 Local Time: March 1, 2017 1:46 PM

Re: [VOTE] KIP-123: Allow per stream/table timestamp extractor

+1 Thanks Bill On Wed, Mar 1, 2017 at 5:06 AM, Eno Thereska wrote: > +1 (non binding). > > Thanks > Eno > > On 28 Feb 2017, at 17:22, Matthias J. Sax wrote: > > > > +1 > > > > Thanks a lot for the KIP! > > > > -Matthias > > > > > > On 2/28/17

Re: [DISCUSS] KIP 130: Expose states of active tasks to KafkaStreams public API

Thanks Florian, Have you had a chance to look at the new state methods in 0.10.2, e.g., KafkaStreams.state()? Thanks Eno > On 1 Mar 2017, at 11:54, Florian Hussonnois wrote: > > Hi all, > > I have just created KIP-130 to add a new method to the KafkaStreams API in >

Re: [VOTE] KIP-119: Drop Support for Scala 2.10 in Kafka 0.11

+1 Thanks, Bill On Wed, Mar 1, 2017 at 5:42 AM, Eno Thereska wrote: > +1, thanks. > > Eno > > On 28 Feb 2017, at 17:17, Guozhang Wang wrote: > > > > ＋1 > > > > On Tue, Feb 28, 2017 at 4:28 AM, Tom Crayford > wrote: > > > >> +1

Re: [DISCUSS] 0.10.3.0/0.11.0.0 release planning

+1 (non-binding) On Tue, Feb 28, 2017 at 6:56 PM, Apurva Mehta wrote: > +1 (non-binding) for 0.11.0 > > I do agree with Ismael's point that exactly-once should go through one > release of stabilization before bumping the version to 1.0. > > Thanks, > Apurva > > On Mon, Feb

[DISCUSS] KIP 130: Expose states of active tasks to KafkaStreams public API

Hi all, I have just created KIP-130 to add a new method to the KafkaStreams API in order to expose the states of threads and active tasks. https://cwiki.apache.org/confluence/display/KAFKA/KIP+130%3A+Expose+states+of+active+tasks+to+KafkaStreams+public+API Thanks, -- Florian HUSSONNOIS

[jira] [Commented] (KAFKA-4800) Streams State transition ASCII diagrams need fixing and polishing

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

[GitHub] kafka pull request #2621: KAFKA-4800: Streams State transition ASCII diagram...

GitHub user cvaliente opened a pull request: https://github.com/apache/kafka/pull/2621 KAFKA-4800: Streams State transition ASCII diagrams need fixing and polishing added tags to not break javadoc display of the ASCII diagrams. see broken ascii here:

  1   2   >