[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. >

[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] [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=15236584#comment-15236584 ] Jiangjie Qin commented on KAFKA-3163: - Move this ticket back to 0.10.0.0 per latest discussion. The

[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 >

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

[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 >

[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=15236512#comment-15236512 ] Greg Fodor edited comment on KAFKA-3544 at 4/12/16 3:05 AM: Not sure of the

[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=15236512#comment-15236512 ] Greg Fodor edited comment on KAFKA-3544 at 4/12/16 3:04 AM: Not sure of the

[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=15236512#comment-15236512 ] Greg Fodor edited comment on KAFKA-3544 at 4/12/16 3:04 AM: Not sure of the

[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=15236512#comment-15236512 ] Greg Fodor commented on KAFKA-3544: --- Not sure of the best way to share the topology. Here's the relevant

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

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 >

[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

[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: - 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: - Description: Right now it seems that if you want to apply an arbitrary stateful transformation

[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=15236434#comment-15236434 ] Guozhang Wang commented on KAFKA-3543: -- Yeah, we should definitely improve our documentation

[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=15236427#comment-15236427 ] Greg Fodor commented on KAFKA-3543: --- Just something akin to a flatTransform where the output of the

[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-3542) Add "repartition (+ join)" operations to streams

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

[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=15236414#comment-15236414 ] Guozhang Wang commented on KAFKA-1981: -- The contributor pinged us for reviews. Assigned to [~ijuma]

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

[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=15236401#comment-15236401 ] Guozhang Wang commented on KAFKA-3542: -- That is a fair point. Currently we let users to specify a

[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=15236394#comment-15236394 ] Guozhang Wang commented on KAFKA-3543: -- What kind of helper methods do you have in mind? Interested

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 >

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=+VOTE+KIP+4+Metadata+Schema > > > I also would like to

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

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

[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=15236375#comment-15236375 ] Greg Fodor commented on KAFKA-3543: --- That makes sense, thanks! It may be useful to provide a helper

[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=15236374#comment-15236374 ] Greg Fodor commented on KAFKA-3542: --- Right, this map approach is what I am doing right now before all of

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

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

[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=15236355#comment-15236355 ] Guozhang Wang commented on KAFKA-3543: -- In Kafka Streams we do not materialize in each operator, but

[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=15236349#comment-15236349 ] Guozhang Wang commented on KAFKA-3542: -- If you are joining two KTable streams, then yes, you'd use an

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

[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=15236347#comment-15236347 ] Guozhang Wang commented on KAFKA-3542: -- [~gfodor] You can use "map" to set the key for streams before

[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=15236343#comment-15236343 ] Greg Fodor commented on KAFKA-3542: --- Ah, I may understand what you're getting at here -- to do the

[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=15236339#comment-15236339 ] Greg Fodor commented on KAFKA-3543: --- Ah interesting, my assumption was that the items emitted from the

[jira] [Work started] (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 ] Work on KAFKA-3430 started by Bill Bejeck. -- > Allow users to set key in KTable.toStream() and KStream >

[jira] [Commented] (KAFKA-3545) Generalized Serdes for List/Map

[ https://issues.apache.org/jira/browse/KAFKA-3545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15236334#comment-15236334 ] Guozhang Wang commented on KAFKA-3545: -- Thanks for reporting. Having generalized serdes for

[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=15236331#comment-15236331 ] Greg Fodor commented on KAFKA-3542: --- I might just not be understanding, but a simple example is if I

[jira] [Updated] (KAFKA-3545) Generalized Serdes for List/Map

[ https://issues.apache.org/jira/browse/KAFKA-3545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-3545: - Labels: api (was: ) > Generalized Serdes for List/Map > --- > >

[jira] [Updated] (KAFKA-3545) Generalized Serdes for List/Map

[ https://issues.apache.org/jira/browse/KAFKA-3545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-3545: - Fix Version/s: 0.10.1.0 > Generalized Serdes for List/Map > --- > >

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

[ https://issues.apache.org/jira/browse/KAFKA-3544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-3544: - Labels: semantics (was: ) > Missing topics on startup > - > >

[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=15236324#comment-15236324 ] Guozhang Wang commented on KAFKA-3544: -- Thanks for reporting this. Sounds like a bug as we actually

Jenkins build is back to normal : kafka-0.10.0-jdk7 #34

See

[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=15236313#comment-15236313 ] Guozhang Wang commented on KAFKA-3543: -- [~gfodor] We have seen such use cases in other places, and

[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=15236304#comment-15236304 ] Guozhang Wang commented on KAFKA-3542: -- [~gfodor] Kafka Streams already such kind of repartitioning

Re: KStream Close Processor

Yeah we can definitely do better in documentation. While regarding the API changes I would prefer to hold and think through if such use cases are common in pattern, and that if we can even re-order the closing process to get around the issue I mentioned above if it is required. Guozhang On Mon,

[jira] [Commented] (KAFKA-3523) Capture org.apache.kafka.clients.consumer.CommitFailedException in UncaughtExceptionHandler

[ https://issues.apache.org/jira/browse/KAFKA-3523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15236290#comment-15236290 ] Guozhang Wang commented on KAFKA-3523: -- Looked at the source code, the `CommitFailedException` itself

[jira] [Updated] (KAFKA-3523) Capture org.apache.kafka.clients.consumer.CommitFailedException in UncaughtExceptionHandler

[ https://issues.apache.org/jira/browse/KAFKA-3523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-3523: - Description: When the sync commit failed due to an ongoing rebalance, it is thrown all the way

[jira] [Assigned] (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 reassigned KAFKA-3499: Assignee: Guozhang Wang > byte[] should not be used as Map key nor Set member >

[jira] [Updated] (KAFKA-3445) ConnectorConfig should validate TASKS_MAX_CONFIG's lower bound limit

[ https://issues.apache.org/jira/browse/KAFKA-3445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-3445: Fix Version/s: 0.10.0.0 > ConnectorConfig should validate TASKS_MAX_CONFIG's lower bound limit >

[jira] [Updated] (KAFKA-3508) Transient failure in kafka.security.auth.SimpleAclAuthorizerTest.testHighConcurrencyModificationOfResourceAcls

[ https://issues.apache.org/jira/browse/KAFKA-3508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-3508: Fix Version/s: 0.10.0.0 > Transient failure in >

[jira] [Updated] (KAFKA-3528) AbstractCoordinator wakeup during rebalance can cause spurious rebalances

[ https://issues.apache.org/jira/browse/KAFKA-3528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-3528: Fix Version/s: 0.10.0.0 > AbstractCoordinator wakeup during rebalance can cause spurious rebalances

[jira] [Updated] (KAFKA-3407) ErrorLoggingCallback trims helpful diagnostic information.

[ https://issues.apache.org/jira/browse/KAFKA-3407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-3407: Fix Version/s: 0.10.0.0 > ErrorLoggingCallback trims helpful diagnostic information. >

[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 ] Gwen Shapira updated KAFKA-3488: Fix Version/s: 0.10.0.0 > commitAsync() fails if metadata update creates new SASL/SSL connection >

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

[ https://issues.apache.org/jira/browse/KAFKA-3505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-3505: Fix Version/s: 0.10.0.0 > Set curRecord in punctuate() functions >

[jira] [Updated] (KAFKA-3464) Connect security system tests

[ https://issues.apache.org/jira/browse/KAFKA-3464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-3464: Fix Version/s: 0.10.0.0 > Connect security system tests > - > >

[jira] [Updated] (KAFKA-3384) bin scripts may not be portable/POSIX compliant

[ https://issues.apache.org/jira/browse/KAFKA-3384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-3384: Fix Version/s: 0.10.0.0 > bin scripts may not be portable/POSIX compliant >

[jira] [Updated] (KAFKA-2672) SendFailedException when new consumer is run with SSL

[ https://issues.apache.org/jira/browse/KAFKA-2672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-2672: Fix Version/s: 0.10.0.0 > SendFailedException when new consumer is run with SSL >

[jira] [Commented] (KAFKA-3042) updateIsr should stop after failed several times due to zkVersion issue

[ https://issues.apache.org/jira/browse/KAFKA-3042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15236180#comment-15236180 ] Robert Christ commented on KAFKA-3042: -- The log on disk also stops and 00:39:46,246. It does not

[jira] [Updated] (KAFKA-2930) Update references to ZooKeeper in the docs

[ https://issues.apache.org/jira/browse/KAFKA-2930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-2930: Fix Version/s: 0.10.0.0 > Update references to ZooKeeper in the docs >

[jira] [Updated] (KAFKA-2844) Use different keyTab for client and server in SASL tests

[ https://issues.apache.org/jira/browse/KAFKA-2844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-2844: Fix Version/s: 0.10.0.0 > Use different keyTab for client and server in SASL tests >

[jira] [Updated] (KAFKA-2239) Allow coordinator to aggresively remove group when it is no longer owning the group

[ https://issues.apache.org/jira/browse/KAFKA-2239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-2239: Fix Version/s: 0.9.0.0 > Allow coordinator to aggresively remove group when it is no longer owning

[jira] [Updated] (KAFKA-496) high level producer send should return a response

[ https://issues.apache.org/jira/browse/KAFKA-496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-496: --- Fix Version/s: (was: 0.10.1.0) 0.9.0.0 > high level producer send should return

Merged trunk to 0.10.0

Hi Kafka Devs, As you remember, I agreed to merge trunk to 0.10.0 branch on weekly basis until the next RC to avoid burdening committers with double commits. I just merged latest trunk into 0.10.0 and pushed to apache. Enjoy. Gwen Shapira

[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=15236160#comment-15236160 ] ASF GitHub Bot commented on KAFKA-3163: --- GitHub user becketqin opened a pull request:

Re: [VOTE] KIP-52: Kafka Connect Control APIs

Thanks to all who voted. Looks like this KIP passes with +5 (binding), and +1 (non-binding). -Jason On Thu, Apr 7, 2016 at 2:44 AM, Ismael Juma wrote: > +1 (non-binding) > > Ismael > > On Thu, Apr 7, 2016 at 1:25 AM, Jason Gustafson > wrote: > > > Minor

[GitHub] kafka pull request: KAFKA-3163: Add time based index to Kafka.

GitHub user becketqin opened a pull request: https://github.com/apache/kafka/pull/1215 KAFKA-3163: Add time based index to Kafka. This is patch for KIP-33. https://cwiki.apache.org/confluence/display/KAFKA/KIP-33+-+Add+a+time+based+log+index You can merge this pull request

[jira] [Created] (KAFKA-3545) Generalized Serdes for List/Map

Greg Fodor created KAFKA-3545: - Summary: Generalized Serdes for List/Map Key: KAFKA-3545 URL: https://issues.apache.org/jira/browse/KAFKA-3545 Project: Kafka Issue Type: Improvement

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

Greg Fodor created KAFKA-3544: - Summary: Missing topics on startup Key: KAFKA-3544 URL: https://issues.apache.org/jira/browse/KAFKA-3544 Project: Kafka Issue Type: Bug Components:

[jira] [Comment Edited] (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=15236121#comment-15236121 ] Greg Fodor edited comment on KAFKA-3543 at 4/11/16 10:40 PM: - Also note that

[jira] [Created] (KAFKA-3543) Allow a variant of transform() which allows emitting multiple values

Greg Fodor created KAFKA-3543: - Summary: Allow a variant of transform() which allows emitting multiple values Key: KAFKA-3543 URL: https://issues.apache.org/jira/browse/KAFKA-3543 Project: Kafka

[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 ] Greg Fodor updated KAFKA-3543: -- Summary: Allow a variant of transform() which can emit multiple values (was: Allow a variant of

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

Greg Fodor created KAFKA-3542: - Summary: Add "repartition (+ join)" operations to streams Key: KAFKA-3542 URL: https://issues.apache.org/jira/browse/KAFKA-3542 Project: Kafka Issue Type:

[GitHub] kafka pull request: MINOR: Remove unused hadoop version

GitHub user granthenke opened a pull request: https://github.com/apache/kafka/pull/1214 MINOR: Remove unused hadoop version All dependencies on hadoop were removed with MiniKDC. This removes the left over version entry. You can merge this pull request into a Git repository by

[jira] [Comment Edited] (KAFKA-3042) updateIsr should stop after failed several times due to zkVersion issue

[ https://issues.apache.org/jira/browse/KAFKA-3042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15236055#comment-15236055 ] Flavio Junqueira edited comment on KAFKA-3042 at 4/11/16 9:58 PM: -- Thanks

[jira] [Commented] (KAFKA-3042) updateIsr should stop after failed several times due to zkVersion issue

[ https://issues.apache.org/jira/browse/KAFKA-3042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15236055#comment-15236055 ] Flavio Junqueira commented on KAFKA-3042: - Thanks for the logs. I still don’t have an answer, but

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 > < > http://search-hadoop.com/m/uyzND1xlaiU10QlYX=+VOTE+KIP+4+Metadata+Schema > > > I also would like to include a behavior change to the MetadataResponse. I >

[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: - Fix Version/s: (was: 0.10.1.0) 0.10.0.0 > Extract selector as a separate

[jira] [Updated] (KAFKA-3538) Abstract the creation/retrieval of Producer for stream sinks for unit testing

[ https://issues.apache.org/jira/browse/KAFKA-3538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-3538: - Fix Version/s: 0.10.1.0 > Abstract the creation/retrieval of Producer for stream sinks for unit

[jira] [Updated] (KAFKA-3538) Abstract the creation/retrieval of Producer for stream sinks for unit testing

[ https://issues.apache.org/jira/browse/KAFKA-3538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-3538: - Labels: semantics (was: ) > Abstract the creation/retrieval of Producer for stream sinks for

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

See

[jira] [Created] (KAFKA-3541) OffsetIndex-Memory Mapped files gets corrupted on a shared drive or encrypted drive

Sriharsha Chintalapani created KAFKA-3541: - Summary: OffsetIndex-Memory Mapped files gets corrupted on a shared drive or encrypted drive Key: KAFKA-3541 URL:

[jira] [Updated] (KAFKA-3540) KafkaConsumer.close() may block indefinitely

[ https://issues.apache.org/jira/browse/KAFKA-3540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Zhurakousky updated KAFKA-3540: Description: KafkaConsumer API doc states {code} Close the consumer, waiting indefinitely

[jira] [Created] (KAFKA-3540) KafkaConsumer.close() may block indefinitely

Oleg Zhurakousky created KAFKA-3540: --- Summary: KafkaConsumer.close() may block indefinitely Key: KAFKA-3540 URL: https://issues.apache.org/jira/browse/KAFKA-3540 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=15235799#comment-15235799 ] Michael Noll edited comment on KAFKA-3499 at 4/11/16 8:05 PM: -- FWIW, we ran

[jira] [Created] (KAFKA-3539) KafkaProducer.send() may block even though it returns the Future

Oleg Zhurakousky created KAFKA-3539: --- Summary: KafkaProducer.send() may block even though it returns the Future Key: KAFKA-3539 URL: https://issues.apache.org/jira/browse/KAFKA-3539 Project: Kafka

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

See Changes: [wangguoz] MINOR: fix incorrect exception message in KafkaProducer -- [...truncated 4372 lines...] kafka.admin.AdminRackAwareTest > testRackAwareExpansion PASSED

[jira] [Created] (KAFKA-3538) Abstract the creation/retrieval of Producer for stream sinks for unit testing

Michael Coon created KAFKA-3538: --- Summary: Abstract the creation/retrieval of Producer for stream sinks for unit testing Key: KAFKA-3538 URL: https://issues.apache.org/jira/browse/KAFKA-3538 Project:

[jira] [Comment Edited] (KAFKA-3522) Consider adding version information into rocksDB storage format

[ https://issues.apache.org/jira/browse/KAFKA-3522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15235814#comment-15235814 ] Michael Noll edited comment on KAFKA-3522 at 4/11/16 7:41 PM: -- [~jkreps]

[jira] [Commented] (KAFKA-3522) Consider adding version information into rocksDB storage format

[ https://issues.apache.org/jira/browse/KAFKA-3522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15235814#comment-15235814 ] Michael Noll commented on KAFKA-3522: - [~jkreps] wrote: {quote} I think you could potentially just

[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=15235799#comment-15235799 ] Michael Noll edited comment on KAFKA-3499 at 4/11/16 7:35 PM: -- FWIW, we ran

[jira] [Resolved] (KAFKA-3519) Refactor Transformer templates to return the same strong-typed value.

[ https://issues.apache.org/jira/browse/KAFKA-3519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-3519. -- Resolution: Fixed Issue resolved by pull request 1204

[jira] [Commented] (KAFKA-3519) Refactor Transformer templates to return the same strong-typed value.

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

[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=15235799#comment-15235799 ] Michael Noll commented on KAFKA-3499: - FWIW, we ran into the same problem when handling byte[] in

[GitHub] kafka pull request: KAFKA-3519: Refactor Transformer's transform /...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1204 --- 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] [Updated] (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:all-tabpanel ] Guozhang Wang updated KAFKA-3537: - Labels: semantics (was: ) > Provide access to low-level Metrics in ProcessorContext >

  1   2   >