[jira] [Commented] (KAFKA-4595) Controller send thread can't stop when broker change listener event trigger for dead brokers

[ https://issues.apache.org/jira/browse/KAFKA-4595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15811007#comment-15811007 ] Pengwei commented on KAFKA-4595: One method is to add a lock timeout method instead of blo

Re: Problem generating documentation locally

The core:siteDocsTar target should generate them. -Ewen On Fri, Jan 6, 2017 at 4:26 PM, Vahid S Hashemian wrote: > I'm trying to build the project documentation locally, but I can't seem to > be able to populate content for files in the 'docs/generated/' folder. > I've tried some of the doc-rel

Re: [DISCUSS] KIP-104: Granular Sensors for Streams

Eno - I'm +1 on this change. Thanks, Damian On Sun, 8 Jan 2017 at 20:45 Eno Thereska wrote: > I can see the point that all of a sudden exposing the internal Metrics > class might be too big a bite to take in this KIP, since the Metrics class > might have to be cleaned up further. I was perhaps n

Re: [DISCUSS] KIP-104: Granular Sensors for Streams

Thanks Eno. It is indeed a good point about additional classes that users would have to be able to construct in order to add metrics to a sensor. We have generally assumed those classes to be internal and have queued one of them (SimpleRate) for removal (KAFKA-4178). They are simple for the most p

RE: KafkaConnect SinkTask::put

Hi Shikhar - many thanks - that works a treat :) -Original Message- From: Shikhar Bhushan [mailto:shik...@confluent.io] Sent: 06 January 2017 17:39 To: dev@kafka.apache.org Subject: Re: KafkaConnect SinkTask::put Sorry I forgot to specify, this needs to go into your Connect worker confi

Re: [VOTE] KIP-108: Create Topic Policy

Ismael, thanks for the KIP I see it as quite useful in a managed cloud environment. +1 (non-binding) -- Edoardo Comar IBM MessageHub eco...@uk.ibm.com IBM UK Ltd, Hursley Park, SO21 2JN IBM United Kingdom Limited Registered in England and Wales wi

[GitHub] kafka pull request #2215: KAFKA-3537: Expose metrics registry

Github user enothereska closed the pull request at: https://github.com/apache/kafka/pull/2215 --- 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-3537) Provide access to low-level Metrics in ProcessorContext

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

Re: [DISCUSS] KIP-104: Granular Sensors for Streams

Thanks Ismael, Damian, I have updated KIP to go with the conservative option. Eno > On 9 Jan 2017, at 09:44, Ismael Juma wrote: > > Thanks Eno. > > It is indeed a good point about additional classes that users would have to > be able to construct in order to add metrics to a sensor. We have gen

Re: [VOTE] KIP-105: Addition of Record Level for Sensors

+1 (non-binding) On Fri, Jan 6, 2017 at 6:12 PM, Matthias J. Sax wrote: > +1 > > On 1/6/17 9:09 AM, Neha Narkhede wrote: > > +1 > > > > On Fri, Jan 6, 2017 at 9:04 AM Sriram Subramanian > wrote: > > > >> +1 > >> > >> On Fri, Jan 6, 2017 at 8:40 AM, Bill Bejeck wrote: > >> > >>> +1 > >>> > >>>

[jira] [Assigned] (KAFKA-4588) QueryableStateIntegrationTest.shouldNotMakeStoreAvailableUntilAllStoresAvailable is occasionally failing on jenkins

