How to submit a KIP?

Hi, I have created a Jira Issue - https://issues.apache.org/jira/browse/KAFKA-3663  and was wondering what is the next step?Should I create a KIP? If so, how do I do that, as I do not have permissions to do that. Thanks,Jayesh Thakrar

[jira] [Updated] (KAFKA-3144) report members with no assigned partitions in ConsumerGroupCommand

[ https://issues.apache.org/jira/browse/KAFKA-3144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vahid Hashemian updated KAFKA-3144: --- Status: Patch Available (was: Open) > report members with no assigned partitions in

[jira] [Commented] (KAFKA-3673) Connect tests dont handle concurrent config changes

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

[GitHub] kafka pull request: KAFKA-3673: Connect tests don't handle concurr...

GitHub user Ishiihara opened a pull request: https://github.com/apache/kafka/pull/1340 KAFKA-3673: Connect tests don't handle concurrent config changes You can merge this pull request into a Git repository by running: $ git pull https://github.com/Ishiihara/kafka

[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=15275027#comment-15275027 ] Ismael Juma commented on KAFKA-1981: I don't see your account, are you sure you created an account for

[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=15275024#comment-15275024 ] Eric Wasserman commented on KAFKA-1981: --- I think it must be the same as my Jira user: ewasserman >

[jira] [Updated] (KAFKA-3673) Connect tests dont handle concurrent config changes

[ https://issues.apache.org/jira/browse/KAFKA-3673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liquan Pei updated KAFKA-3673: -- Description: [INFO - 2016-04-28 18:42:45,346 - runner - log - lineno:221]: SerialTestRunner:

[jira] [Created] (KAFKA-3673) Connect tests dont handle concurrent config changes

Liquan Pei created KAFKA-3673: - Summary: Connect tests dont handle concurrent config changes Key: KAFKA-3673 URL: https://issues.apache.org/jira/browse/KAFKA-3673 Project: Kafka Issue Type: Bug

[jira] [Updated] (KAFKA-3670) ControlledShutdownLeaderSelector should pick the preferred replica as the new leader, if possible

[ https://issues.apache.org/jira/browse/KAFKA-3670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3670: --- Reviewer: Jun Rao Status: Patch Available (was: In Progress) >

[GitHub] kafka pull request: HOTFIX: Ensure connector target state changes ...

GitHub user hachikuji opened a pull request: https://github.com/apache/kafka/pull/1339 HOTFIX: Ensure connector target state changes propagated to worker You can merge this pull request into a Git repository by running: $ git pull https://github.com/hachikuji/kafka

[jira] [Commented] (KAFKA-3670) ControlledShutdownLeaderSelector should pick the preferred replica as the new leader, if possible

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

[GitHub] kafka pull request: KAFKA-3670; ControlledShutdownLeaderSelector s...

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/1338 KAFKA-3670; ControlledShutdownLeaderSelector should pick the preferred replica as the new leader, if possible You can merge this pull request into a Git repository by running: $ git pull

[jira] [Commented] (KAFKA-3312) Add a offsets methods to ZkUtils and replace relevant usages

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

[jira] [Commented] (KAFKA-3312) Add a offsets methods to ZkUtils and replace relevant usages

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

[GitHub] kafka pull request: KAFKA-3312: Add utility offset methods to ZkUt...

GitHub user vahidhashemian reopened a pull request: https://github.com/apache/kafka/pull/1025 KAFKA-3312: Add utility offset methods to ZkUtils Create utility getOffset(...) and updateOffset(...) methods to replace readData(...), readDataMaybeNull(...) and updatePersistentPath(...)

[GitHub] kafka pull request: KAFKA-3312: Add utility offset methods to ZkUt...

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

[jira] [Commented] (KAFKA-3587) LogCleaner fails due to incorrect offset map computation on a replica

[ https://issues.apache.org/jira/browse/KAFKA-3587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15274977#comment-15274977 ] Edoardo Comar commented on KAFKA-3587: -- [~junrao] the difference between option 1 and option 2 is

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

Hi Mark, Thanks for the email. First of all, I'd like to mention that the `Unstable` annotation has been removed from the new Java consumer in 0.10, so you can expect compatibility from now on. We definitely understand that compatibility is important for widespread adoption. The current PR for

[jira] [Commented] (KAFKA-3565) Producer's throughput lower with compressed data after KIP-31/32

[ https://issues.apache.org/jira/browse/KAFKA-3565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15274969#comment-15274969 ] Jiangjie Qin commented on KAFKA-3565: - [~junrao] I didn't have time to run the test yet. I will

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

I understand and empathize with both sides of the story here. I spend some of my time on Spark and Kafka integration and I have cc'ed Cody who's been working on new Kafka consumer API with Spark Streaming. Spark hasn't merged the new Kafka consumer API integration, the PR is up and we, as a

[jira] [Created] (KAFKA-3672) Introduce globally consistent checkpoint in Kafka Streams

Guozhang Wang created KAFKA-3672: Summary: Introduce globally consistent checkpoint in Kafka Streams Key: KAFKA-3672 URL: https://issues.apache.org/jira/browse/KAFKA-3672 Project: Kafka

[jira] [Commented] (KAFKA-3565) Producer's throughput lower with compressed data after KIP-31/32

[ https://issues.apache.org/jira/browse/KAFKA-3565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15274917#comment-15274917 ] Jun Rao commented on KAFKA-3565: [~becket_qin], any new findings on the consumer performance? Thanks. >

[jira] [Work started] (KAFKA-3670) ControlledShutdownLeaderSelector should pick the preferred replica as the new leader, if possible

[ https://issues.apache.org/jira/browse/KAFKA-3670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-3670 started by Ismael Juma. -- > ControlledShutdownLeaderSelector should pick the preferred replica as the new >

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

See Changes: [cshapi] Minor: added description for lag in consumer group command [ismael] KAFKA-3669; Add secondary constructor for KafkaConfig with a default [ismael] KAFKA-3655; awaitFlushCompletion() in RecordAccumulator should

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

See Changes: [ismael] KAFKA-3669; Add secondary constructor for KafkaConfig with a default [ismael] KAFKA-3655; awaitFlushCompletion() in RecordAccumulator should always -- [...truncated 8747

[GitHub] kafka pull request: KAFKA-3658: Validate retention period be longe...

GitHub user guozhangwang opened a pull request: https://github.com/apache/kafka/pull/1337 KAFKA-3658: Validate retention period be longer than window size You can merge this pull request into a Git repository by running: $ git pull https://github.com/guozhangwang/kafka K3658

[jira] [Commented] (KAFKA-3144) report members with no assigned partitions in ConsumerGroupCommand

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

[GitHub] kafka pull request: KAFKA-3144: Report members with no assigned pa...

GitHub user vahidhashemian opened a pull request: https://github.com/apache/kafka/pull/1336 KAFKA-3144: Report members with no assigned partitions in ConsumerGroupCommand This PR makes a couple of enhancements to the `--describe` option of `ConsumerGroupCommand`: 1. Listing

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

See Changes: [ismael] KAFKA-3669; Add secondary constructor for KafkaConfig with a default [ismael] KAFKA-3655; awaitFlushCompletion() in RecordAccumulator should always -- [...truncated 2154

Re: KIP-57: Interoperable LZ4 Framing

On Fri, May 6, 2016 at 11:07 PM, Dana Powers wrote: > Updated: > https://cwiki.apache.org/confluence/display/KAFKA/KIP-57+-+Interoperable+LZ4+Framing > > Should I restart the vote? > I think the update is small enough that we don't need to restart the vote. Ismael

Re: KIP-57: Interoperable LZ4 Framing

Ok -- removed Public Interfaces discussion. It should be up to date w/ PR review comments now. -Dana On Fri, May 6, 2016 at 2:15 PM, Ismael Juma wrote: > One more suggestion Dana, I would remove the "Public interfaces" section as > those classes are not actually public (only

Re: KIP-57: Interoperable LZ4 Framing

Updated: https://cwiki.apache.org/confluence/display/KAFKA/KIP-57+-+Interoperable+LZ4+Framing Should I restart the vote? -Dana On Fri, May 6, 2016 at 2:12 PM, Ismael Juma wrote: > On Sun, May 1, 2016 at 3:57 AM, Dana Powers wrote: >> >> > 2. We're

[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=15274757#comment-15274757 ] Ismael Juma commented on KAFKA-1981: [~ewasserman], if you give me your wiki id, I can give you the

[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=15274751#comment-15274751 ] Eric Wasserman commented on KAFKA-1981: --- I attached a KIP to this Jira ticket as I don't have

[jira] [Commented] (KAFKA-3669) Add secondary constructor for KafkaConfig with a default value for doLog

[ https://issues.apache.org/jira/browse/KAFKA-3669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15274744#comment-15274744 ] Mark Grover commented on KAFKA-3669: Thanks [~ijuma]! > Add secondary constructor for KafkaConfig

Re: [VOTE] KIP-57: Interoperable LZ4 Framing

+1 (assuming the changes I mentioned in the discuss thread are incorporated) Ismael On Thu, May 5, 2016 at 1:13 AM, Jun Rao wrote: > Thanks for the response. +1 on the KIP. > > Jun > > On Thu, Apr 28, 2016 at 9:01 AM, Dana Powers > wrote: > > > Sure

Re: KIP-57: Interoperable LZ4 Framing

One more suggestion Dana, I would remove the "Public interfaces" section as those classes are not actually public (only the classes with Javadoc are public: https://kafka.apache.org/090/javadoc/index.html) and the information in the KIP is a bit stale when compared to the PR. Ismael On Fri, May

Re: KIP-57: Interoperable LZ4 Framing

On Sun, May 1, 2016 at 3:57 AM, Dana Powers wrote: > > > 2. We're completely disabling checksumming of the compressed payload on > > consumption. Normally you'd want to validate each level of framing for > > correct end-to-end validation. You could still do this (albeit

[jira] [Updated] (KAFKA-3587) LogCleaner fails due to incorrect offset map computation on a replica

[ https://issues.apache.org/jira/browse/KAFKA-3587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3587: --- Fix Version/s: 0.10.0.0 > LogCleaner fails due to incorrect offset map computation on a replica >

[jira] [Resolved] (KAFKA-3655) awaitFlushCompletion() in RecordAccumulator should always decrement flushesInProgress count.

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

[jira] [Commented] (KAFKA-3655) awaitFlushCompletion() in RecordAccumulator should always decrement flushesInProgress count.

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

[GitHub] kafka pull request: KAFKA-3655; awaitFlushCompletion() in RecordAc...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1315 --- 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-3669) Add secondary constructor for KafkaConfig with a default value for doLog

[ https://issues.apache.org/jira/browse/KAFKA-3669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3669: --- Assignee: Mark Grover > Add secondary constructor for KafkaConfig with a default value for doLog >

[jira] [Updated] (KAFKA-3669) Add secondary constructor for KafkaConfig with a default value for doLog

[ https://issues.apache.org/jira/browse/KAFKA-3669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3669: --- Affects Version/s: (was: 0.11.0.0) > Add secondary constructor for KafkaConfig with a default

[jira] [Commented] (KAFKA-3669) Add secondary constructor for KafkaConfig with a default value for doLog

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

[GitHub] kafka pull request: KAFKA-3669: Add secondary constructor for Kafk...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1334 --- 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] [Work started] (KAFKA-3671) Topics should not be in common ConnectorConfig definitions

[ https://issues.apache.org/jira/browse/KAFKA-3671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-3671 started by Liquan Pei. - > Topics should not be in common ConnectorConfig definitions >

[jira] [Updated] (KAFKA-3671) Topics should not be in common ConnectorConfig definitions

[ https://issues.apache.org/jira/browse/KAFKA-3671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liquan Pei updated KAFKA-3671: -- Summary: Topics should not be in common ConnectorConfig definitions (was: topics should not be in

[jira] [Created] (KAFKA-3671) topics should not be in common ConnectorConfig definitions

Liquan Pei created KAFKA-3671: - Summary: topics should not be in common ConnectorConfig definitions Key: KAFKA-3671 URL: https://issues.apache.org/jira/browse/KAFKA-3671 Project: Kafka Issue

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

See Changes: [cshapi] Minor: added description for lag in consumer group command -- [...truncated 33 lines...] Building project 'core' with Scala version 2.10.6 Build file

[jira] [Assigned] (KAFKA-3670) ControlledShutdownLeaderSelector should pick the preferred replica as the new leader, if possible

[ https://issues.apache.org/jira/browse/KAFKA-3670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reassigned KAFKA-3670: -- Assignee: Ismael Juma > ControlledShutdownLeaderSelector should pick the preferred replica as

[jira] [Commented] (KAFKA-3587) LogCleaner fails due to incorrect offset map computation on a replica

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

[GitHub] kafka pull request: KAFKA-3587 Improve logic to build offsetMap in...

Github user alekar closed the pull request at: https://github.com/apache/kafka/pull/1329 --- 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: Minor: added description for lag in consumer g...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1320 --- 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-3587) LogCleaner fails due to incorrect offset map computation on a replica

[ https://issues.apache.org/jira/browse/KAFKA-3587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15274677#comment-15274677 ] Jun Rao commented on KAFKA-3587: [~ecomar], yes, what you described matches my expectation. Now, I am not

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

See Changes: [me] KAFKA-3592: System test - configurable paths -- [...truncated 6393 lines...] org.apache.kafka.connect.storage.KafkaStatusBackingStoreTest > readConnectorState PASSED

[jira] [Commented] (KAFKA-3587) LogCleaner fails due to incorrect offset map computation on a replica

[ https://issues.apache.org/jira/browse/KAFKA-3587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15274622#comment-15274622 ] Edoardo Comar commented on KAFKA-3587: -- [~junrao] thanks for your observation

[jira] [Commented] (KAFKA-3669) Add secondary constructor for KafkaConfig with a default value for doLog

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

[GitHub] kafka pull request: KAFKA-3669: Add secondary constructor for Kafk...

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

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

See Changes: [me] KAFKA-3592: System test - configurable paths -- [...truncated 4441 lines...] kafka.admin.AdminRackAwareTest > testAssignmentWithRackAware PASSED

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

See Changes: [me] KAFKA-3592: System test - configurable paths -- [...truncated 1627 lines...] kafka.log.LogTest > testLogRolls PASSED kafka.log.LogTest > testMessageSizeCheck PASSED

[jira] [Created] (KAFKA-3670) ControlledShutdownLeaderSelector should pick the preferred replica as the new leader, if possible

Jun Rao created KAFKA-3670: -- Summary: ControlledShutdownLeaderSelector should pick the preferred replica as the new leader, if possible Key: KAFKA-3670 URL: https://issues.apache.org/jira/browse/KAFKA-3670

Re: KAFKA-3112

KAFKA-2657 is unresolved so you can safely assume it hasn't been fixed yet. On Fri, 6 May 2016 at 07:38 Raj Tanneru wrote: > Yeah it is a duplicate of KAFKA-2657. The question is how to check / know > if it is merged to 0.9.0.1 release. What are the options that I have if

[jira] [Commented] (KAFKA-3669) Add secondary constructor for KafkaConfig with a default value for doLog

[ https://issues.apache.org/jira/browse/KAFKA-3669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15274554#comment-15274554 ] Mark Grover commented on KAFKA-3669: https://github.com/apache/kafka/pull/1333 for 0.10 branch and

[GitHub] kafka pull request: KAFKA-3669: Add secondary constructor for Kafk...

GitHub user markgrover opened a pull request: https://github.com/apache/kafka/pull/1334 KAFKA-3669: Add secondary constructor for KafkaConfig with a default … …value for doLog You can merge this pull request into a Git repository by running: $ git pull

[jira] [Commented] (KAFKA-3669) Add secondary constructor for KafkaConfig with a default value for doLog

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

[jira] [Commented] (KAFKA-3669) Add secondary constructor for KafkaConfig with a default value for doLog

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

[GitHub] kafka pull request: KAFKA-3669: Add secondary constructor for Kafk...

GitHub user markgrover opened a pull request: https://github.com/apache/kafka/pull/1333 KAFKA-3669: Add secondary constructor for KafkaConfig with a default … …value for doLog You can merge this pull request into a Git repository by running: $ git pull

[jira] [Commented] (KAFKA-3587) LogCleaner fails due to incorrect offset map computation on a replica

[ https://issues.apache.org/jira/browse/KAFKA-3587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15274534#comment-15274534 ] Manas Alekar commented on KAFKA-3587: - [~junrao] During cleaning the offset stored in offsetMap is

[jira] [Commented] (KAFKA-3587) LogCleaner fails due to incorrect offset map computation on a replica

[ https://issues.apache.org/jira/browse/KAFKA-3587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15274526#comment-15274526 ] Jun Rao commented on KAFKA-3587: [~alekar], note that when copying retained messages to new log segments,

[jira] [Commented] (KAFKA-3144) report members with no assigned partitions in ConsumerGroupCommand

[ https://issues.apache.org/jira/browse/KAFKA-3144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15274522#comment-15274522 ] Vahid Hashemian commented on KAFKA-3144: [~junrao] It seems the reason for this is groups with no

[jira] [Commented] (KAFKA-3587) LogCleaner fails due to incorrect offset map computation on a replica

[ https://issues.apache.org/jira/browse/KAFKA-3587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15274513#comment-15274513 ] Manas Alekar commented on KAFKA-3587: - [~guozhang] Like your idea, I'll wait for us to decide on what

[jira] [Commented] (KAFKA-3587) LogCleaner fails due to incorrect offset map computation on a replica

[ https://issues.apache.org/jira/browse/KAFKA-3587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15274500#comment-15274500 ] Manas Alekar commented on KAFKA-3587: - The issue with just building the map till it is full as

[jira] [Issue Comment Deleted] (KAFKA-3587) LogCleaner fails due to incorrect offset map computation on a replica

[ https://issues.apache.org/jira/browse/KAFKA-3587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manas Alekar updated KAFKA-3587: Comment: was deleted (was: The issue with just building the map till it is full as proposed in pull

[jira] [Resolved] (KAFKA-3592) System tests - don't hardcode paths to scripts

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

Re: [VOTE] 0.10.0.0 RC3

Thanks, Gwen. I was testing RC2 with Spark Streaming and found an issue that has a minor fix. I think this issue exists with RC3 as well: https://issues.apache.org/jira/browse/KAFKA-3669 On Thu, May 5, 2016 at 1:46 PM, Gwen Shapira wrote: > Hello Kafka users, developers and

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

See Changes: [ismael] KAFKA-3666; Update links for new consumer API [wangguoz] KAFKA-3616: Make kafka producers/consumers injectable for KafkaStreams -- [...truncated 459 lines...]

[jira] [Commented] (KAFKA-3592) System tests - don't hardcode paths to scripts

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

[GitHub] kafka pull request: KAFKA-3592: System test - configurable paths

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1245 --- 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-3587) LogCleaner fails due to incorrect offset map computation on a replica

[ https://issues.apache.org/jira/browse/KAFKA-3587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15274483#comment-15274483 ] Manas Alekar commented on KAFKA-3587: - The issue with just building the map till it is full as

[jira] [Created] (KAFKA-3669) Add secondary constructor for KafkaConfig with a default value for doLog

Mark Grover created KAFKA-3669: -- Summary: Add secondary constructor for KafkaConfig with a default value for doLog Key: KAFKA-3669 URL: https://issues.apache.org/jira/browse/KAFKA-3669 Project: Kafka

[jira] [Commented] (KAFKA-3664) When subscription set changes on new consumer, the partitions may be removed without offset being committed.

[ https://issues.apache.org/jira/browse/KAFKA-3664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15274470#comment-15274470 ] Jiangjie Qin commented on KAFKA-3664: - [~hachikuji] I am not sure. If we still return the partitions

[jira] [Commented] (KAFKA-3587) LogCleaner fails due to incorrect offset map computation on a replica

[ https://issues.apache.org/jira/browse/KAFKA-3587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15274454#comment-15274454 ] Guozhang Wang commented on KAFKA-3587: -- Oops, accidentally deleted my previous comment, re-posting

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

See

[jira] [Commented] (KAFKA-3587) LogCleaner fails due to incorrect offset map computation on a replica

[ https://issues.apache.org/jira/browse/KAFKA-3587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15274442#comment-15274442 ] Jun Rao commented on KAFKA-3587: Yes, let's first agree upon the best approach on the jira. It would be

[jira] [Issue Comment Deleted] (KAFKA-3587) LogCleaner fails due to incorrect offset map computation on a replica

[ https://issues.apache.org/jira/browse/KAFKA-3587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-3587: - Comment: was deleted (was: We have multiple PRs for this JIRA now, and I suggest we'd better

[jira] [Commented] (KAFKA-3587) LogCleaner fails due to incorrect offset map computation on a replica

[ https://issues.apache.org/jira/browse/KAFKA-3587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15274418#comment-15274418 ] Guozhang Wang commented on KAFKA-3587: -- We have multiple PRs for this JIRA now, and I suggest we'd

[jira] [Commented] (KAFKA-3664) When subscription set changes on new consumer, the partitions may be removed without offset being committed.

[ https://issues.apache.org/jira/browse/KAFKA-3664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15274390#comment-15274390 ] Jason Gustafson commented on KAFKA-3664: [~becket_qin] Thanks for the report. After the topic

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

See Changes: [ismael] KAFKA-3666; Update links for new consumer API [wangguoz] KAFKA-3616: Make kafka producers/consumers injectable for KafkaStreams -- [...truncated 7829 lines...]

[jira] [Commented] (KAFKA-3587) LogCleaner fails due to incorrect offset map computation on a replica

[ https://issues.apache.org/jira/browse/KAFKA-3587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15274372#comment-15274372 ] Jun Rao commented on KAFKA-3587: [~ecomar], thanks for the explanation. I am not sure about your first

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

See Changes: [ismael] KAFKA-3666; Update links for new consumer API -- [...truncated 8691 lines...] org.apache.kafka.connect.storage.KafkaStatusBackingStoreTest > readConnectorState PASSED

[jira] [Assigned] (KAFKA-3664) When subscription set changes on new consumer, the partitions may be removed without offset being committed.

[ https://issues.apache.org/jira/browse/KAFKA-3664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vahid Hashemian reassigned KAFKA-3664: -- Assignee: Vahid Hashemian > When subscription set changes on new consumer, the

[jira] [Updated] (KAFKA-3616) Make kafka producers/consumers injectable for KafkaStreams

[ https://issues.apache.org/jira/browse/KAFKA-3616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-3616: - Fix Version/s: (was: 0.10.1.0) 0.10.0.0 > Make kafka producers/consumers

[jira] [Updated] (KAFKA-3616) Make kafka producers/consumers injectable for KafkaStreams

[ https://issues.apache.org/jira/browse/KAFKA-3616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-3616: - Resolution: Fixed Status: Resolved (was: Patch Available) > Make kafka

[jira] [Commented] (KAFKA-3616) Make kafka producers/consumers injectable for KafkaStreams

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

[GitHub] kafka pull request: KAFKA-3616: Make kafka producers/consumers inj...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1264 --- 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: list of challenges encountered using 0.9.0.1

Thanks for the updates, Jason. Let me know if you have questions about use case that brings up any of these scenarios. On Thu, May 5, 2016 at 7:34 PM, Jason Gustafson wrote: > Hey Cliff, > > Thanks for the feedback. A few select comments: > > 1. The new Java KafkaConsumer

[jira] [Resolved] (KAFKA-3666) Update new Consumer API links in the docs

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

[jira] [Commented] (KAFKA-3666) Update new Consumer API links in the docs

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

[GitHub] kafka pull request: KAFKA-3666: Update links for new consumer API

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

  1   2   >