Re: [VOTE] KIP-43: Kafka SASL enhancements

Hi all, The updated KIP-43 passes with 3 binding +1s (Harsha, Gwen and Jun) and 3 non-binding +1s. Many thanks to everyone for the feedback. The initial PR is available at https://github.com/apache/kafka/pull/812. Feedback is appreciated. Thank you, Rajini On Fri, Apr 1, 2016 at 11:09 PM, Gra

[jira] [Commented] (KAFKA-3498) Transient failure in kafka.api.SslConsumerTest.testSimpleConsumption

[ https://issues.apache.org/jira/browse/KAFKA-3498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15223759#comment-15223759 ] Rajini Sivaram commented on KAFKA-3498: --- This is a duplicate of KAFKA-3488. > Trans

Re: [RELEASE UPDATE] Postponing the next release candidates and canceling current vote

Sad to see release got postponed. I was looking forward to rack aware replica assignment, to have HA support out of the box. It is hard to follow all the different discussions and what actually caused release to be postponed. Was rack aware feature one of the controversial features? If not would it

[GitHub] kafka pull request: MINOR: Fix zk path in KafkaHealthCheck comment

GitHub user srdo opened a pull request: https://github.com/apache/kafka/pull/1182 MINOR: Fix zk path in KafkaHealthCheck comment You can merge this pull request into a Git repository by running: $ git pull https://github.com/srdo/kafka comment-fix Alternatively you can review

[GitHub] kafka pull request: [TRIVIAL] fix typo in JavaDoc

GitHub user mjsax opened a pull request: https://github.com/apache/kafka/pull/1181 [TRIVIAL] fix typo in JavaDoc I could also include this in https://github.com/apache/kafka/pull/1180 (just wanted to keep PR-1180 "clean") You can merge this pull request into a Git repository by

[GitHub] kafka pull request: KAFKA-3488: Avoid failing of unsent requests i...

GitHub user rajinisivaram opened a pull request: https://github.com/apache/kafka/pull/1183 KAFKA-3488: Avoid failing of unsent requests in consumer where possible Fail unsent requests only when returning from KafkaConsumer.poll(). You can merge this pull request into a Git repositor

[jira] [Commented] (KAFKA-3488) commitAsync() fails if metadata update creates new SASL/SSL connection

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

[jira] [Updated] (KAFKA-3488) commitAsync() fails if metadata update creates new SASL/SSL connection

[ https://issues.apache.org/jira/browse/KAFKA-3488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3488: --- Reviewer: Jason Gustafson Status: Patch Available (was: Open) > commitAsync() fails if metadata

[GitHub] kafka pull request: [TRIVIAL] fix typo in JavaDoc

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

Re: [RELEASE UPDATE] Postponing the next release candidates and canceling current vote

Hi Ewen, Do you mean issues related to versions (since that should be the only difference between trunk and 0.10.0)? Ismael On Mon, Apr 4, 2016 at 4:07 AM, Ewen Cheslack-Postava wrote: > Just wanted to throw it out there that still double committing when the > committer remembers to do so is u

How to make a new KIP ?

Hi Kafka Developers, I would like to start a new KIP like Ewan has proposed into this discussion : https://issues.apache.org/jira/browse/KAFKA-3496 I've created a new account into confluence but some rights are required to create a new page. Am I right ? Thank you in advance, -- Florian HUSSO

[jira] [Commented] (KAFKA-2426) A Kafka node tries to connect to itself through its advertised hostname

[ https://issues.apache.org/jira/browse/KAFKA-2426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15224342#comment-15224342 ] khenaidoo nursimulu commented on KAFKA-2426: Thanks for the quick reply Mikael

Re: [VOTE] KIP-4 Metadata Schema

Hi Jun, Please See my responses below: Hmm, I am not sure about the listener approach. It ignores configs like > enable.topic.deletion and also opens the door for potential ordering issues > since now there are two separate paths for propagating the metadata to the > brokers. This mechanism is

[jira] [Commented] (KAFKA-3491) Issue with consumer close() in finally block with 'enable.auto.commit=true'

[ https://issues.apache.org/jira/browse/KAFKA-3491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15224527#comment-15224527 ] Jason Gustafson commented on KAFKA-3491: This is a tough one. I tend to agree with

Re: [RELEASE UPDATE] Postponing the next release candidates and canceling current vote

Are there any commits that is only for 0.10.0 but not for trunk? Guozhang On Mon, Apr 4, 2016 at 4:24 AM, Ismael Juma wrote: > Hi Ewen, > > Do you mean issues related to versions (since that should be the only > difference between trunk and 0.10.0)? > > Ismael > > On Mon, Apr 4, 2016 at 4:07 AM

[jira] [Commented] (KAFKA-3491) Issue with consumer close() in finally block with 'enable.auto.commit=true'

[ https://issues.apache.org/jira/browse/KAFKA-3491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15224544#comment-15224544 ] Ismael Juma commented on KAFKA-3491: It seems to me that a `rewind` would be clearer t

[jira] [Commented] (KAFKA-3491) Issue with consumer close() in finally block with 'enable.auto.commit=true'

[ https://issues.apache.org/jira/browse/KAFKA-3491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15224549#comment-15224549 ] Guozhang Wang commented on KAFKA-3491: -- [~hachikuji] Could you clarify a bit more on

Re: How to make a new KIP ?

Hi Florian, I have granted you the permission, you should be able to create new wiki pages now. Cheers, Guozhang On Mon, Apr 4, 2016 at 6:19 AM, Florian Hussonnois wrote: > Hi Kafka Developers, > > I would like to start a new KIP like Ewan has proposed into this > discussion : > https://issue

[jira] [Commented] (KAFKA-3491) Issue with consumer close() in finally block with 'enable.auto.commit=true'

[ https://issues.apache.org/jira/browse/KAFKA-3491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15224555#comment-15224555 ] Ewen Cheslack-Postava commented on KAFKA-3491: -- Yeah, `rewind` makes sense --

Re: KIP-4 Wiki Update

Thanks for the review Guozhang, see my responses below. 1. One minor thing: "Note there is a special use case - automatic topic > creation for TopicMetadataRequest, to trigger it user should set > client_id=consumer and define only topic name:" > I think the current behavior is that as long as t

[jira] [Commented] (KAFKA-3491) Issue with consumer close() in finally block with 'enable.auto.commit=true'

[ https://issues.apache.org/jira/browse/KAFKA-3491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15224588#comment-15224588 ] Jason Gustafson commented on KAFKA-3491: [~guozhang] That's what I was thinking in

Re: [DISCUSS] KIP-52 - Add Connector Control APIs

Hey Ismael, thanks for having a look. I've changed pause/resume to use PUT. -Jason On Sun, Apr 3, 2016 at 7:30 PM, Ewen Cheslack-Postava wrote: > Ismael, > > Great point. Pause and resume should be idempotent and actually represent > updating a resource that gets written to Kafka (although I mu

[jira] [Commented] (KAFKA-3494) mbeans overwritten with identical clients on a single jvm

[ https://issues.apache.org/jira/browse/KAFKA-3494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15224655#comment-15224655 ] Jiangjie Qin commented on KAFKA-3494: - One solution might be introduce a {{UniqueClien

[jira] [Commented] (KAFKA-3480) Autogenerate metrics documentation

[ https://issues.apache.org/jira/browse/KAFKA-3480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15224663#comment-15224663 ] Gwen Shapira commented on KAFKA-3480: - Cool idea [~o...@apache.org]. Right now our doc

[jira] [Created] (KAFKA-3499) byte[] should not be used as Map key nor Set member

josh gruenberg created KAFKA-3499: - Summary: byte[] should not be used as Map key nor Set member Key: KAFKA-3499 URL: https://issues.apache.org/jira/browse/KAFKA-3499 Project: Kafka Issue Typ

[jira] [Updated] (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:all-tabpanel ] Ismael Juma updated KAFKA-3499: --- Fix Version/s: 0.10.0.0 > byte[] should not be used as Map key nor Set member > --

[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&focusedCommentId=15224691#comment-15224691 ] Ismael Juma commented on KAFKA-3499: [~guozhang], this looks important to fix so I set

[jira] [Commented] (KAFKA-3494) mbeans overwritten with identical clients on a single jvm

[ https://issues.apache.org/jira/browse/KAFKA-3494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15224717#comment-15224717 ] Onur Karaman commented on KAFKA-3494: - Are you proposing this {{UniqueClientidWithSequ

Re: [DISCUSS] KIP-35 - Retrieve protocol version

> > >In case of connection closures, the KIP recommends that clients should >use some other method of determining the apiRequest version to use, > like, >probing. For instance, client will send V0 version of apiVersion request >and will try higher versions incrementally. In case b,

[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&focusedCommentId=15224741#comment-15224741 ] Jay Kreps commented on KAFKA-3499: -- I think this problem is more general than byte[] sinc

[jira] [Updated] (KAFKA-3500) KafkaOffsetBackingStore set method needs to handle null

[ https://issues.apache.org/jira/browse/KAFKA-3500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liquan Pei updated KAFKA-3500: -- Environment: (was: In some cases, the key or value for the offset map can be null. However, it seems

[jira] [Created] (KAFKA-3500) KafkaOffsetBackingStore set method needs to handle null

Liquan Pei created KAFKA-3500: - Summary: KafkaOffsetBackingStore set method needs to handle null Key: KAFKA-3500 URL: https://issues.apache.org/jira/browse/KAFKA-3500 Project: Kafka Issue Type:

[jira] [Comment Edited] (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&focusedCommentId=15224741#comment-15224741 ] Jay Kreps edited comment on KAFKA-3499 at 4/4/16 6:27 PM: -- I thin

How will KIP-35 and KIP-43 play together?

Hi Kafka Team, As a practical test-case of KIP-35, I'd like to turn your attention to KIP-43: https://cwiki.apache.org/confluence/display/KAFKA/KIP-43 KIP-43 makes an interesting modification to the protocol, but only under specific conditions: "*Client flow:* 1. If sasl.mechanism is not GSS

[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&focusedCommentId=15224758#comment-15224758 ] Ismael Juma commented on KAFKA-3499: [~jkreps], I think there are two separate issues:

Re: [VOTE] KIP-4 Metadata Schema

Grant, 2. The issues that I was thinking are the following. (a) Say the controller has topic deletion disabled and a topic deletion request is submitted to ZK. In this case, the controller will ignore this request. However, the broker may pick up the topic deletion marker in a transient window. (b

Re: KIP-4 Wiki Update

About the "only controller" to "any broker" over time, I think I buy all these points. Since this is out of the scope of this KIP, and since as Grant said, this would be a rather general feature, but not only restricted to the added admin requests in this KIP, we can leave that discussion for later

[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&focusedCommentId=15224768#comment-15224768 ] Jay Kreps commented on KAFKA-3499: -- Yeah, gotcha, that would be totally broken. > byte[]

[jira] [Commented] (KAFKA-3491) Issue with consumer close() in finally block with 'enable.auto.commit=true'

[ https://issues.apache.org/jira/browse/KAFKA-3491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15224792#comment-15224792 ] Guozhang Wang commented on KAFKA-3491: -- I think when the event loop is single threade

[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&focusedCommentId=15224809#comment-15224809 ] Guozhang Wang commented on KAFKA-3499: -- [~ijuma] We realized this problem before in t

Kafka KIP meeting April 5 at 11:00am PST

Hi, Everyone, We will have a Kafka KIP meeting tomorrow at 11:00am PST. If you plan to attend but haven't received an invite, please let me know. The following is the agenda. Agenda: KIP-4 - MetadataRequest schema KIP-35 - Retrieve protocol version Thanks, -- Guozhang

Re: Kafka KIP meeting April 5 at 11:00am PST

Hey Guozhang, Can you add KIP-52 to the agenda? Based on the current discussion, I don't think it will take much time. Thanks, Jason On Mon, Apr 4, 2016 at 11:59 AM, Guozhang Wang wrote: > Hi, Everyone, > > We will have a Kafka KIP meeting tomorrow at 11:00am PST. If you plan to > attend but h

Re: How will KIP-35 and KIP-43 play together?

I think with KIP-43, the existing way of sasl handshake during connection still works. It's just that if you want to support non-GSSAPI, you will need a new sasl handshake implementation in the client. It's unfortunate that Protocol currently only covers the communication after the connection is re

Re: How will KIP-35 and KIP-43 play together?

I think the challenge here is that even after KIP-35 clients will not know whether the server supports new sasl mechanisms or not, so non-Java clients will have to assume it is not supported (and will therefore lag behind on features). I think this highlights a short-coming of KIP-35, and I'm wond

Re: How will KIP-35 and KIP-43 play together?

An option would be to add a version for the handshake in the KIP-35 response. Ismael On 4 Apr 2016 20:09, "Gwen Shapira" wrote: > I think the challenge here is that even after KIP-35 clients will not know > whether the server supports new sasl mechanisms or not, so non-Java clients > will have t

Re: How will KIP-35 and KIP-43 play together?

Yeah. This gets us close to Ewen's feature-version suggestion, since we need to version things that are not tied to specific Requests. Gwen On Mon, Apr 4, 2016 at 12:20 PM, Ismael Juma wrote: > An option would be to add a version for the handshake in the KIP-35 > response. > > Ismael > On 4 Apr

Re: How will KIP-35 and KIP-43 play together?

As Jun says the SASL (and SSL) handshake is not done using the Kafka protocol and is performed before any Kafka protocol requests pass between client and server. It might make sense to move the SASL handshake from its custom protocol format into the Kafka protocol and make it use the proper Kafka

[jira] [Commented] (KAFKA-3494) mbeans overwritten with identical clients on a single jvm

[ https://issues.apache.org/jira/browse/KAFKA-3494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15224923#comment-15224923 ] Jiangjie Qin commented on KAFKA-3494: - I was thinking to use {{UniqueClientIdWithSeque

[DISCUSS] KIP-53 Add custom policies for reconnect attempts to NetworkdClient

Hi Kafka Team, I have made a new Kafka Improvement Proposal. https://cwiki.apache.org/confluence/display/KAFKA/KIP-53+-+Add+custom+policies+for+reconnect+attempts+to+NetworkdClient This is my first proposal so I don't know if I have given enough information. Also I have already proposed an implem

[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&focusedCommentId=15224928#comment-15224928 ] Tommy Becker commented on KAFKA-3499: - This was/is a problem in Samza as well. Though

Re: How will KIP-35 and KIP-43 play together?

SASL mechanisms are configurable properties and slightly different from versions since the fact that a broker version *can* support a mechanism doesn't actually mean that a broker *does* support that mechanism. SASL implementations typically interact with external authentication servers, so I would

Re: How will KIP-35 and KIP-43 play together?

By the way, I don't think non-Java clients have to lag on this feature even if we don't do anything because the SASL mechanism is defined by a client property. So, if a non-GSSAPI mechanism is chosen, the clients would optimistically use the new way (older brokers would close the connection). This

Re: How will KIP-35 and KIP-43 play together?

Rajini, it's a good point that not all mechanisms may be enabled. However, we can handle that case by rejecting a mechanism requested by the client without having to initially provide a list of mechanisms right? Ismael On Mon, Apr 4, 2016 at 8:57 PM, Rajini Sivaram wrote: > SASL mechanisms are

[jira] [Created] (KAFKA-3501) Console consumer process hangs on SIGINT

Sébastien Launay created KAFKA-3501: --- Summary: Console consumer process hangs on SIGINT Key: KAFKA-3501 URL: https://issues.apache.org/jira/browse/KAFKA-3501 Project: Kafka Issue Type: Bug

[jira] [Updated] (KAFKA-3501) Console consumer process hangs on SIGINT

[ https://issues.apache.org/jira/browse/KAFKA-3501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sébastien Launay updated KAFKA-3501: Attachment: jstack.txt > Console consumer process hangs on SIGINT >

Re: [DISCUSS] KIP-53 Add custom policies for reconnect attempts to NetworkdClient

If I understand the problem we are fixing is a connection storm where when a new broker comes online it is overwhelmed with connections. In general we try hard to avoid plugins where possible. Maybe instead of adding another plugin interface we could just directly solve this problem by doing some

Re: [RELEASE UPDATE] Postponing the next release candidates and canceling current vote

Ismael, Fair enough, I guess it doesn't matter if we're going to merge again -- then until we decide to branch we'll be back in sync. At the moment there's a pretty major diff between trunk and 0.10.0 and I'm not sure what went on only trunk and what went to 0.10.0 only. As long as the latter set

Re: How will KIP-35 and KIP-43 play together?

If a client provides a mechanism that is not enabled (or supported) in the broker, the server rejects the mechanism and returns the set of enabled mechanisms in the error response. I thought Gwen's question was asking how a client would be able to determine what mechanisms are supported in the brok

[jira] [Created] (KAFKA-3502) Build failure due to failure in streams' test

Ashish K Singh created KAFKA-3502: - Summary: Build failure due to failure in streams' test Key: KAFKA-3502 URL: https://issues.apache.org/jira/browse/KAFKA-3502 Project: Kafka Issue Type: Bug

Re: How will KIP-35 and KIP-43 play together?

Hi Rajini, I think Gwen's question was in relation to the fact that we are changing the SASL protocol in KIP-43, not the fact that clients need to know the mechanisms supported by the broker. I think the approach of returning the supported protocols in the error response works fine. Ismael On 4

Re: [VOTE] KIP-50 - Enhance Authorizer interface to be aware of supported Principal Types

Hi Jun, Thanks for the call out to the KIP-4 Authorizer work. I will discuss it with Ashish and let him follow up here. Thanks, Grant On Sun, Apr 3, 2016 at 10:37 AM, Jun Rao wrote: > Ashish, > > For the two benefits that you listed, fail fast can be done just in the > implementation w/o getSu

Re: [RELEASE UPDATE] Postponing the next release candidates and canceling current vote

It's true that the current situation is not so clear. Gwen, maybe we should do the initial merge of trunk to 0.10.0 soon to get them back in sync? Please let me know if you'd like some help (the first merge may not be completely straightforward although subsequent ones will). Ismael On 4 Apr 2016

[jira] [Commented] (KAFKA-3502) Build failure due to failure in streams' test

[ https://issues.apache.org/jira/browse/KAFKA-3502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15225080#comment-15225080 ] Guozhang Wang commented on KAFKA-3502: -- Hi [~singhashish] is this consistently re-pro

[jira] [Created] (KAFKA-3503) Throw exception on missing/non-existent partition

Navin Markandeya created KAFKA-3503: --- Summary: Throw exception on missing/non-existent partition Key: KAFKA-3503 URL: https://issues.apache.org/jira/browse/KAFKA-3503 Project: Kafka Issue

[jira] [Updated] (KAFKA-3503) Throw exception on missing/non-existent partition

[ https://issues.apache.org/jira/browse/KAFKA-3503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Navin Markandeya updated KAFKA-3503: Description: I would expect some exception to be thrown when a consumer tries to access a n

[jira] [Commented] (KAFKA-3502) Build failure due to failure in streams' test

[ https://issues.apache.org/jira/browse/KAFKA-3502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15225095#comment-15225095 ] Ashish K Singh commented on KAFKA-3502: --- [~guozhang] I could not reproduce it even o

[jira] [Created] (KAFKA-3504) Changelog partition configured to enable log compaction

Guozhang Wang created KAFKA-3504: Summary: Changelog partition configured to enable log compaction Key: KAFKA-3504 URL: https://issues.apache.org/jira/browse/KAFKA-3504 Project: Kafka Issue T

[jira] [Commented] (KAFKA-3502) Build failure due to failure in streams' test

[ https://issues.apache.org/jira/browse/KAFKA-3502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15225104#comment-15225104 ] Guozhang Wang commented on KAFKA-3502: -- Sounds good. But it always worth reporting su

[jira] [Created] (KAFKA-3505) Set curRecord in punctuate() functions

Guozhang Wang created KAFKA-3505: Summary: Set curRecord in punctuate() functions Key: KAFKA-3505 URL: https://issues.apache.org/jira/browse/KAFKA-3505 Project: Kafka Issue Type: Sub-task

Re: How will KIP-35 and KIP-43 play together?

Ismael, Thank you, that makes sense. On Mon, Apr 4, 2016 at 9:52 PM, Ismael Juma wrote: > Hi Rajini, > > I think Gwen's question was in relation to the fact that we are changing > the SASL protocol in KIP-43, not the fact that clients need to know the > mechanisms supported by the broker. > > I

[jira] [Updated] (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:all-tabpanel ] Guozhang Wang updated KAFKA-3499: - Issue Type: Sub-task (was: Bug) Parent: KAFKA-2590 > byte[] should not be used as Map key

[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&focusedCommentId=15225135#comment-15225135 ] Guozhang Wang commented on KAFKA-3499: -- Converting to Kafka Streams subtask to keep t

[GitHub] kafka pull request: HOTFIX: set timestamp in SinkNode

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1137 --- 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] [Created] (KAFKA-3506) Kafka Connect Task Restart API

Jason Gustafson created KAFKA-3506: -- Summary: Kafka Connect Task Restart API Key: KAFKA-3506 URL: https://issues.apache.org/jira/browse/KAFKA-3506 Project: Kafka Issue Type: Improvement

[jira] [Assigned] (KAFKA-3505) Set curRecord in punctuate() functions

[ https://issues.apache.org/jira/browse/KAFKA-3505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang reassigned KAFKA-3505: Assignee: Guozhang Wang > Set curRecord in punctuate() functions >

[GitHub] kafka pull request: Kafka Connect metrics NPE prevention

GitHub user SupermanScott opened a pull request: https://github.com/apache/kafka/pull/1184 Kafka Connect metrics NPE prevention Summary: When a worker is started up but hasn't setup the assignmentSnapshot it is possible to throw a NPE. This happens in our environment as we ha

[GitHub] kafka pull request: KAFKA-3501: Console consumer process hangs on ...

GitHub user slaunay opened a pull request: https://github.com/apache/kafka/pull/1185 KAFKA-3501: Console consumer process hangs on exit - replace `System.exit(1)` with a regular `return` in order to release the latch blocking the shutdown hook thread from shutting down the JVM -

[jira] [Commented] (KAFKA-3501) Console consumer process hangs on SIGINT

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

[jira] [Updated] (KAFKA-3501) Console consumer process hangs on SIGINT

[ https://issues.apache.org/jira/browse/KAFKA-3501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sébastien Launay updated KAFKA-3501: Status: Patch Available (was: Open) PR against trunk to fix the issue with a new unit test:

[jira] [Work started] (KAFKA-3506) Kafka Connect Task Restart API

[ https://issues.apache.org/jira/browse/KAFKA-3506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-3506 started by Jason Gustafson. -- > Kafka Connect Task Restart API > -- > >

[jira] [Commented] (KAFKA-3491) Issue with consumer close() in finally block with 'enable.auto.commit=true'

[ https://issues.apache.org/jira/browse/KAFKA-3491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15225237#comment-15225237 ] Ewen Cheslack-Postava commented on KAFKA-3491: -- I don't think we should worry

Jenkins build is back to normal : kafka-trunk-jdk8 #504

See

[jira] [Updated] (KAFKA-2590) KIP-28: Kafka Streams Checklist

[ https://issues.apache.org/jira/browse/KAFKA-2590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-2590: - Labels: (was: streams) > KIP-28: Kafka Streams Checklist > --- > >

[jira] [Commented] (KAFKA-3491) Issue with consumer close() in finally block with 'enable.auto.commit=true'

[ https://issues.apache.org/jira/browse/KAFKA-3491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15225287#comment-15225287 ] Guozhang Wang commented on KAFKA-3491: -- Yeah that was what I thought, i.e. we can be

[jira] [Updated] (KAFKA-2590) KIP-28: Kafka Streams Checklist

[ https://issues.apache.org/jira/browse/KAFKA-2590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-2590: - Labels: streams (was: ) > KIP-28: Kafka Streams Checklist > --- > >

[jira] [Updated] (KAFKA-2590) KIP-28: Kafka Streams Checklist

[ https://issues.apache.org/jira/browse/KAFKA-2590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-2590: - Component/s: kafka streams > KIP-28: Kafka Streams Checklist > --- > >

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

See Changes: [wangguoz] HOTFIX: set timestamp in SinkNode -- [...truncated 7592 lines...] org.apache.kafka.streams.kstream.internals.KTableKTableOuterJoinTest > testNotSendingOldValue PASSED o

[jira] [Updated] (KAFKA-3183) Add metrics for persistent store caching layer

[ https://issues.apache.org/jira/browse/KAFKA-3183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-3183: - Component/s: kafka streams > Add metrics for persistent store caching layer >

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

[ https://issues.apache.org/jira/browse/KAFKA-3101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-3101: - Component/s: kafka streams > Optimize Aggregation Outputs > > >

[jira] [Updated] (KAFKA-3185) Allow users to cleanup internal data

[ https://issues.apache.org/jira/browse/KAFKA-3185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-3185: - Component/s: kafka streams > Allow users to cleanup internal data > --

[jira] [Updated] (KAFKA-3477) Add customizable StreamPartition into #to functions of Streams DSL

[ https://issues.apache.org/jira/browse/KAFKA-3477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-3477: - Component/s: kafka streams > Add customizable StreamPartition into #to functions of Streams DSL >

[jira] [Updated] (KAFKA-3184) Add Checkpoint for In-memory State Store

[ https://issues.apache.org/jira/browse/KAFKA-3184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-3184: - Component/s: kafka streams > Add Checkpoint for In-memory State Store > --

[jira] [Updated] (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:all-tabpanel ] Guozhang Wang updated KAFKA-3337: - Component/s: kafka streams > Extract selector as a separate groupBy operator for KTable aggregatio

[jira] [Updated] (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 ] Guozhang Wang updated KAFKA-3429: - Component/s: kafka streams > Remove Serdes needed for repartitioning in KTable stateful operations

[jira] [Updated] (KAFKA-3440) Add Javadoc for KTable (changelog stream) and KStream (record stream)

[ https://issues.apache.org/jira/browse/KAFKA-3440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-3440: - Component/s: kafka streams > Add Javadoc for KTable (changelog stream) and KStream (record stream)

[jira] [Updated] (KAFKA-3439) Document possible exception thrown in public APIs

[ https://issues.apache.org/jira/browse/KAFKA-3439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-3439: - Component/s: kafka streams > Document possible exception thrown in public APIs > -

[jira] [Updated] (KAFKA-3430) Allow users to set key in KTable.toStream() and KStream

[ https://issues.apache.org/jira/browse/KAFKA-3430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-3430: - Component/s: kafka streams > Allow users to set key in KTable.toStream() and KStream > ---

[jira] [Updated] (KAFKA-3338) Add print and writeAsText functions to the Streams DSL

[ https://issues.apache.org/jira/browse/KAFKA-3338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-3338: - Component/s: kafka streams > Add print and writeAsText functions to the Streams DSL >

[jira] [Updated] (KAFKA-3443) Support regex topics in addSource() and stream()

[ https://issues.apache.org/jira/browse/KAFKA-3443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-3443: - Component/s: kafka streams > Support regex topics in addSource() and stream() > --

[jira] [Updated] (KAFKA-3478) Finer Stream Flow Control

[ https://issues.apache.org/jira/browse/KAFKA-3478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-3478: - Component/s: kafka streams > Finer Stream Flow Control > - > >

  1   2   >