[ https://issues.apache.org/jira/browse/KAFKA-4588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy reassigned KAFKA-4588: - Assignee: Damian Guy > QueryableStateIntegrationTest.shouldNotMakeStoreAvailableUntilAllStoresAva

[GitHub] kafka pull request #2334: subset of KAFKA-4353: Add uuid

GitHub user rnpridgeon opened a pull request: https://github.com/apache/kafka/pull/2334 subset of KAFKA-4353: Add uuid Alternatively I am open to using Avro's 'Fixed' type with a 16 byte size. However most requests I have seen received wish to see UUID represented as type String so

[jira] [Commented] (KAFKA-4353) Add semantic types to Kafka Connect

[ https://issues.apache.org/jira/browse/KAFKA-4353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15811608#comment-15811608 ] ASF GitHub Bot commented on KAFKA-4353: --- GitHub user rnpridgeon opened a pull reques

[GitHub] kafka pull request #2335: TRIVIAL: Fix spelling of log message

GitHub user reftel opened a pull request: https://github.com/apache/kafka/pull/2335 TRIVIAL: Fix spelling of log message You can merge this pull request into a Git repository by running: $ git pull https://github.com/reftel/kafka feature/triggering Alternatively you can revie

[jira] [Commented] (KAFKA-4556) unordered messages when multiple topics are combined in single topic through stream

[ https://issues.apache.org/jira/browse/KAFKA-4556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15811854#comment-15811854 ] Savdeep Singh commented on KAFKA-4556: -- [~ewencp] Thanks for the response, please fin

[jira] [Updated] (KAFKA-4556) unordered messages when multiple topics are combined in single topic through stream

[ https://issues.apache.org/jira/browse/KAFKA-4556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Savdeep Singh updated KAFKA-4556: - Attachment: stream topology.png Stream topology example > unordered messages when multiple topics

[jira] [Created] (KAFKA-4609) KTable/KTable join followed by groupBy and aggregate/count can result in incorrect results

Damian Guy created KAFKA-4609: - Summary: KTable/KTable join followed by groupBy and aggregate/count can result in incorrect results Key: KAFKA-4609 URL: https://issues.apache.org/jira/browse/KAFKA-4609 Pr

[jira] [Created] (KAFKA-4610) getting error:Batch containing 3 record(s) expired due to timeout while requesting metadata from brokers for test2R2P2-1

sandeep kumar singh created KAFKA-4610: -- Summary: getting error:Batch containing 3 record(s) expired due to timeout while requesting metadata from brokers for test2R2P2-1 Key: KAFKA-4610 URL: https://issues.a

[VOTE] KIP-109: Old Consumer Deprecation

Happy Monday, I'd like to thank everyone who participated in the discussion around this KIP and shared their opinion. The only concern that was raised was not having a defined migration plan yet for existing users of the old consumer. I hope that responses to this concern (on the discussion thr

[jira] [Updated] (KAFKA-3745) Consider adding join key to ValueJoiner interface

[ https://issues.apache.org/jira/browse/KAFKA-3745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-3745: --- Labels: api needs-kip newbie (was: api newbie) > Consider adding join key to ValueJoiner inte

[jira] [Commented] (KAFKA-3745) Consider adding join key to ValueJoiner interface

[ https://issues.apache.org/jira/browse/KAFKA-3745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15812244#comment-15812244 ] Matthias J. Sax commented on KAFKA-3745: [~sree2k] thanks for picking this up. Jus

[jira] [Comment Edited] (KAFKA-3745) Consider adding join key to ValueJoiner interface

[ https://issues.apache.org/jira/browse/KAFKA-3745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15812244#comment-15812244 ] Matthias J. Sax edited comment on KAFKA-3745 at 1/9/17 5:01 PM:

[jira] [Commented] (KAFKA-4455) CommitFailedException during rebalance doesn't release resources in tasks/processors

[ https://issues.apache.org/jira/browse/KAFKA-4455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15812326#comment-15812326 ] Davor Poldrugo commented on KAFKA-4455: --- This should be resolved by KAFKA-4561, so t

[jira] [Commented] (KAFKA-4441) Kafka Monitoring is incorrect during rapid topic creation and deletion

[ https://issues.apache.org/jira/browse/KAFKA-4441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15812411#comment-15812411 ] Edoardo Comar commented on KAFKA-4441: -- Please ignore the previous comment - the {{Un

Re: [DISCUSS] KIP-108: Create Topic Policy

This is great. Thanks, Ismael. One question. When TopicDetails are passed to the policy implementation, would the server defaults already have been merged? If not, I think the policy also needs access to the server defaults. Cheers, Roger On Fri, Jan 6, 2017 at 9:26 AM, Ismael Juma wrote:

Re: [VOTE] KIP-66: Single Message Transforms for Kafka Connect

Thanks all. The vote passed with +5 (binding). On Fri, Jan 6, 2017 at 11:37 AM Shikhar Bhushan wrote: That makes sense to me, I'll fold that into the PR and update the KIP if it gets committed in that form. On Fri, Jan 6, 2017 at 9:44 AM Jason Gustafson wrote: +1 One minor comment: would it m

[jira] [Commented] (KAFKA-4547) Consumer.position returns incorrect results for Kafka 0.10.1.0 client

[ https://issues.apache.org/jira/browse/KAFKA-4547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15812429#comment-15812429 ] Jason Gustafson commented on KAFKA-4547: [~vahid] Thanks for looking into this. Th

Re: [DISCUSS] KIP-104: Granular Sensors for Streams

One hopefully final update to the KIP to re-add two methods for generic sensor creation. Also the interface should have been marked unstable from the beginning, so did that now. Thanks, and please vote if you haven't done so. The above changes shouldn't trigger a re-vote since they are more con

out of the box security?

in light of things like this - https://www.bleepingcomputer.com/news/security/mongodb-apocalypse-is-here-as-ransom-attacks-hit-10-000-servers/ and given that plenty of people/orgs have public facing kafka installations that are wide open - https://www.shodan.io/search?query=kafka (yes, i realize t

Re: [DISCUSS] KIP-108: Create Topic Policy

Hi Roger, That's a good question. The server defaults are passed via the `configure` method of the `Configurable` interface that is implemented by `CreateTopicPolicy`. I'll mention this explicitly in the KIP. Ismael On Mon, Jan 9, 2017 at 6:04 PM, Roger Hoover wrote: > This is great. Thanks,

[jira] [Created] (KAFKA-4611) Support custom authentication mechanism

mahendiran chandrasekar created KAFKA-4611: -- Summary: Support custom authentication mechanism Key: KAFKA-4611 URL: https://issues.apache.org/jira/browse/KAFKA-4611 Project: Kafka Iss

[jira] [Updated] (KAFKA-4611) Support custom authentication mechanism

[ https://issues.apache.org/jira/browse/KAFKA-4611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] mahendiran chandrasekar updated KAFKA-4611: --- Description: Currently there are two login mechanisms supported by kafka clien

[jira] [Commented] (KAFKA-4547) Consumer.position returns incorrect results for Kafka 0.10.1.0 client

[ https://issues.apache.org/jira/browse/KAFKA-4547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15812544#comment-15812544 ] Vahid Hashemian commented on KAFKA-4547: [~hachikuji] Thanks for the feedback. Wha

[GitHub] kafka pull request #2319: KAFKA-4551: StreamsSmokeTest.test_streams intermit...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2319 --- 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-4551) StreamsSmokeTest.test_streams intermittent failure

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

[jira] [Commented] (KAFKA-4551) StreamsSmokeTest.test_streams intermittent failure

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

[jira] [Commented] (KAFKA-4125) Provide low-level Processor API meta data in DSL layer

[ https://issues.apache.org/jira/browse/KAFKA-4125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15812586#comment-15812586 ] Bill Bejeck commented on KAFKA-4125: Is this task still viable/desired? If so I'll pic

[GitHub] kafka pull request #2327: MINOR: Fix small error in javadoc for persistent S...

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

[jira] [Commented] (KAFKA-4547) Consumer.position returns incorrect results for Kafka 0.10.1.0 client

[ https://issues.apache.org/jira/browse/KAFKA-4547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15812595#comment-15812595 ] Jason Gustafson commented on KAFKA-4547: I was thinking in addition to your sugges

Re: [DISCUSS] KIP-104: Granular Sensors for Streams

Thanks Eno, a couple of follow-up comments: 1. About `sensor()` functions, could we rename them to `addSensor()` to be consistent with other APIs? Also do we want to still add the "String scopeName, String entityName, String operationName" parameters to enforce the naming hierarchy or just let use

[jira] [Comment Edited] (KAFKA-4547) Consumer.position returns incorrect results for Kafka 0.10.1.0 client

[ https://issues.apache.org/jira/browse/KAFKA-4547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15812595#comment-15812595 ] Jason Gustafson edited comment on KAFKA-4547 at 1/9/17 7:23 PM:

[jira] [Commented] (KAFKA-4547) Consumer.position returns incorrect results for Kafka 0.10.1.0 client

[ https://issues.apache.org/jira/browse/KAFKA-4547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15812615#comment-15812615 ] Vahid Hashemian commented on KAFKA-4547: Thanks for clarifying. I'll submit a PR a

[GitHub] kafka pull request #2336: MINOR: Fix small error in javadoc for persistent S...

GitHub user nixsticks opened a pull request: https://github.com/apache/kafka/pull/2336 MINOR: Fix small error in javadoc for persistent Stores Closed the last PR I made for this because I accidentally borked it with my other PR. Small error, I figure this is from copy-pasting the ab

Re: [DISCUSS] KIP-104: Granular Sensors for Streams

Sure, updated the KIP for both. Thanks Eno > On 9 Jan 2017, at 19:23, Guozhang Wang wrote: > > Thanks Eno, a couple of follow-up comments: > > 1. About `sensor()` functions, could we rename them to `addSensor()` to be > consistent with other APIs? Also do we want to still add the "String > sco

Re: [VOTE] KIP-104: Granular Sensors for Streams

Thanks for the KIP, +1 on the latest update. Ismael On Fri, Jan 6, 2017 at 9:37 AM, Eno Thereska wrote: > The discussion points for KIP-104 are addressed. At this point we'd like > to start the vote for it: > > https://cwiki.apache.org/confluence/display/KAFKA/KIP- > 104%3A+Granular+Sensors+for

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

See Changes: [wangguoz] KAFKA-4551: StreamsSmokeTest.test_streams intermittent failure -- [...truncated 7998 lines...] kafka.utils.timer.TimerTaskListTest > testAll STARTED kafka.utils.timer.T

Re: out of the box security?

Hi Radai, This is a good point. At Confluent, we discussed this briefly a while back, but we never got around to working out a concrete proposal. It would be great if someone were interested in working out the details in a KIP. Ismael On Mon, Jan 9, 2017 at 6:13 PM, radai wrote: > in light of

Re: [VOTE] KIP-104: Granular Sensors for Streams

+1, thanks. On Jan 9, 2017 12:27 PM, "Ismael Juma" wrote: Thanks for the KIP, +1 on the latest update. Ismael On Fri, Jan 6, 2017 at 9:37 AM, Eno Thereska wrote: > The discussion points for KIP-104 are addressed. At this point we'd like > to start the vote for it: > > https://cwiki.apache.or

[jira] [Commented] (KAFKA-4125) Provide low-level Processor API meta data in DSL layer

[ https://issues.apache.org/jira/browse/KAFKA-4125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15812918#comment-15812918 ] Matthias J. Sax commented on KAFKA-4125: I think we need a KIP for this -- we did

Re: [DISCUSS] KIP-108: Create Topic Policy

Got it. Thanks, Ismael. On Mon, Jan 9, 2017 at 10:42 AM, Ismael Juma wrote: > Hi Roger, > > That's a good question. The server defaults are passed via the `configure` > method of the `Configurable` interface that is implemented by > `CreateTopicPolicy`. I'll mention this explicitly in the KIP.

Re: [VOTE] KIP-108: Create Topic Policy

+1 (non-binding) On Mon, Jan 9, 2017 at 2:15 AM, Edoardo Comar wrote: > Ismael, > thanks for the KIP I see it as quite useful in a managed cloud > environment. > > +1 (non-binding) > -- > Edoardo Comar > IBM MessageHub > eco...@uk.ibm.com > IBM UK

Re: [VOTE] KIP-108: Create Topic Policy

+1 Thanks for the KIP - this is a very useful feature. Thanks, Joel On Mon, Jan 9, 2017 at 2:15 AM, Edoardo Comar wrote: > Ismael, > thanks for the KIP I see it as quite useful in a managed cloud > environment. > > +1 (non-binding) > -- > Edoard

Re: [VOTE] KIP-108: Create Topic Policy

+1 (non-binding) On Mon, Jan 9, 2017 at 1:49 PM, Joel Koshy wrote: > +1 > > Thanks for the KIP - this is a very useful feature. > > Thanks, > > Joel > > On Mon, Jan 9, 2017 at 2:15 AM, Edoardo Comar wrote: > > > Ismael, > > thanks for the KIP I see it as quite useful in a managed cloud > > envi

[jira] [Assigned] (KAFKA-4064) Add support for infinite endpoints for range queries in Kafka Streams KV stores

[ https://issues.apache.org/jira/browse/KAFKA-4064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xavier Léauté reassigned KAFKA-4064: Assignee: Xavier Léauté (was: Roger Hoover) > Add support for infinite endpoints for range

Re: [VOTE] KIP-103: Separation of Internal and External traffic

+1 On Fri, Jan 6, 2017 at 4:53 PM, Ismael Juma wrote: > Hi all, > > Since a few people (including myself) felt that listener name was clearer > than protocol label, I updated the KIP to use that (as mentioned in the > discuss thread). Given that this is a minor change, I don't think we need > to

Re: [DISCUSS] KIP-105: Addition of Record Level for Sensors

Didn't get a chance to review this earlier, but this LGTM. Minor comments: - The current name is fine, but I would have preferred calling it RecordingLevel to RecordLevel - first thing that comes to my mind with RecordLevel is Kafka records. - Under future work: it may be useful to allow specifying

Re: [VOTE] KIP-105: Addition of Record Level for Sensors

+1 (although I added a minor comment on the discussion thread) On Mon, Jan 9, 2017 at 3:43 AM, Michael Noll wrote: > +1 (non-binding) > > On Fri, Jan 6, 2017 at 6:12 PM, Matthias J. Sax > wrote: > > > +1 > > > > On 1/6/17 9:09 AM, Neha Narkhede wrote: > > > +1 > > > > > > On Fri, Jan 6, 2017 at

Re: [DISCUSS] KIP-110: Add Codec for ZStandard Compression

Thanks for posting the KIP, ZStandard looks like a nice improvement over the existing compression algorithms. A couple of questions: 1. Can you please elaborate on the details of the benchmark? 2. About https://github.com/luben/zstd-jni, can we rely on it? A few things to consider: are there other

[GitHub] kafka pull request #2337: MINOR: rework JavaDoc for windowing related public...

GitHub user mjsax opened a pull request: https://github.com/apache/kafka/pull/2337 MINOR: rework JavaDoc for windowing related public API - also some code refactoring and bug fixes You can merge this pull request into a Git repository by running: $ git pull https://github.com/

Re: [VOTE] KIP-108: Create Topic Policy

+1 - thanks for the proposal, I think it will be super useful for admins. On Sun, Jan 8, 2017 at 6:50 AM, Ismael Juma wrote: > Hi all, > > As the discussion seems to have settled down, I would like to initiate the > voting process for KIP-108: Create Topic Policy: > > https://cwiki.apache.org/con

Re: [DISCUSS] KIP-105: Addition of Record Level for Sensors

Thanks Joel, I'll address these tomorrow, no problem. Eno > On 9 Jan 2017, at 22:04, Joel Koshy wrote: > > Didn't get a chance to review this earlier, but this LGTM. Minor comments: > - The current name is fine, but I would have preferred calling it > RecordingLevel to RecordLevel - first thing

Re: [VOTE] KIP-108: Create Topic Policy

+1 - thanks Ismael! On Mon, Jan 9, 2017 at 2:30 PM Gwen Shapira wrote: > +1 - thanks for the proposal, I think it will be super useful for admins. > > On Sun, Jan 8, 2017 at 6:50 AM, Ismael Juma wrote: > > Hi all, > > > > As the discussion seems to have settled down, I would like to initiate >

Re: [DISCUSS] KIP-104: Granular Sensors for Streams

Thanks!! On Mon, Jan 9, 2017 at 12:18 PM, Eno Thereska wrote: > Sure, updated the KIP for both. > > Thanks > Eno > > On 9 Jan 2017, at 19:23, Guozhang Wang wrote: > > > > Thanks Eno, a couple of follow-up comments: > > > > 1. About `sensor()` functions, could we rename them to `addSensor()` to

[GitHub] kafka pull request #2332: MINOR: some public JavaDoc cleanup

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2332 --- 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-4125) Provide low-level Processor API meta data in DSL layer

[ https://issues.apache.org/jira/browse/KAFKA-4125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15813181#comment-15813181 ] Guozhang Wang commented on KAFKA-4125: -- [~bbejeck] Could you lead a KIP proposal / di

Re: [VOTE] KIP-108: Create Topic Policy

+1, that1 On Mon, Jan 9, 2017 at 2:47 PM, Neha Narkhede wrote: > +1 - thanks Ismael! > > On Mon, Jan 9, 2017 at 2:30 PM Gwen Shapira wrote: > > > +1 - thanks for the proposal, I think it will be super useful for admins. > > > > On Sun, Jan 8, 2017 at 6:50 AM, Ismael Juma wrote: > > > Hi all, >

Re: [VOTE] KIP-108: Create Topic Policy

(hit send too soon) +1 (non-binding).. that is a very well written KIP! On Mon, Jan 9, 2017 at 3:28 PM, Apurva Mehta wrote: > +1, that1 > > On Mon, Jan 9, 2017 at 2:47 PM, Neha Narkhede wrote: > >> +1 - thanks Ismael! >> >> On Mon, Jan 9, 2017 at 2:30 PM Gwen Shapira wrote: >> >> > +1 - thank

[jira] [Updated] (KAFKA-3209) Support single message transforms in Kafka Connect

[ https://issues.apache.org/jira/browse/KAFKA-3209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-3209: - Reviewer: Ewen Cheslack-Postava > Support single message transforms in Kafka Conne

[jira] [Updated] (KAFKA-3853) Report offsets for empty groups in ConsumerGroupCommand

[ https://issues.apache.org/jira/browse/KAFKA-3853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-3853: - Reviewer: Ewen Cheslack-Postava > Report offsets for empty groups in ConsumerGroup

[jira] [Updated] (KAFKA-4481) Relax Kafka Streams API type constraints

[ https://issues.apache.org/jira/browse/KAFKA-4481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-4481: - Reviewer: Guozhang Wang > Relax Kafka Streams API type constraints > -

[jira] [Updated] (KAFKA-4602) KIP-72 Allow putting a bound on memory consumed by Incoming requests

[ https://issues.apache.org/jira/browse/KAFKA-4602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-4602: - Reviewer: Ewen Cheslack-Postava > KIP-72 Allow putting a bound on memory consumed

[jira] [Updated] (KAFKA-3751) Add support for SASL/SCRAM mechanisms

[ https://issues.apache.org/jira/browse/KAFKA-3751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-3751: - Reviewer: Ismael Juma > Add support for SASL/SCRAM mechanisms > --

[jira] [Updated] (KAFKA-4462) Improved Kafka Client Compatibility Policy

[ https://issues.apache.org/jira/browse/KAFKA-4462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-4462: - Reviewer: Jason Gustafson > Improved Kafka Client Compatibility Policy > -

[jira] [Updated] (KAFKA-4426) Add consumer.close(timeout, unit) for graceful close with timeout

[ https://issues.apache.org/jira/browse/KAFKA-4426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-4426: - Reviewer: Jason Gustafson > Add consumer.close(timeout, unit) for graceful close w

[jira] [Updated] (KAFKA-4591) Create Topic Policy

[ https://issues.apache.org/jira/browse/KAFKA-4591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-4591: - Reviewer: Jason Gustafson > Create Topic Policy > --- > >

[jira] [Updated] (KAFKA-4565) Separation of Internal and External traffic (KIP-103)

[ https://issues.apache.org/jira/browse/KAFKA-4565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-4565: - Reviewer: Jason Gustafson > Separation of Internal and External traffic (KIP-103)

[jira] [Updated] (KAFKA-4381) Add per partition lag metric to KafkaConsumer.

[ https://issues.apache.org/jira/browse/KAFKA-4381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-4381: - Reviewer: Ewen Cheslack-Postava > Add per partition lag metric to KafkaConsumer. >

[jira] [Updated] (KAFKA-4426) Add consumer.close(timeout, unit) for graceful close with timeout

[ https://issues.apache.org/jira/browse/KAFKA-4426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-4426: - Status: Patch Available (was: Open) > Add consumer.close(timeout, unit) for grace

[jira] [Work started] (KAFKA-4558) throttling_test fails if the producer starts too fast.

[ https://issues.apache.org/jira/browse/KAFKA-4558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-4558 started by Apurva Mehta. --- > throttling_test fails if the producer starts too fast. >

Re: [DISCUSS] KIP-109: Old Consumer Deprecation

> > > The ideal scenario would be for us to provide a tool for no downtime > migration as discussed in the original thread (I filed > https://issues.apache.org/jira/browse/KAFKA-4513 in response to that > discussion). There are a few issues, however: > >- There doesn't seem to be much demand fo

[jira] [Created] (KAFKA-4612) Simple Kafka Streams app causes "ClassCastException: java.lang.String cannot be cast to [B"

Kurt Ostfeld created KAFKA-4612: --- Summary: Simple Kafka Streams app causes "ClassCastException: java.lang.String cannot be cast to [B" Key: KAFKA-4612 URL: https://issues.apache.org/jira/browse/KAFKA-4612

Re: [VOTE] KIP-108: Create Topic Policy

+1 On Mon, Jan 9, 2017 at 3:29 PM, Apurva Mehta wrote: > (hit send too soon) > > +1 (non-binding).. that is a very well written KIP! > > On Mon, Jan 9, 2017 at 3:28 PM, Apurva Mehta wrote: > > > +1, that1 > > > > On Mon, Jan 9, 2017 at 2:47 PM, Neha Narkhede wrote: > > > >> +1 - thanks Ismael!

[jira] [Updated] (KAFKA-4346) Add foreachValue method to KStream

[ https://issues.apache.org/jira/browse/KAFKA-4346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-4346: --- Labels: needs-kip newbie (was: newbie) > Add foreachValue method to KStream > ---

[jira] [Updated] (KAFKA-4217) KStream.transform equivalent of flatMap

[ https://issues.apache.org/jira/browse/KAFKA-4217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-4217: --- Labels: api needs-kip newbie (was: api newbie) > KStream.transform equivalent of flatMap > --

[jira] [Updated] (KAFKA-4218) Enable access to key in ValueTransformer

[ https://issues.apache.org/jira/browse/KAFKA-4218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-4218: --- Summary: Enable access to key in ValueTransformer (was: Enable access to key in {{ValueTransf

[jira] [Updated] (KAFKA-4218) Enable access to key in {{ValueTransformer}}

[ https://issues.apache.org/jira/browse/KAFKA-4218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-4218: --- Labels: api needs-kip newbie (was: api newbie) > Enable access to key in {{ValueTransformer}}

Re: 0.10.2.0 release planning

Hey folks, Here's a quick update and reminder that feature freeze is coming up on Friday (don't worry, you'll have through the end of the day to merge stuff). Most importantly, *everyone* can contribute to landing the many KIPs and features we're trying to get in by Friday. Committers need to tak

[jira] [Updated] (KAFKA-4603) shell in doc argument error and command parsed error

[ https://issues.apache.org/jira/browse/KAFKA-4603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xin updated KAFKA-4603: --- Summary: shell in doc argument error and command parsed error (was: argument error,and command parsed error) > shell

[jira] [Commented] (KAFKA-4612) Simple Kafka Streams app causes "ClassCastException: java.lang.String cannot be cast to [B"

[ https://issues.apache.org/jira/browse/KAFKA-4612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15813501#comment-15813501 ] Matthias J. Sax commented on KAFKA-4612: Did you configure global default key and

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

See Changes: [wangguoz] MINOR: some public JavaDoc cleanup -- [...truncated 18066 lines...] org.apache.kafka.streams.KafkaStreamsTest > testCleanup STARTED org.apache.kafka.streams.KafkaStream

[jira] [Updated] (KAFKA-3751) Add support for SASL/SCRAM mechanisms

[ https://issues.apache.org/jira/browse/KAFKA-3751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3751: --- Reviewer: Jun Rao (was: Ismael Juma) > Add support for SASL/SCRAM mechanisms > --

[jira] [Updated] (KAFKA-4603) the argument of shell in doc wrong and command parsed error

[ https://issues.apache.org/jira/browse/KAFKA-4603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xin updated KAFKA-4603: --- Summary: the argument of shell in doc wrong and command parsed error (was: shell in doc argument error and command pa

Re: [DISCUSS] KIP-109: Old Consumer Deprecation

Hi Joel, Great to hear that LinkedIn is likely to implement KAFKA-4513. :) Yes, the KIP as it stands is a compromise given the situation. We could push the deprecation to the subsequent release: likely to be 0.11.0.0 since there are a number of KIPs that require message format changes. This would

[jira] [Commented] (KAFKA-4570) How to transfer extended fields in producing or consuming requests.

[ https://issues.apache.org/jira/browse/KAFKA-4570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15813696#comment-15813696 ] zander commented on KAFKA-4570: --- [~ewencp] Can I interpret it this way that there is no way

[jira] [Updated] (KAFKA-4603) the argument of shell in doc wrong and command parsed error

[ https://issues.apache.org/jira/browse/KAFKA-4603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-4603: - Assignee: Xin > the argument of shell in doc wrong and command parsed error >

[GitHub] kafka pull request #2320: MINOR: Maybe decorate inner topics for SourceNode

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

Re: [VOTE] KIP-104: Granular Sensors for Streams

+1. Thanks Eno! On Mon, Jan 9, 2017 at 1:05 PM Guozhang Wang wrote: > +1, thanks. > > On Jan 9, 2017 12:27 PM, "Ismael Juma" wrote: > > Thanks for the KIP, +1 on the latest update. > > Ismael > > On Fri, Jan 6, 2017 at 9:37 AM, Eno Thereska > wrote: > > > The discussion points for KIP-104 are a

[jira] [Commented] (KAFKA-4569) Transient failure in org.apache.kafka.clients.consumer.KafkaConsumerTest.testWakeupWithFetchDataAvailable

[ https://issues.apache.org/jira/browse/KAFKA-4569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15813892#comment-15813892 ] Umesh Chaudhary commented on KAFKA-4569: Hi [~ijuma], One observation regarding th

[jira] [Commented] (KAFKA-4570) How to transfer extended fields in producing or consuming requests.

[ https://issues.apache.org/jira/browse/KAFKA-4570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15813908#comment-15813908 ] Ewen Cheslack-Postava commented on KAFKA-4570: -- [~zander] I am not super fami

Re: [DISCUSS] KIP-109: Old Consumer Deprecation

I don't mean to derail this at all, but given Ismael's question I'm wondering what exactly we consider a message format change? Are we assuming that additions like a new compression format (i.e. semantic changes where previously undefined bits, but bits which existed) don't require a format version

  1   2   >