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

@Gwen - yes it did come back to per-API versions - I think that happened toward the end of the KIP hangout. I already said this, but personally I'm also in favor of per-API versions. A global/aggregate API version also works but that is just a proxy to a vector of per-API versions and at the end of

Re: [VOTE] KIP-35: Retrieving protocol version

As the KIP has been modified since we started this vote, the vote is restarted from now. The updated KIP is available at https://cwiki.apache.org/confluence/display/KAFKA/KIP-35+-+Retrieving+protocol+version . On Mon, Mar 14, 2016 at 3:54 PM, Ashish Singh wrote: > Hey Guys, > > I would like to

[jira] [Commented] (KAFKA-3400) Topic stop working / can't describe topic

[ https://issues.apache.org/jira/browse/KAFKA-3400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15199470#comment-15199470 ] Tobias commented on KAFKA-3400: --- The thing is that we are not deleting until the error happe

[jira] [Commented] (KAFKA-3006) Make collection default container type for sequences in the consumer API

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

[jira] [Commented] (KAFKA-3411) Streams: stop using "job" terminology, rename job.id to application.id

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

[jira] [Commented] (KAFKA-3415) AdminOperationException when altering Topic with same number of partitions

[ https://issues.apache.org/jira/browse/KAFKA-3415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15201473#comment-15201473 ] Gérald Quintana commented on KAFKA-3415: Thanks Edoardo > AdminOperationException

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

> > > Anyway, I'm not particularly strong in favor of either approach, but I > think what's concerning Gwen (and myself) is that we're going down to the > wire with a significant decision and the KIP itself seems different every > time we look at it. And still a little incomplete. It would be nice,

[jira] [Resolved] (KAFKA-3411) Streams: stop using "job" terminology, rename job.id to application.id

[ https://issues.apache.org/jira/browse/KAFKA-3411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-3411. -- Resolution: Fixed Fix Version/s: 0.10.0.0 Issue resolved by pull request 1081 [https://gi

[jira] [Commented] (KAFKA-2982) Mark the old Scala producer and related classes as deprecated

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

[jira] [Resolved] (KAFKA-3371) ClientCompatibilityTest system test failing since KIP-31/KIP-32 was merged

[ https://issues.apache.org/jira/browse/KAFKA-3371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava resolved KAFKA-3371. -- Resolution: Fixed Fix Version/s: 0.10.0.0 Issue resolved by pull request

[jira] [Commented] (KAFKA-3383) Producer should not remove an in flight request before successfully parsing the response.

[ https://issues.apache.org/jira/browse/KAFKA-3383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15200588#comment-15200588 ] Jiangjie Qin commented on KAFKA-3383: - [~junrao] It was due to some quota sensor excep

[jira] [Updated] (KAFKA-2832) support exclude.internal.topics in new consumer

[ https://issues.apache.org/jira/browse/KAFKA-2832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-2832: Resolution: Fixed Status: Resolved (was: Patch Available) Issue resolved by pull request 10

[GitHub] kafka pull request: KAFKA-2370: kafka connect pause/resume API

GitHub user hachikuji opened a pull request: https://github.com/apache/kafka/pull/1087 KAFKA-2370: kafka connect pause/resume API You can merge this pull request into a Git repository by running: $ git pull https://github.com/hachikuji/kafka KAFKA-2370 Alternatively you can r

[jira] [Updated] (KAFKA-3403) Upgrade ZkClient to 0.8

[ https://issues.apache.org/jira/browse/KAFKA-3403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke updated KAFKA-3403: --- Status: Patch Available (was: Open) > Upgrade ZkClient to 0.8 > --- > >

Re: [VOTE] KIP-45: Standardize KafkaConsumer API to use Collection

+1 (non-binding) On Wed, Mar 16, 2016 at 1:40 PM, Ismael Juma wrote: > +1 (non-binding) > > Ismael > > On Tue, Mar 15, 2016 at 9:18 PM, Jason Gustafson > wrote: > > > I'd like to open the vote for KIP-45. We've discussed several > alternatives > > on the mailing list and in the KIP call, but th

[jira] [Resolved] (KAFKA-3202) Add system test for KIP-31 and KIP-32 - Change message format version on the fly

[ https://issues.apache.org/jira/browse/KAFKA-3202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira resolved KAFKA-3202. - Resolution: Fixed Issue resolved by pull request 1070 [https://github.com/apache/kafka/pull/1070]

[jira] [Updated] (KAFKA-3331) Refactor TopicCommand to make it testable and add unit tests

[ https://issues.apache.org/jira/browse/KAFKA-3331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish K Singh updated KAFKA-3331: -- Status: Patch Available (was: Open) > Refactor TopicCommand to make it testable and add unit te

[jira] [Updated] (KAFKA-3392) ConsumerRecords iterator throws NoSuchElementException when a TopicPartition is empty

[ https://issues.apache.org/jira/browse/KAFKA-3392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-3392: - Assignee: Drausin Wulsin (was: Neha Narkhede) > ConsumerRecords iterator throws NoSuchElementExce

[GitHub] kafka pull request: KAFKA-3378 Fix for instantly connecting Socket...

GitHub user llowrey opened a pull request: https://github.com/apache/kafka/pull/1085 KAFKA-3378 Fix for instantly connecting SocketChannels (v3) You can merge this pull request into a Git repository by running: $ git pull https://github.com/llowrey/kafka trunk Alternatively y

[GitHub] kafka pull request: KAFKA-3306: Change metdata response to include...

GitHub user granthenke opened a pull request: https://github.com/apache/kafka/pull/1095 KAFKA-3306: Change metdata response to include required additional fi… …elds - Adds a Boolean type to the protocol - Adds new fields to the Metadata reponse protocol - Adds se

[jira] [Commented] (KAFKA-3410) Unclean leader election and "Halting because log truncation is not allowed"

[ https://issues.apache.org/jira/browse/KAFKA-3410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15198321#comment-15198321 ] Gwen Shapira commented on KAFKA-3410: - 1. Broker 2 couldn't have been the leader since

[jira] [Commented] (KAFKA-2370) Add pause/unpause connector support

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

[jira] [Created] (KAFKA-3414) Return of MetadataCache.getAliveBrokers should not be mutated by cache updates

Ismael Juma created KAFKA-3414: -- Summary: Return of MetadataCache.getAliveBrokers should not be mutated by cache updates Key: KAFKA-3414 URL: https://issues.apache.org/jira/browse/KAFKA-3414 Project: Kaf

[jira] [Updated] (KAFKA-3414) Return of MetadataCache.getAliveBrokers should not be mutated by cache updates

[ https://issues.apache.org/jira/browse/KAFKA-3414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3414: --- Status: Patch Available (was: Open) > Return of MetadataCache.getAliveBrokers should not be mutated b

[jira] [Updated] (KAFKA-3417) Invalid characters in config properties not be validated

[ https://issues.apache.org/jira/browse/KAFKA-3417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Byron Ruth updated KAFKA-3417: -- Description: I ran into an error using a {{client.id}} with invalid characters (per the [config valida

[jira] [Commented] (KAFKA-2832) support exclude.internal.topics in new consumer

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

[jira] [Commented] (KAFKA-3422) Add overloading functions for each operator not requiring serialization

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

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

See Changes: [wangguoz] KAFKA-3411: Streams: stop using "job" terminology, rename job.id to [wangguoz] KAFKA-3392: ConsumerRecords iterator throws NoSuchElementException when -- [...truncated

[jira] [Commented] (KAFKA-3378) Client blocks forever if SocketChannel connects instantly

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

[jira] [Updated] (KAFKA-3421) Update docs with new connector features

[ https://issues.apache.org/jira/browse/KAFKA-3421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-3421: Reviewer: Gwen Shapira > Update docs with new connector features > -

Re: [VOTE] KIP-45: Standardize KafkaConsumer API to use Collection

+1 On Tue, Mar 15, 2016 at 2:18 PM, Jason Gustafson wrote: > I'd like to open the vote for KIP-45. We've discussed several alternatives > on the mailing list and in the KIP call, but this vote is only on the > documented KIP: > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=613

[jira] [Commented] (KAFKA-3330) Truncate log cleaner offset checkpoint if the log is truncated

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

[jira] [Updated] (KAFKA-3412) Multiple commitAsync() calls causes SendFailedException in commit callback

[ https://issues.apache.org/jira/browse/KAFKA-3412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-3412: Priority: Blocker (was: Major) Reviewer: Ewen Cheslack-Postava Marking as blocker, since it is

[jira] [Comment Edited] (KAFKA-3153) Serializer/Deserializer Registration and Type inference

[ https://issues.apache.org/jira/browse/KAFKA-3153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15201799#comment-15201799 ] Guozhang Wang edited comment on KAFKA-3153 at 3/18/16 5:10 PM: -

[jira] [Commented] (KAFKA-3409) Mirror maker hangs indefinitely due to commit

[ https://issues.apache.org/jira/browse/KAFKA-3409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15198601#comment-15198601 ] Jiangjie Qin commented on KAFKA-3409: - [~singhashish] Yes, I think we should swallow i

[jira] [Commented] (KAFKA-3417) Invalid characters in config properties not be validated

[ https://issues.apache.org/jira/browse/KAFKA-3417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15200031#comment-15200031 ] Byron Ruth commented on KAFKA-3417: --- I posted on the sarama Go client repo as well for s

[GitHub] kafka pull request: KAFKA-3383: remove in flight request only afte...

Github user zhuchen1018 closed the pull request at: https://github.com/apache/kafka/pull/1050 --- 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-3403) Upgrade ZkClient to 0.8

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

[jira] [Commented] (KAFKA-3135) Unexpected delay before fetch response transmission

[ https://issues.apache.org/jira/browse/KAFKA-3135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15200041#comment-15200041 ] Jason Gustafson commented on KAFKA-3135: [~rangadi] Are you on OSX? So far, I've o

[GitHub] kafka pull request: KAFKA-3371: ClientCompatibilityTest system tes...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1051 --- 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-3413) Load Error Message should be a Warning

[ https://issues.apache.org/jira/browse/KAFKA-3413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15198055#comment-15198055 ] Scott Reynolds commented on KAFKA-3413: --- >This is an error due to the severe implica

Re: [VOTE] KIP-45: Standardize KafkaConsumer API to use Collection

+1 (non-binding) On Wednesday, March 16, 2016, Gwen Shapira wrote: > correcting my mistake - the proposal is wire-compatible, but not source > compatible for some calls. My vote remains though. > > On Wed, Mar 16, 2016 at 10:24 AM, Gwen Shapira > wrote: > > > +1 > > > > I want to clarify that t

[jira] [Commented] (KAFKA-3413) Load Error Message should be a Warning

[ https://issues.apache.org/jira/browse/KAFKA-3413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15197861#comment-15197861 ] Gwen Shapira commented on KAFKA-3413: - This is an error due to the severe implications

[jira] [Commented] (KAFKA-3425) Add KIP-45 note to upgrade docs

[ https://issues.apache.org/jira/browse/KAFKA-3425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15202672#comment-15202672 ] Ismael Juma commented on KAFKA-3425: Maybe we should use this JIRA for missing upgrade

[jira] [Created] (KAFKA-3422) Add overloading functions for each operator not requiring serialization

Guozhang Wang created KAFKA-3422: Summary: Add overloading functions for each operator not requiring serialization Key: KAFKA-3422 URL: https://issues.apache.org/jira/browse/KAFKA-3422 Project: Kafka

[GitHub] kafka pull request: KAFKA-3403: Upgrade ZkClient to 0.8

GitHub user granthenke opened a pull request: https://github.com/apache/kafka/pull/1084 KAFKA-3403: Upgrade ZkClient to 0.8 This ZkClient version adds authentication validation and a conditional delete method needed for other patches You can merge this pull request into a Git repos

[GitHub] kafka pull request: KAFKA-3426; Improve protocol type errors when ...

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/1100 KAFKA-3426; Improve protocol type errors when invalid sizes are received You can merge this pull request into a Git repository by running: $ git pull https://github.com/ijuma/kafka kafka-3426-i

[GitHub] kafka pull request: KAFKA-3411: Streams: stop using "job" terminol...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1081 --- 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] [Updated] (KAFKA-3397) use -1(latest) as time default value for tools.GetOffsetShell

[ https://issues.apache.org/jira/browse/KAFKA-3397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xin Wang updated KAFKA-3397: Summary: use -1(latest) as time default value for tools.GetOffsetShell (was: add missing 'REQUIRED' for too

[jira] [Comment Edited] (KAFKA-3360) Add a protocol page/section to the official Kafka documentation

[ https://issues.apache.org/jira/browse/KAFKA-3360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15198422#comment-15198422 ] Greg Fodor edited comment on KAFKA-3360 at 3/16/16 11:39 PM: -

[jira] [Commented] (KAFKA-3410) Unclean leader election and "Halting because log truncation is not allowed"

[ https://issues.apache.org/jira/browse/KAFKA-3410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15198369#comment-15198369 ] Gwen Shapira commented on KAFKA-3410: - 2. You are right. We can use this JIRA to track

can I please join the contributors list ?

Hi I can't assign a JIRA issue to myself . Can I please join the contributor lists so that I am enabled ? my username is 'ecomar' thanks, Edo -- Edoardo Comar MQ Cloud Technologies WebSphere Application Service Platform for Networks (ASPN) eco...@uk

[jira] [Commented] (KAFKA-3409) Mirror maker hangs indefinitely due to commit

[ https://issues.apache.org/jira/browse/KAFKA-3409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15198591#comment-15198591 ] TAO XIAO commented on KAFKA-3409: - This can also happen when producer is slow and buffer m

[GitHub] kafka pull request: KAFKA-3303: Pass partial record metadata to Pr...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1015 --- 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-3378) Client blocks forever if SocketChannel connects instantly

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

[jira] [Commented] (KAFKA-3403) Upgrade ZkClient to 0.8

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

[jira] [Updated] (KAFKA-3427) broker can return incorrect version of fetch response when the broker hits an unknown exception

[ https://issues.apache.org/jira/browse/KAFKA-3427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-3427: --- Description: In FetchResponse.handleError(), we generate FetchResponse like the following, which always defau

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

I'm a fan of separating feature support/versions into a separate request from metadata -- they're different requests and I don't see how the current model of metadata can properly map to the request version info we need. The complexity of support differing across brokers seems like something client

[jira] [Updated] (KAFKA-3400) Topic stop working / can't describe topic

[ https://issues.apache.org/jira/browse/KAFKA-3400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish K Singh updated KAFKA-3400: -- Fix Version/s: 0.10.0.0 > Topic stop working / can't describe topic > --

[jira] [Updated] (KAFKA-3006) Make collection default container type for sequences in the consumer API

[ https://issues.apache.org/jira/browse/KAFKA-3006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-3006: --- Priority: Blocker (was: Critical) Marking this an 0.10.0.0 blocker since the vote on KIP-45 has passed. > Ma

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

Yeah, Magnus, I'm not arguing for either approach (1) or approach (2), I'm saying the only reason it would make sense to combine the version check and the metadata request would be if the version check was cluster wide like the other metadata. That was where that idea originated and if you make the

[jira] [Comment Edited] (KAFKA-3400) Topic stop working / can't describe topic

[ https://issues.apache.org/jira/browse/KAFKA-3400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15197911#comment-15197911 ] Ashish K Singh edited comment on KAFKA-3400 at 3/16/16 10:50 PM: ---

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

As discussed in the KIP meeting yesterday, the scope of KIP-43 has been reduced so that it can be integrated into 0.10.0.0. The updated KIP is here: https://cwiki.apache.org/confluence/display/KAFKA/KIP-43%3A+Kafka+SASL+enhancements . Can we continue the vote on the updated KIP? Thank you, Rajin

[jira] [Commented] (KAFKA-3336) Unify ser/de pair classes into one serde class

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

[jira] [Updated] (KAFKA-3417) Invalid characters in config properties not be validated

[ https://issues.apache.org/jira/browse/KAFKA-3417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Byron Ruth updated KAFKA-3417: -- Description: I ran into an error using a {{client.id}} with invalid characters (per the [config valida

[jira] [Updated] (KAFKA-3427) broker can return incorrect version of fetch response when the broker hits an unknown exception

[ https://issues.apache.org/jira/browse/KAFKA-3427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-3427: --- Status: Patch Available (was: Open) > broker can return incorrect version of fetch response when the broker h

[jira] [Commented] (KAFKA-3378) Client blocks forever if SocketChannel connects instantly

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

[jira] [Commented] (KAFKA-3402) Restore behaviour of MetadataCache.getTopicMetadata when unsupported security protocol is received

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

[jira] [Commented] (KAFKA-3315) Add Connect API to expose connector configuration info

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

[jira] [Commented] (KAFKA-3410) Unclean leader election and "Halting because log truncation is not allowed"

[ https://issues.apache.org/jira/browse/KAFKA-3410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15198342#comment-15198342 ] James Cheng commented on KAFKA-3410: 1. Hm, you're right, I did say that, didn't I? So

[jira] [Updated] (KAFKA-3403) Upgrade ZkClient to 0.8

[ https://issues.apache.org/jira/browse/KAFKA-3403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-3403: Priority: Critical (was: Major) Reviewer: Flavio Junqueira > Upgrade ZkClient to 0.8 >

[jira] [Updated] (KAFKA-3250) release tarball is unnecessarily large due to duplicate libraries

[ https://issues.apache.org/jira/browse/KAFKA-3250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-3250: Resolution: Fixed Status: Resolved (was: Patch Available) Issue resolved by pull request 10

[jira] [Updated] (KAFKA-3359) Parallel log-recovery of un-flushed segments on startup

[ https://issues.apache.org/jira/browse/KAFKA-3359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vamsi Subhash Achanta updated KAFKA-3359: - Priority: Major (was: Minor) > Parallel log-recovery of un-flushed segments on st

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

See

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

I was a bit surprised to discover that the latest KIP includes an array of versions per request. Especially since we spent an hour discussing global APIs and their tradeoffs. I'm pointing this out in case anyone else missed that - to make sure we are all on the same page in this discussion. Gwen

[jira] [Commented] (KAFKA-3153) Serializer/Deserializer Registration and Type inference

[ https://issues.apache.org/jira/browse/KAFKA-3153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15201131#comment-15201131 ] Michael Noll commented on KAFKA-3153: - [~guozhang], [~yasuhiro.matsuda]: What about th

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

I'm sorry for the confusion but I was referring to a simplified version of the KIP that I'd failed to document on the wiki yet, my bad! The now updated KIP leaves the existing MetadataRequest untouched and instead adds a specific API to query the broker for supported APIs: ApiVersionQueryRequest.

[jira] [Commented] (KAFKA-3414) Return of MetadataCache.getAliveBrokers should not be mutated by cache updates

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

[GitHub] kafka pull request: KAFKA-3315: Add REST and Connector API to expo...

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

Jenkins build is back to normal : kafka-trunk-jdk7 #1119

See

[jira] [Created] (KAFKA-3412) Multiple commitAsync() calls causes SendFailedException in commit callback

Jason Gustafson created KAFKA-3412: -- Summary: Multiple commitAsync() calls causes SendFailedException in commit callback Key: KAFKA-3412 URL: https://issues.apache.org/jira/browse/KAFKA-3412 Project:

[GitHub] kafka pull request: KAFKA-3250: release tarball is unnecessarily l...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1075 --- 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] [Updated] (KAFKA-3266) List/Alter Acls - protocol and server side implementation

[ https://issues.apache.org/jira/browse/KAFKA-3266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke updated KAFKA-3266: --- Fix Version/s: (was: 0.10.0.0) 0.10.1.0 > List/Alter Acls - protocol and server

Re: [GitHub] kafka pull request: Parallel log-recovery of un-flushed segments o...

Can some one please review this? On Fri, Mar 11, 2016 at 12:09 AM, Achanta Vamsi Subhash < achanta.va...@flipkart.com> wrote: > Hi, > I would like to make this into 0.0.10.0 so can someone look into this and > review? > > On Wed, Mar 9, 2016 at 10:29 PM, Achanta Vamsi Subhash < > achanta.va...@fl

[jira] [Updated] (KAFKA-3378) Client blocks forever if SocketChannel connects instantly

[ https://issues.apache.org/jira/browse/KAFKA-3378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-3378: Assignee: Larkin Lowrey > Client blocks forever if SocketChannel connects instantly > --

[jira] [Commented] (KAFKA-3403) Upgrade ZkClient to 0.8

[ https://issues.apache.org/jira/browse/KAFKA-3403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15198249#comment-15198249 ] Grant Henke commented on KAFKA-3403: [~fpj] I saw it just hit maven central today. I w

[jira] [Updated] (KAFKA-3417) Invalid characters in config properties not being validated?

[ https://issues.apache.org/jira/browse/KAFKA-3417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Byron Ruth updated KAFKA-3417: -- Summary: Invalid characters in config properties not being validated? (was: Invalid characters in confi

[jira] [Commented] (KAFKA-3383) Producer should not remove an in flight request before successfully parsing the response.

[ https://issues.apache.org/jira/browse/KAFKA-3383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15201777#comment-15201777 ] Jiangjie Qin commented on KAFKA-3383: - [~junrao] I think the broker side bug has alrea

[jira] [Updated] (KAFKA-3414) Return of MetadataCache.getAliveBrokers should not be mutated by cache updates

[ https://issues.apache.org/jira/browse/KAFKA-3414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-3414: Resolution: Fixed Status: Resolved (was: Patch Available) Issue resolved by pull request 10

[jira] [Updated] (KAFKA-3336) Unify ser/de pair classes into one serde class

[ https://issues.apache.org/jira/browse/KAFKA-3336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-3336: Reviewer: Gwen Shapira > Unify ser/de pair classes into one serde class > --

Re: [VOTE] KIP-45: Standardize KafkaConsumer API to use Collection

+1 (non-binding) Ismael On Tue, Mar 15, 2016 at 9:18 PM, Jason Gustafson wrote: > I'd like to open the vote for KIP-45. We've discussed several alternatives > on the mailing list and in the KIP call, but this vote is only on the > documented KIP: > https://cwiki.apache.org/confluence/pages/view

kafka-streams: Using custom partitioner with higher level DSL constructs?

(lemme know if this belongs on the users email list, I'm not sure where API questions fall) Hi, I'm Ben Osheroff, I wrote Maxwell (http://github.com/zendesk/maxwell) and have been prototyping an engine to do arbitrary denormalizations of Maxwell's CDC events based on the kafka-streams library; the

[GitHub] kafka pull request: KAFKA-3422: Add overloading functions without ...

GitHub user guozhangwang opened a pull request: https://github.com/apache/kafka/pull/1093 KAFKA-3422: Add overloading functions without serdes in Streams DSL You can merge this pull request into a Git repository by running: $ git pull https://github.com/guozhangwang/kafka KCon

[jira] [Updated] (KAFKA-1694) KIP-4: Command line and centralized operations

[ https://issues.apache.org/jira/browse/KAFKA-1694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke updated KAFKA-1694: --- Fix Version/s: 0.10.1.0 > KIP-4: Command line and centralized operations > ---

[jira] [Updated] (KAFKA-3417) Invalid characters in config properties not be validated

[ https://issues.apache.org/jira/browse/KAFKA-3417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Byron Ruth updated KAFKA-3417: -- Description: I ran into an error using a {{client.id}} with invalid characters (per the [config valida

[GitHub] kafka pull request: KAFKA-3378 Fix for instantly connecting Socket...

GitHub user llowrey opened a pull request: https://github.com/apache/kafka/pull/1083 KAFKA-3378 Fix for instantly connecting SocketChannels (v2) Alternative implementation You can merge this pull request into a Git repository by running: $ git pull https://github.com/llowrey/ka

[jira] [Comment Edited] (KAFKA-3413) Load Error Message should be a Warning

[ https://issues.apache.org/jira/browse/KAFKA-3413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15198055#comment-15198055 ] Scott Reynolds edited comment on KAFKA-3413 at 3/16/16 8:11 PM:

[jira] [Updated] (KAFKA-3316) Add Connect REST API to list available connector classes

[ https://issues.apache.org/jira/browse/KAFKA-3316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liquan Pei updated KAFKA-3316: -- Affects Version/s: 0.10.0.0 Status: Patch Available (was: In Progress) > Add Connect RES

[jira] [Updated] (KAFKA-3306) Change metadata response to include required additional fields

[ https://issues.apache.org/jira/browse/KAFKA-3306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke updated KAFKA-3306: --- Summary: Change metadata response to include required additional fields (was: Change metdata response

[jira] [Commented] (KAFKA-3421) Update docs with new connector features

[ https://issues.apache.org/jira/browse/KAFKA-3421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15200716#comment-15200716 ] Gwen Shapira commented on KAFKA-3421: - This can be done post the first 0.10 release ca

  1   2   3   >