Re: KAFKA-3112

It said this is a duplication. This is the https://issues.apache.org/jira/browse/KAFKA-2657 that KAKFA-3112 duplicates to. On Thu, 5 May 2016 at 22:13 Raj Tanneru wrote: > > Hi All, > Does anyone know if KAFKA-3112 is merged to 0.9.0.1? Is there a place to > check which version has this fix? Jir

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

See Changes: [me] KAFKA-3627: consumer fails to execute delayed tasks in poll when records -- [...truncated 2968 lines...] kafka.integration.SslTopicMetadataTest > testAutoCreateTopicWithCollis

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

See Changes: [me] KAFKA-3627: consumer fails to execute delayed tasks in poll when records -- [...truncated 6384 lines...] org.apache.kafka.connect.runtime.distributed.DistributedHerderTest > t

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

GitHub user alekar opened a pull request: https://github.com/apache/kafka/pull/1329 KAFKA-3587 Improve logic to build offsetMap in log.Cleaner. You can merge this pull request into a Git repository by running: $ git pull https://github.com/alekar/kafka trunk Alternatively you

[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&focusedCommentId=15273777#comment-15273777 ] ASF GitHub Bot commented on KAFKA-3587: --- GitHub user alekar opened a pull request:

[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&focusedCommentId=15273821#comment-15273821 ] Edoardo Comar commented on KAFKA-3587: -- [~junrao] I was thinking of two possible opti

[jira] [Created] (KAFKA-3665) Default ssl.endpoint.identification.algorithm should be https

Ismael Juma created KAFKA-3665: -- Summary: Default ssl.endpoint.identification.algorithm should be https Key: KAFKA-3665 URL: https://issues.apache.org/jira/browse/KAFKA-3665 Project: Kafka Issu

[jira] [Updated] (KAFKA-3665) Default ssl.endpoint.identification.algorithm should be https

[ https://issues.apache.org/jira/browse/KAFKA-3665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3665: --- Description: The default `ssl.endpoint.identification.algorithm` is `null` which is not a secure defa

[GitHub] kafka pull request: KAFKA-3665; Default ssl.endpoint.identificatio...

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/1330 KAFKA-3665; Default ssl.endpoint.identification.algorithm should be https You can merge this pull request into a Git repository by running: $ git pull https://github.com/ijuma/kafka kafka-3665-

[jira] [Commented] (KAFKA-3665) Default ssl.endpoint.identification.algorithm should be https

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

[jira] [Updated] (KAFKA-3665) Default ssl.endpoint.identification.algorithm should be https

[ https://issues.apache.org/jira/browse/KAFKA-3665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3665: --- Status: Patch Available (was: Open) > Default ssl.endpoint.identification.algorithm should be https >

[jira] [Commented] (KAFKA-3665) Default ssl.endpoint.identification.algorithm should be https

[ https://issues.apache.org/jira/browse/KAFKA-3665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15273902#comment-15273902 ] Ismael Juma commented on KAFKA-3665: Thoughts [~rsivaram], [~junrao], [~gwenshap], [~h

[jira] [Commented] (KAFKA-3665) Default ssl.endpoint.identification.algorithm should be https

[ https://issues.apache.org/jira/browse/KAFKA-3665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15273917#comment-15273917 ] Rajini Sivaram commented on KAFKA-3665: --- [~ijuma] I agree that secure installations

[jira] [Commented] (KAFKA-3665) Default ssl.endpoint.identification.algorithm should be https

[ https://issues.apache.org/jira/browse/KAFKA-3665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15273931#comment-15273931 ] Ismael Juma commented on KAFKA-3665: Thanks [~rsivaram]. I agree that this could catch

[jira] [Resolved] (KAFKA-725) Broker Exception: Attempt to read with a maximum offset less than start offset

[ https://issues.apache.org/jira/browse/KAFKA-725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-725. --- Resolution: Fixed [~guozhang]'s PR was merged to trunk and 0.10. > Broker Exception: Attempt to read w

[jira] [Commented] (KAFKA-3665) Default ssl.endpoint.identification.algorithm should be https

[ https://issues.apache.org/jira/browse/KAFKA-3665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15274001#comment-15274001 ] Ryan P commented on KAFKA-3665: --- [~ijuma], just a nit but [RFC 6125|https://tools.ietf.org/s

[jira] [Commented] (KAFKA-3665) Default ssl.endpoint.identification.algorithm should be https

[ https://issues.apache.org/jira/browse/KAFKA-3665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15274012#comment-15274012 ] Ismael Juma commented on KAFKA-3665: [~Ryan P], I agree that this would be better. The

[jira] [Created] (KAFKA-3666) Update offset checking example in the docs

Dustin Cote created KAFKA-3666: -- Summary: Update offset checking example in the docs Key: KAFKA-3666 URL: https://issues.apache.org/jira/browse/KAFKA-3666 Project: Kafka Issue Type: Improvement

[jira] [Commented] (KAFKA-3665) Default ssl.endpoint.identification.algorithm should be https

[ https://issues.apache.org/jira/browse/KAFKA-3665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15274035#comment-15274035 ] Ryan P commented on KAFKA-3665: --- [~ijuma], I can absolutely do that. Would you like me to

[jira] [Commented] (KAFKA-3665) Default ssl.endpoint.identification.algorithm should be https

[ https://issues.apache.org/jira/browse/KAFKA-3665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15274052#comment-15274052 ] Ismael Juma commented on KAFKA-3665: [~Ryan P], that sounds great. The reason why I wa

[jira] [Updated] (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 ] Dustin Cote updated KAFKA-3666: --- Summary: Update new Consumer API links in the docs (was: Update offset checking example in the docs)

[jira] [Commented] (KAFKA-3666) Update offset checking example in the docs

[ https://issues.apache.org/jira/browse/KAFKA-3666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15274090#comment-15274090 ] Dustin Cote commented on KAFKA-3666: After looking at the docs in trunk, it looks like

[jira] [Updated] (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 ] Dustin Cote updated KAFKA-3666: --- Description: New Consumer API links in the docs point to the initial proposed design doc. This should

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

GitHub user cotedm opened a pull request: https://github.com/apache/kafka/pull/1331 Update links for new consumer API Pull request to update the consumer API links in the docs. You can merge this pull request into a Git repository by running: $ git pull https://github.com/coted

[jira] [Created] (KAFKA-3667) Improve Section 7.2 Encryption and Authentication using SSL to include proper hostname verification configuration

Ryan P created KAFKA-3667: - Summary: Improve Section 7.2 Encryption and Authentication using SSL to include proper hostname verification configuration Key: KAFKA-3667 URL: https://issues.apache.org/jira/browse/KAFKA-3667

Re: KAFKA-3112

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 I need this fix. How can I get patch for this on 0.8.2.1? Sent from my iPhone > On May 6, 2016, at 12:06 AM, tao xiao wrote: > > It said this is a d

[jira] [Updated] (KAFKA-3667) Improve Section 7.2 Encryption and Authentication using SSL to include proper hostname verification configuration

[ https://issues.apache.org/jira/browse/KAFKA-3667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryan P updated KAFKA-3667: -- Description: Kafka's documentation should include additional guidance on how to properly enable SSL with hostna

[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&focusedCommentId=15274155#comment-15274155 ] Dustin Cote commented on KAFKA-3666: Leaving the github link here since the PR didn't

[jira] [Created] (KAFKA-3668) Unable to authenticate Kafka broker to secured Zookeeper

Alex created KAFKA-3668: --- Summary: Unable to authenticate Kafka broker to secured Zookeeper Key: KAFKA-3668 URL: https://issues.apache.org/jira/browse/KAFKA-3668 Project: Kafka Issue Type: Bug Affe

[jira] [Commented] (KAFKA-3665) Default ssl.endpoint.identification.algorithm should be https

[ https://issues.apache.org/jira/browse/KAFKA-3665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15274195#comment-15274195 ] Jun Rao commented on KAFKA-3665: Thanks for the patch. A couple of questions. 1. Is the r

[GitHub] kafka pull request: KAFKA-3587: LogCleaner fails due to incorrect ...

GitHub user mimaison opened a pull request: https://github.com/apache/kafka/pull/1332 KAFKA-3587: LogCleaner fails due to incorrect offset map computation … Removed the over pessimistic require and instead attempt to fill the dedup buffer. Use the (only) map until full; this m

[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&focusedCommentId=15274201#comment-15274201 ] ASF GitHub Bot commented on KAFKA-3587: --- GitHub user mimaison opened a pull request:

[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&focusedCommentId=15274204#comment-15274204 ] Edoardo Comar commented on KAFKA-3587: -- For clarity, [~mimaison] PR https://github.co

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

[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&focusedCommentId=15274215#comment-15274215 ] ASF GitHub Bot commented on KAFKA-3666: --- Github user asfgit closed the pull request

[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 [https://github

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 doesn’t have a method

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

[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&focusedCommentId=15274256#comment-15274256 ] ASF GitHub Bot commented on KAFKA-3616: --- Github user asfgit closed the pull request

[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 producers/consumer

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

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

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 or

[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&focusedCommentId=15274372#comment-15274372 ] Jun Rao commented on KAFKA-3587: [~ecomar], thanks for the explanation. I am not sure abou

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...] org.apache.

[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&focusedCommentId=15274390#comment-15274390 ] Jason Gustafson commented on KAFKA-3664: [~becket_qin] Thanks for the report. Afte

[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&focusedCommentId=15274418#comment-15274418 ] Guozhang Wang commented on KAFKA-3587: -- We have multiple PRs for this JIRA now, and I

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

[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&focusedCommentId=15274442#comment-15274442 ] Jun Rao commented on KAFKA-3587: Yes, let's first agree upon the best approach on the jira

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&focusedCommentId=15274454#comment-15274454 ] Guozhang Wang commented on KAFKA-3587: -- Oops, accidentally deleted my previous commen

[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&focusedCommentId=15274470#comment-15274470 ] Jiangjie Qin commented on KAFKA-3664: - [~hachikuji] I am not sure. If we still return

[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-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&focusedCommentId=15274483#comment-15274483 ] Manas Alekar commented on KAFKA-3587: - The issue with just building the map till it is

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

[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&focusedCommentId=15274486#comment-15274486 ] ASF GitHub Bot commented on KAFKA-3592: --- Github user asfgit closed the pull request

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...] kafka.coordi

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 client-developers, >

[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

[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] [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&focusedCommentId=15274500#comment-15274500 ] Manas Alekar commented on KAFKA-3587: - The issue with just building the map till it 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&focusedCommentId=15274513#comment-15274513 ] Manas Alekar commented on KAFKA-3587: - [~guozhang] Like your idea, I'll wait for us to

[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&focusedCommentId=15274522#comment-15274522 ] Vahid Hashemian commented on KAFKA-3144: [~junrao] It seems the reason for this 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&focusedCommentId=15274526#comment-15274526 ] Jun Rao commented on KAFKA-3587: [~alekar], note that when copying retained messages to ne

[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&focusedCommentId=15274534#comment-15274534 ] Manas Alekar commented on KAFKA-3587: - [~junrao] During cleaning the offset stored in

[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 https://github.com/ma

[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&focusedCommentId=15274544#comment-15274544 ] ASF GitHub Bot commented on KAFKA-3669: --- GitHub user markgrover opened a pull reques

[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 https://github.com/ma

[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&focusedCommentId=15274552#comment-15274552 ] ASF GitHub Bot commented on KAFKA-3669: --- GitHub user markgrover opened a pull reques

[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&focusedCommentId=15274554#comment-15274554 ] Mark Grover commented on KAFKA-3669: https://github.com/apache/kafka/pull/1333 for 0.1

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 I > need this fix. How

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

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 kafka.log

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 kafka.admin.AdminRackAwareTest

[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

[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&focusedCommentId=15274591#comment-15274591 ] ASF GitHub Bot commented on KAFKA-3669: --- Github user markgrover closed the pull requ

[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&focusedCommentId=15274622#comment-15274622 ] Edoardo Comar commented on KAFKA-3587: -- [~junrao] thanks for your observation https:

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 org.apa

[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&focusedCommentId=15274677#comment-15274677 ] Jun Rao commented on KAFKA-3587: [~ecomar], yes, what you described matches my expectation

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

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

[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&focusedCommentId=15274683#comment-15274683 ] ASF GitHub Bot commented on KAFKA-3587: --- Github user alekar closed the pull request

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

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

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

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

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

[jira] [Resolved] (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 resolved KAFKA-3669. Resolution: Fixed Fix Version/s: 0.10.0.0 Issue resolved by pull request 1334 [https://github

[GitHub] kafka pull request: KAFKA 3671: Move topics to SinkConnectorConfig

GitHub user Ishiihara opened a pull request: https://github.com/apache/kafka/pull/1335 KAFKA 3671: Move topics to SinkConnectorConfig You can merge this pull request into a Git repository by running: $ git pull https://github.com/Ishiihara/kafka sink-connector-config Alternat

[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&focusedCommentId=15274708#comment-15274708 ] ASF GitHub Bot commented on KAFKA-3669: --- Github user asfgit closed the pull request

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

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

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

[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&focusedCommentId=15274720#comment-15274720 ] ASF GitHub Bot commented on KAFKA-3655: --- Github user asfgit closed the pull request

[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 [https://github

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

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 more > weakly) > > by valid

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 6

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 thing. Yes, the substantive change is fixing

  1   2   >