[jira] [Resolved] (KAFKA-3188) Add system test for KIP-31 and KIP-32 - Compatibility Test

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

[jira] [Updated] (KAFKA-3419) New consumer javadoc unclear on topic subscription vs partition assignment

[ https://issues.apache.org/jira/browse/KAFKA-3419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-3419: --- Fix Version/s: 0.10.0.0 > New consumer javadoc unclear on topic subscription vs partition

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

[GitHub] kafka pull request: KAFKA-3394: allow null offset metadata in comm...

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

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

+1 I want to clarify that the compatibility issue is only for unshaded dependencies. Code and wire protocol will be compatible. Gwen 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

[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=15199776#comment-15199776 ] Edoardo Comar commented on KAFKA-3415: -- I agree that the retcode to the shell should be 0, not 1. I

[jira] [Commented] (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:comment-tabpanel=15200404#comment-15200404 ] ASF GitHub Bot commented on KAFKA-3250: --- Github user asfgit closed the pull request at:

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

We have proposed and discussed majorly three approaches so far, there were many minor versions with small variations. Comparing them really requires a side by side proposal and their pros/cons, and I agree with others that this has been lacking in the KIP. We just updated the KIP with following

[jira] [Commented] (KAFKA-1173) Using Vagrant to get up and running with Apache Kafka

[ https://issues.apache.org/jira/browse/KAFKA-1173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15202404#comment-15202404 ] Stefan Gower commented on KAFKA-1173: - It is certainly helpful to have a way to quickly set up a

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

[ https://issues.apache.org/jira/browse/KAFKA-2370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-2370: Status: Patch Available (was: Open) > Add pause/unpause connector support >

[GitHub] kafka pull request: MINOR: KAFKA-3260 follow up, fix commitRecord ...

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

[GitHub] kafka pull request: KAFKA-3402; Restore behaviour of MetadataCache...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1073 --- 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-3424) Add CORS support to Connect REST API

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

[GitHub] kafka pull request: KAFKA-3378; Client blocks forever if SocketCha...

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/1094 KAFKA-3378; Client blocks forever if SocketChannel connects instantly This is a different implementation to the one in #1085 by Larkin Lowrey (@llowrey). The hard part here was actually finding the

Kafka Mirroring Issue: Leader Not Available Exception

I am trying to mirror a three node kafka cluster to a single node cluster. When I starts the mirror maker I got the exception LeaderNotAvailable, but at the same time topics are created and messages are commited. Please help me out. Best Regards Anshul Bhatnagar

[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=15197995#comment-15197995 ] Gwen Shapira commented on KAFKA-3410: - 1. Broker became leader because he was the last leader in the

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

See Changes: [cshapi] KAFKA-2832: Add a consumer config option to exclude internal topics [cshapi] KAFKA-3188: Compatibility test for old and new clients with 0.10 broker [me] KAFKA-3315: Add REST and Connector API to expose

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

+1 (non-binding) On Wed, Mar 16, 2016 at 12:24 PM, Gwen Shapira wrote: > +1 > > I want to clarify that the compatibility issue is only for unshaded > dependencies. Code and wire protocol will be compatible. > > Gwen > > On Tue, Mar 15, 2016 at 2:18 PM, Jason Gustafson

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

+1. Normally I'd be more of a stickler for compatibility, but this is new, I think it's worth emphasizing that unstable actually means unstable & might require recompile (and maybe even adapting code when we think the change warrants it), and I think the impact is relatively low since those

[jira] [Commented] (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:comment-tabpanel=15202120#comment-15202120 ] ASF GitHub Bot commented on KAFKA-3397: --- Github user asfgit closed the pull request at:

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

See Changes: [cshapi] KAFKA-3414; Return of MetadataCache.getAliveBrokers should not be [cshapi] KAFKA-3373; MINOR: follow-up, a few val renames remaining [cshapi] KAFKA-3250: release tarball is unnecessarily large due to duplicate

[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=15200219#comment-15200219 ] ASF GitHub Bot commented on KAFKA-2832: --- Github user asfgit closed the pull request at:

[jira] [Updated] (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:all-tabpanel ] Gwen Shapira updated KAFKA-3402: Resolution: Fixed Status: Resolved (was: Patch Available) Issue resolved by pull request

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

See Changes: [cshapi] KAFKA-3424: Add CORS support to Connect REST API -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on ubuntu-4 (docker Ubuntu

[jira] [Created] (KAFKA-3417) Invalid characters in config not be caught early enough

Byron Ruth created KAFKA-3417: - Summary: Invalid characters in config not be caught early enough Key: KAFKA-3417 URL: https://issues.apache.org/jira/browse/KAFKA-3417 Project: Kafka Issue Type:

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

See Changes: [cshapi] KAFKA-2982; Mark the old Scala producer and related classes as -- [...truncated 1573 lines...] kafka.integration.SslTopicMetadataTest > testBasicTopicMetadata PASSED

[jira] [Comment Edited] (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=15197729#comment-15197729 ] Ashish K Singh edited comment on KAFKA-3409 at 3/16/16 5:49 PM: This can

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

See Changes: [cshapi] KAFKA-3424: Add CORS support to Connect REST API -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on ubuntu-us1 (Ubuntu

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

See Changes: [cshapi] KAFKA-3403: Upgrade ZkClient to 0.8 [cshapi] KAFKA-3402; Restore behaviour of MetadataCache.getTopicMetadata when -- Started by an SCM change Started by an SCM change

[GitHub] kafka pull request: KAFKA-3424: Add CORS support to Connect REST A...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1099 --- 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-3424) Add CORS support to Connect REST API

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

[jira] [Updated] (KAFKA-3424) Add CORS support to Connect REST API

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

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

See Changes: [cshapi] KAFKA-3427: broker can return incorrect version of fetch response when -- [...truncated 1708 lines...] jdk1.7.0_51/jre/lib/zi/Asia/Samarkand

[jira] [Created] (KAFKA-3426) Improve protocol type errors when invalid sizes are received

Ismael Juma created KAFKA-3426: -- Summary: Improve protocol type errors when invalid sizes are received Key: KAFKA-3426 URL: https://issues.apache.org/jira/browse/KAFKA-3426 Project: Kafka

[GitHub] kafka pull request: [KAFKA-3316]: Add REST API for listing connect...

GitHub user Ishiihara opened a pull request: https://github.com/apache/kafka/pull/1090 [KAFKA-3316]: Add REST API for listing connector plugins You can merge this pull request into a Git repository by running: $ git pull https://github.com/Ishiihara/kafka kafka-3316

[jira] [Work started] (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:all-tabpanel ] Work on KAFKA-3422 started by Guozhang Wang. > Add overloading functions for each operator not requiring serialization >

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

See Changes: [cshapi] KAFKA-3427: broker can return incorrect version of fetch response when -- [...truncated 1607 lines...]

[GitHub] kafka pull request: KAFKA-3414; Return of MetadataCache.getAliveBr...

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/1088 KAFKA-3414; Return of MetadataCache.getAliveBrokers should not be mutated by cache updates `Map.values` returns `DefaultValuesIterable` where the default implementation of `toSeq` is (sadly)

[jira] [Work started] (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 ] Work on KAFKA-3316 started by Liquan Pei. - > Add Connect REST API to list available connector classes >

[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 ] Gwen Shapira updated KAFKA-3427: Resolution: Fixed Status: Resolved (was: Patch Available) Issue resolved by pull request

[jira] [Commented] (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:comment-tabpanel=15203035#comment-15203035 ] ASF GitHub Bot commented on KAFKA-3427: --- Github user asfgit closed the pull request at:

[GitHub] kafka pull request: KAFKA-3427: broker can return incorrect versio...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1101 --- 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-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: -- Status: Patch Available (was: Open) > Topic stop working / can't describe topic >

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

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

GitHub user zhuchen1018 reopened a pull request: https://github.com/apache/kafka/pull/1050 KAFKA-3383: remove in flight request only after response parsing succeeds @becketqin, could you take a look at the patch? You can merge this pull request into a Git repository by running:

[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: - Resolution: Fixed Status: Resolved (was: Patch Available) Issue resolved by pull request

[GitHub] kafka pull request: KAFKA-3392: ConsumerRecords iterator throws No...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1055 --- 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-3190) KafkaProducer should not invoke callback in send()

[ https://issues.apache.org/jira/browse/KAFKA-3190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-3190: Priority: Critical (was: Blocker) Fix Version/s: (was: 0.10.0.0)

[jira] [Updated] (KAFKA-3306) Change metdata 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: --- Status: Patch Available (was: Open) > Change metdata response to include required additional fields

[jira] [Updated] (KAFKA-2945) CreateTopic - protocol and server side implementation

[ https://issues.apache.org/jira/browse/KAFKA-2945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke updated KAFKA-2945: --- Fix Version/s: 0.10.1.0 > CreateTopic - protocol and server side implementation >

[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=15198172#comment-15198172 ] Flavio Junqueira commented on KAFKA-3403: - [~granthenke] zkclient 0.8 is already available. are

[jira] [Commented] (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=15198422#comment-15198422 ] Greg Fodor commented on KAFKA-3360: --- Apologies as I did not really know the best place to put this, and

[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=15200965#comment-15200965 ] ASF GitHub Bot commented on KAFKA-3383: --- GitHub user zhuchen1018 reopened a pull request:

[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=15198619#comment-15198619 ] Jiangjie Qin commented on KAFKA-3409: - [~xiaotao183] Yes, there are a few scenarios in which offset

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

See Changes: [me] MINOR: KAFKA-3260 follow up, fix commitRecord calls in tests [me] KAFKA-3371: ClientCompatibilityTest system test failing -- [...truncated 3701 lines...]

[jira] [Updated] (KAFKA-3424) Add CORS support to Connect REST API

[ https://issues.apache.org/jira/browse/KAFKA-3424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-3424: - Status: Patch Available (was: Open) > Add CORS support to Connect REST API >

[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: Resolution: Fixed Fix Version/s: 0.10.0.0 Status: Resolved (was: Patch Available)

[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=15198173#comment-15198173 ] Flavio Junqueira commented on KAFKA-3403: -

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

Looks like the KIP has passed. The finally tally is +5 among committers and +9 overall. Thanks to Pierre-Yves Ritschard for all of the hard work and persistence with this! -Jason On Wed, Mar 16, 2016 at 9:01 PM, Ewen Cheslack-Postava wrote: > +1. > > Normally I'd be more of

[jira] [Updated] (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:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-3315: - Resolution: Fixed Status: Resolved (was: Patch Available) Issue resolved

[jira] [Assigned] (KAFKA-1342) Slow controlled shutdowns can result in stale shutdown requests

[ https://issues.apache.org/jira/browse/KAFKA-1342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin reassigned KAFKA-1342: --- Assignee: Jiangjie Qin (was: Onur Karaman) > Slow controlled shutdowns can result in stale

[jira] [Commented] (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:comment-tabpanel=15202467#comment-15202467 ] ASF GitHub Bot commented on KAFKA-3427: --- GitHub user junrao opened a pull request:

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

Scott Reynolds created KAFKA-3413: - Summary: Load Error Message should be a Warning Key: KAFKA-3413 URL: https://issues.apache.org/jira/browse/KAFKA-3413 Project: Kafka Issue Type:

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

"I think I would make this approach work by looking at the released server version documentation for each version that I am trying to support and test against*, manually identify the expected "protocol vectors" each supports, store that as a map of vectors to "broker versions", check each vector

[jira] [Updated] (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:all-tabpanel ] Guozhang Wang updated KAFKA-3422: - Resolution: Fixed Status: Resolved (was: Patch Available) Issue resolved by pull request

[GitHub] kafka pull request: KAFKA-2982; Mark the old Scala producer and re...

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

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

On Thu, Mar 17, 2016 at 1:42 PM, Gwen Shapira wrote: > "I think I would make this approach work by looking at the released server > version documentation for each version that I am trying to support and test > against*, manually identify the expected "protocol vectors" each

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

Jay, I think you are correct. Once a client gets the metadata from a broker, it does not really need to get brokers and topics info from other brokers again. However, with the current suggestion the client will still have to send metadata request to get broker's supported protocols. Client can

[jira] [Created] (KAFKA-3418) Add section on detecting consumer failures in new consumer javadoc

Jason Gustafson created KAFKA-3418: -- Summary: Add section on detecting consumer failures in new consumer javadoc Key: KAFKA-3418 URL: https://issues.apache.org/jira/browse/KAFKA-3418 Project: Kafka

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

Jun Rao created KAFKA-3427: -- Summary: broker can return incorrect version of fetch response when the broker hits an unknown exception Key: KAFKA-3427 URL: https://issues.apache.org/jira/browse/KAFKA-3427

[GitHub] kafka pull request: KAFKA-3415: Add partitions check if 0 partitio...

GitHub user edoardocomar opened a pull request: https://github.com/apache/kafka/pull/1089 KAFKA-3415: Add partitions check if 0 partitions are to be added If no partitions are to be added, the command will exit gracefully with retcode 0 and a printed message. This patch

[jira] [Created] (KAFKA-3420) Transient failure in OffsetCommitTest.testNonExistingTopicOffsetCommit

Jason Gustafson created KAFKA-3420: -- Summary: Transient failure in OffsetCommitTest.testNonExistingTopicOffsetCommit Key: KAFKA-3420 URL: https://issues.apache.org/jira/browse/KAFKA-3420 Project:

[jira] [Commented] (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:comment-tabpanel=15197541#comment-15197541 ] ASF GitHub Bot commented on KAFKA-3371: --- Github user asfgit closed the pull request at:

[jira] [Updated] (KAFKA-3234) Minor documentation edits: clarify minISR; some topic-level configs are missing

[ https://issues.apache.org/jira/browse/KAFKA-3234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Koshy updated KAFKA-3234: -- Fix Version/s: (was: 0.10.0.0) 0.10.0.1 > Minor documentation edits: clarify

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

Hey Ashish, Couple quick things: 1. You list as a rejected alternative "making the documentation the source of truth for the protocol", but I think what you actually describe in that section is global versioning, which of those two things are we voting to reject? I think this is a philosophical

[GitHub] kafka pull request: KAFKA-3414; Return of MetadataCache.getAliveBr...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1088 --- 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-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:comment-tabpanel=15200533#comment-15200533 ] ASF GitHub Bot commented on KAFKA-3202: --- Github user asfgit closed the pull request at:

[jira] [Updated] (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:all-tabpanel ] Ismael Juma updated KAFKA-3402: --- Reviewer: Gwen Shapira > Restore behaviour of MetadataCache.getTopicMetadata when unsupported

[GitHub] kafka pull request: KAFKA-3336: Unify Serializer and Deserializer ...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1066 --- 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] [Comment Edited] (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=15200588#comment-15200588 ] Jiangjie Qin edited comment on KAFKA-3383 at 3/18/16 3:38 AM: -- [~junrao] It

[GitHub] kafka pull request: KAFKA-3424: Add CORS support to Connect REST A...

GitHub user ewencp opened a pull request: https://github.com/apache/kafka/pull/1099 KAFKA-3424: Add CORS support to Connect REST API You can merge this pull request into a Git repository by running: $ git pull https://github.com/ewencp/kafka cors-rest-support Alternatively

[jira] [Updated] (KAFKA-3303) Pass partial record metadata to Interceptor onAcknowledgement in case of errors

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

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

See Changes: [me] HOTFIX: Renamed tests to match expected suffix [wangguoz] KAFKA-3422: Add overloading functions without serdes in Streams DSL [junrao] KAFKA-3394; allow null offset metadata in commit API [wangguoz] KAFKA-3397: use

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

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 the compatibility issue is only for unshaded > dependencies. Code

[GitHub] kafka pull request: HOTFIX: Renamed tests to match expected suffix

GitHub user enothereska opened a pull request: https://github.com/apache/kafka/pull/1096 HOTFIX: Renamed tests to match expected suffix @ewencp @gwenshap @granders could you have a look please? Thanks. You can merge this pull request into a Git repository by running: $ git

[jira] [Created] (KAFKA-3416) Update Fetcher to return Future for Metadata requests

John Warner created KAFKA-3416: -- Summary: Update Fetcher to return Future for Metadata requests Key: KAFKA-3416 URL: https://issues.apache.org/jira/browse/KAFKA-3416 Project: Kafka Issue Type:

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

+1 I think we should just do it and apologize and mark it stable. Also, the javadocs do show the unstable annotation but it isn't easy to figure out exactly what that means. -Jay On Wed, Mar 16, 2016 at 10:24 AM, Gwen Shapira wrote: > +1 > > I want to clarify that the

[jira] [Commented] (KAFKA-3373) Add `log` prefix to KIP-31/32 configs

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

[jira] [Updated] (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:all-tabpanel ] Gwen Shapira updated KAFKA-2982: Resolution: Fixed Status: Resolved (was: Patch Available) Issue resolved by pull request

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

Gwen Shapira created KAFKA-3421: --- Summary: Update docs with new connector features Key: KAFKA-3421 URL: https://issues.apache.org/jira/browse/KAFKA-3421 Project: Kafka Issue Type: Bug

[Reminder] Release Candidate rollout on Monday

Hi Kafka developers and fans, Just a reminder that we are 1.5 US work days before branch cutting. Below are the open blocker. If you have a blocker that you believe should not actually block the release, please move it to the next release (0.10.0.1). We'll make an effort to merge all the

[GitHub] kafka pull request: MINOR: Add InterfaceStability.Unstable annotat...

GitHub user guozhangwang opened a pull request: https://github.com/apache/kafka/pull/1097 MINOR: Add InterfaceStability.Unstable annotations to some Kafka Streams public APIs Also improves Java docs for the Streams high-level DSL. You can merge this pull request into a Git

[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=15200081#comment-15200081 ] Jason Gustafson commented on KAFKA-3409: I think the only way (2) could happen at the moment is if

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

My problem with per-api is that not all combinations are supported. So the client will need to figure out which "safe" combination to revert to - which is a lot like global numbers, but less linear... On Thu, Mar 17, 2016 at 11:29 AM, Joel Koshy wrote: > @Gwen - yes it did

[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: Reviewer: Gwen Shapira > support exclude.internal.topics in new consumer >

[jira] [Commented] (KAFKA-1215) Rack-Aware replica assignment option

[ https://issues.apache.org/jira/browse/KAFKA-1215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15201709#comment-15201709 ] Jun Rao commented on KAFKA-1215: [~allenxwang], could you also update the changes to ZK structure in

[jira] [Updated] (KAFKA-3379) Update tools relying on old producer to use new producer.

[ https://issues.apache.org/jira/browse/KAFKA-3379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish K Singh updated KAFKA-3379: -- Affects Version/s: 0.10.0.0 > Update tools relying on old producer to use new producer. >

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

I dont really see how first checking if the broker supports a certain set of API versions is so much more complex than calling the same set of API versions during operation? The only difference is that without the check we might only make it halfway through, i.e., being able to join a group,

[GitHub] kafka pull request: MINOR: KAFKA-3373 follow-up, a few val renames...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1072 --- 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-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=15200493#comment-15200493 ] Jun Rao commented on KAFKA-3383: [~becket_qin], do you know why the response parsing will fail? >

  1   2   3   >