[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=15236348#comment-15236348 ] Jason Gustafson commented on KAFKA-3488: [~guozhang] Sorry for the late response.

[jira] [Commented] (KAFKA-3542) Add "repartition (+ join)" operations to streams

[ https://issues.apache.org/jira/browse/KAFKA-3542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15236349#comment-15236349 ] Guozhang Wang commented on KAFKA-3542: -- If you are joining two KTable streams, then y

[jira] [Commented] (KAFKA-3543) Allow a variant of transform() which can emit multiple values

[ https://issues.apache.org/jira/browse/KAFKA-3543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15236355#comment-15236355 ] Guozhang Wang commented on KAFKA-3543: -- In Kafka Streams we do not materialize in eac

[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=15236357#comment-15236357 ] Guozhang Wang commented on KAFKA-3488: -- That is good. My previous concern does not ac

Kafka connector:AvroConverter exception

Hi, In the process of kafka sink connetor test, after I launched connect-standalone and ran kafka-avro-console-producer command, I typed {"f1":"value1"} in the console according to the demo mentioned in kafka connector document . But connect-standalone terminal prints such excpetion 2016-04-1

[jira] [Commented] (KAFKA-3542) Add "repartition (+ join)" operations to streams

[ https://issues.apache.org/jira/browse/KAFKA-3542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15236374#comment-15236374 ] Greg Fodor commented on KAFKA-3542: --- Right, this map approach is what I am doing right n

[jira] [Commented] (KAFKA-3543) Allow a variant of transform() which can emit multiple values

[ https://issues.apache.org/jira/browse/KAFKA-3543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15236375#comment-15236375 ] Greg Fodor commented on KAFKA-3543: --- That makes sense, thanks! It may be useful to provi

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

Hello Jun, The 3rd option will require Apache Sentry to go GA with current authorizer interface, and at this point it seems that the interface won't last long. Within a few months, Sentry will have to make a breaking change. I do understand that Kafka should not have to delay its release due to on

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

Magnus, That sounds reasonable. To reduce the changes on the server side, I'd suggest the following minor tweaks on the proposal. 1. Continue supporting the separate SASL and SASL_SSL port. On SASL port, we support the new sequence ApiVersionRequest (optional), SaslHandshakeRequest, SASL tok

Re: [VOTE] KIP-4 Metadata Schema (Round 2)

Grant, Thanks for the updated version. +1 from me. Jun On Mon, Apr 11, 2016 at 10:42 AM, Grant Henke wrote: > Based on the discussion in the previous vote thread > < > http://search-hadoop.com/m/uyzND1xlaiU10QlYX&subj=+VOTE+KIP+4+Metadata+Schema > > > I also would like to include a behavior ch

[jira] [Commented] (KAFKA-3543) Allow a variant of transform() which can emit multiple values

[ https://issues.apache.org/jira/browse/KAFKA-3543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15236394#comment-15236394 ] Guozhang Wang commented on KAFKA-3543: -- What kind of helper methods do you have in mi

Re: [VOTE] KIP-4 Metadata Schema (Round 2)

+1 (non-binding) Ismael On Tue, Apr 12, 2016 at 2:19 AM, Jun Rao wrote: > Grant, > > Thanks for the updated version. +1 from me. > > Jun > > On Mon, Apr 11, 2016 at 10:42 AM, Grant Henke wrote: > > > Based on the discussion in the previous vote thread > > < > > > http://search-hadoop.com/m/uyz

[jira] [Commented] (KAFKA-3542) Add "repartition (+ join)" operations to streams

[ https://issues.apache.org/jira/browse/KAFKA-3542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15236401#comment-15236401 ] Guozhang Wang commented on KAFKA-3542: -- That is a fair point. Currently we let users

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

Ashish, So, you want to take a shot at option 2 for 0.10.0? That's fine with me too. I am just not sure if we have enough time to think through the changes. Thanks, Jun On Mon, Apr 11, 2016 at 6:05 PM, Ashish Singh wrote: > Hello Jun, > > The 3rd option will require Apache Sentry to go GA wit

[jira] [Updated] (KAFKA-1981) Make log compaction point configurable

[ https://issues.apache.org/jira/browse/KAFKA-1981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-1981: - Reviewer: Ismael Juma > Make log compaction point configurable > -

[jira] [Commented] (KAFKA-1981) Make log compaction point configurable

[ https://issues.apache.org/jira/browse/KAFKA-1981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15236414#comment-15236414 ] Guozhang Wang commented on KAFKA-1981: -- The contributor pinged us for reviews. Assign

[jira] [Commented] (KAFKA-3542) Add "repartition (+ join)" operations to streams

[ https://issues.apache.org/jira/browse/KAFKA-3542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15236417#comment-15236417 ] Greg Fodor commented on KAFKA-3542: --- great. feel free to close. > Add "repartition (+ j

[jira] [Resolved] (KAFKA-3542) Add "repartition (+ join)" operations to streams

[ https://issues.apache.org/jira/browse/KAFKA-3542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-3542. -- Resolution: Information Provided > Add "repartition (+ join)" operations to streams > --

[jira] [Commented] (KAFKA-3543) Allow a variant of transform() which can emit multiple values

[ https://issues.apache.org/jira/browse/KAFKA-3543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15236427#comment-15236427 ] Greg Fodor commented on KAFKA-3543: --- Just something akin to a flatTransform where the ou

[jira] [Commented] (KAFKA-3543) Allow a variant of transform() which can emit multiple values

[ https://issues.apache.org/jira/browse/KAFKA-3543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15236434#comment-15236434 ] Guozhang Wang commented on KAFKA-3543: -- Yeah, we should definitely improve our docume

[jira] [Updated] (KAFKA-3543) Allow a variant of transform() which can emit multiple values

[ https://issues.apache.org/jira/browse/KAFKA-3543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-3543: - Description: Right now it seems that if you want to apply an arbitrary stateful transformation to

[jira] [Updated] (KAFKA-3543) Allow a variant of transform() which can emit multiple values

[ https://issues.apache.org/jira/browse/KAFKA-3543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-3543: - Fix Version/s: 0.10.1.0 > Allow a variant of transform() which can emit multiple values >

[jira] [Updated] (KAFKA-3543) Allow a variant of transform() which can emit multiple values

[ https://issues.apache.org/jira/browse/KAFKA-3543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-3543: - Labels: api (was: ) > Allow a variant of transform() which can emit multiple values > ---

[jira] [Updated] (KAFKA-3543) Allow a variant of transform() which can emit multiple values

[ https://issues.apache.org/jira/browse/KAFKA-3543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-3543: - Description: Right now it seems that if you want to apply an arbitrary stateful transformation to

Build failed in Jenkins: kafka-0.10.0-jdk7 #35

See Changes: [cshapi] Minor: Correcting version to 0.10.0.0-SNAPSHOT again following merge -- [...truncated 5884 lines...] org.apache.kafka.connect.storage.MemoryStatusBackingStoreTest > putAnd

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

Yes, Jun. I would like to try get option 2 in, if possible in 0.10. I am not asking for delaying 0.10 for it, but some reviews and early feedback would be great. At this point this is what I have in mind. 1. Move authorizer and related entities to its own package. Note that I am proposing to drop

[jira] [Commented] (KAFKA-3544) Missing topics on startup

[ https://issues.apache.org/jira/browse/KAFKA-3544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15236512#comment-15236512 ] Greg Fodor commented on KAFKA-3544: --- Not sure of the best way to share the topology. Her

[jira] [Comment Edited] (KAFKA-3544) Missing topics on startup

[ https://issues.apache.org/jira/browse/KAFKA-3544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15236512#comment-15236512 ] Greg Fodor edited comment on KAFKA-3544 at 4/12/16 3:04 AM: No

[jira] [Comment Edited] (KAFKA-3544) Missing topics on startup

[ https://issues.apache.org/jira/browse/KAFKA-3544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15236512#comment-15236512 ] Greg Fodor edited comment on KAFKA-3544 at 4/12/16 3:04 AM: No

[jira] [Comment Edited] (KAFKA-3544) Missing topics on startup

[ https://issues.apache.org/jira/browse/KAFKA-3544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15236512#comment-15236512 ] Greg Fodor edited comment on KAFKA-3544 at 4/12/16 3:05 AM: No

[jira] [Updated] (KAFKA-3163) KIP-33 - Add a time based log index to Kafka

[ https://issues.apache.org/jira/browse/KAFKA-3163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-3163: Fix Version/s: (was: 0.10.1.0) 0.10.0.0 > KIP-33 - Add a time based log index

[jira] [Updated] (KAFKA-3163) KIP-33 - Add a time based log index to Kafka

[ https://issues.apache.org/jira/browse/KAFKA-3163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-3163: Status: Patch Available (was: Open) > KIP-33 - Add a time based log index to Kafka > --

Re: [VOTE] KIP-4 Metadata Schema (Round 2)

+1 On Mon, Apr 11, 2016 at 10:42 AM, Grant Henke wrote: > Based on the discussion in the previous vote thread > > I also would like to include a behavior change to the MetadataResponse. I > have update the wiki >

[jira] [Updated] (KAFKA-3163) KIP-33 - Add a time based log index to Kafka

[ https://issues.apache.org/jira/browse/KAFKA-3163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-3163: Reviewer: Jun Rao > KIP-33 - Add a time based log index to Kafka > -

[jira] [Commented] (KAFKA-3163) KIP-33 - Add a time based log index to Kafka

[ https://issues.apache.org/jira/browse/KAFKA-3163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15236584#comment-15236584 ] Jiangjie Qin commented on KAFKA-3163: - Move this ticket back to 0.10.0.0 per latest di

[jira] [Created] (KAFKA-3546) kafka-server-stop fails on some distros

Gwen Shapira created KAFKA-3546: --- Summary: kafka-server-stop fails on some distros Key: KAFKA-3546 URL: https://issues.apache.org/jira/browse/KAFKA-3546 Project: Kafka Issue Type: Bug

[jira] [Resolved] (KAFKA-3546) kafka-server-stop fails on some distros

[ https://issues.apache.org/jira/browse/KAFKA-3546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira resolved KAFKA-3546. - Resolution: Invalid never mind. looks like I used an old version of the script. > kafka-server-st

<    1   2