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

See

[jira] [Commented] (KAFKA-4586) Add purgeDataBefore() API in AdminClient

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

[GitHub] kafka pull request #2476: KAFKA-4586; Add purgeDataBefore() API (KIP-107)

GitHub user lindong28 opened a pull request: https://github.com/apache/kafka/pull/2476 KAFKA-4586; Add purgeDataBefore() API (KIP-107) You can merge this pull request into a Git repository by running: $ git pull https://github.com/lindong28/kafka KAFKA-4586 Alternatively you

[jira] [Updated] (KAFKA-4677) Avoid unnecessary task movement across threads during rebalance

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

[jira] [Commented] (KAFKA-4677) Avoid unnecessary task movement across threads during rebalance

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

[GitHub] kafka pull request #2429: KAFKA-4677: Avoid unnecessary task movement across...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2429 --- 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-3944) After the broker restart, fetchers stopped due to a delayed controlled shutdown message

[ https://issues.apache.org/jira/browse/KAFKA-3944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15847898#comment-15847898 ] James Cheng commented on KAFKA-3944: Is this related to KAFKA-1120? > After the broker restart,

[jira] [Updated] (KAFKA-4611) Support custom authentication mechanism

[ https://issues.apache.org/jira/browse/KAFKA-4611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-4611: - Fix Version/s: (was: 0.10.2.0) > Support custom authentication mechanism >

[jira] [Updated] (KAFKA-3302) Pass kerberos keytab and principal as part of client config

[ https://issues.apache.org/jira/browse/KAFKA-3302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-3302: - Fix Version/s: (was: 0.10.2.0) > Pass kerberos keytab and principal as part

[jira] [Updated] (KAFKA-4495) ThreadCache.maybeEvict can become an infinite loop

[ https://issues.apache.org/jira/browse/KAFKA-4495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-4495: - Fix Version/s: (was: 0.10.2.0) > ThreadCache.maybeEvict can become an

[jira] [Updated] (KAFKA-3478) Finer Stream Flow Control

[ https://issues.apache.org/jira/browse/KAFKA-3478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-3478: - Fix Version/s: (was: 0.10.2.0) > Finer Stream Flow Control >

[jira] [Updated] (KAFKA-1332) Add functionality to the offsetsBeforeTime() API

[ https://issues.apache.org/jira/browse/KAFKA-1332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-1332: - Fix Version/s: (was: 0.10.2.0) > Add functionality to the offsetsBeforeTime()

[jira] [Updated] (KAFKA-3262) Make KafkaStreams debugging friendly

[ https://issues.apache.org/jira/browse/KAFKA-3262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-3262: - Fix Version/s: (was: 0.10.2.0) > Make KafkaStreams debugging friendly >

Re: [VOTE] KIP-107 Add purgeDataBefore() API in AdminClient

got it. I missed the message in the middle declaring that the vote passed. On Tue, Jan 31, 2017 at 5:51 PM, Dong Lin wrote: > This thread was been closed on Jan 18. We had more discussion after > Guozhang's feedback on Jan 21. But no major change was made to the KIP > after

Re: [DISCUSS] KIP-112: Handle disk failure for JBOD

Hi all, I am going to initiate the vote If there is no further concern with the KIP. Thanks, Dong On Fri, Jan 27, 2017 at 8:08 PM, radai wrote: > a few extra points: > > 1. broker per disk might also incur more client <--> broker sockets: > suppose every producer

Re: [VOTE] KIP-107 Add purgeDataBefore() API in AdminClient

This thread was been closed on Jan 18. We had more discussion after Guozhang's feedback on Jan 21. But no major change was made to the KIP after the discussion. On Tue, Jan 31, 2017 at 5:47 PM, Dong Lin wrote: > Hey Apurva, > > I think the KIP table in

Re: [VOTE] KIP-107 Add purgeDataBefore() API in AdminClient

Hey Apurva, I think the KIP table in https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Improvement+Proposals has already been updated. Is there anything I missed? Thanks, Dong On Tue, Jan 31, 2017 at 5:45 PM, Apurva Mehta wrote: > Hi Dong, > > It looks like this

Re: [VOTE] KIP-107 Add purgeDataBefore() API in AdminClient

Hi Dong, It looks like this vote passed. Can you close this thread and update the KIP table? Thanks, Apurva On Tue, Jan 24, 2017 at 1:30 PM, Jun Rao wrote: > Hi, Dong, > > The changes sound good to me. Also, thanks for the explanation of returning > a future from

[jira] [Created] (KAFKA-4718) Revisit DSL partitioning assumption for KStream source topics

Matthias J. Sax created KAFKA-4718: -- Summary: Revisit DSL partitioning assumption for KStream source topics Key: KAFKA-4718 URL: https://issues.apache.org/jira/browse/KAFKA-4718 Project: Kafka

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

See Changes: [me] KAFKA-4717: Use absolute paths to files in root directory so all jars -- [...truncated 3567 lines...] kafka.admin.ConfigCommandTest > shouldParseArgumentsForClientsEntityType

[jira] [Commented] (KAFKA-3543) Allow a variant of transform() which can emit multiple values

[ https://issues.apache.org/jira/browse/KAFKA-3543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15847802#comment-15847802 ] Matthias J. Sax commented on KAFKA-3543: [~gfodor] I close this as duplicate. Nevertheless one

[jira] [Resolved] (KAFKA-3543) Allow a variant of transform() which can emit multiple values

[ https://issues.apache.org/jira/browse/KAFKA-3543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax resolved KAFKA-3543. Resolution: Duplicate > Allow a variant of transform() which can emit multiple values >

[jira] [Assigned] (KAFKA-3940) Log should check the return value of dir.mkdirs()

[ https://issues.apache.org/jira/browse/KAFKA-3940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishita Mandhan reassigned KAFKA-3940: - Assignee: (was: Ishita Mandhan) > Log should check the return value of dir.mkdirs()

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

[ https://issues.apache.org/jira/browse/KAFKA-3522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishita Mandhan reassigned KAFKA-3522: - Assignee: (was: Ishita Mandhan) > Consider adding version information into rocksDB

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

[ https://issues.apache.org/jira/browse/KAFKA-3522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15847779#comment-15847779 ] Ishita Mandhan commented on KAFKA-3522: --- [~ewencp]I don't think I'll be able to work on this

[jira] [Assigned] (KAFKA-2544) Replication tools wiki page needs to be updated

[ https://issues.apache.org/jira/browse/KAFKA-2544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishita Mandhan reassigned KAFKA-2544: - Assignee: (was: Ishita Mandhan) > Replication tools wiki page needs to be updated >

[jira] [Assigned] (KAFKA-4320) Log compaction docs update

[ https://issues.apache.org/jira/browse/KAFKA-4320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishita Mandhan reassigned KAFKA-4320: - Assignee: (was: Ishita Mandhan) > Log compaction docs update >

[jira] [Commented] (KAFKA-4717) connect jars are missing LICENSE/NOTICE files

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

[jira] [Updated] (KAFKA-4717) connect jars are missing LICENSE/NOTICE files

[ https://issues.apache.org/jira/browse/KAFKA-4717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-4717: - Resolution: Fixed Fix Version/s: 0.10.1.2 0.10.3.0

[GitHub] kafka pull request #2473: KAFKA-4717: Use absolute paths to files in root di...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2473 --- 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-4686) Null Message payload is shutting down broker

[ https://issues.apache.org/jira/browse/KAFKA-4686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15847751#comment-15847751 ] Jason Gustafson commented on KAFKA-4686: [~rodrigo.saramago] Thanks for the updates. I spotted

[jira] [Resolved] (KAFKA-4612) Simple Kafka Streams app causes "ClassCastException: java.lang.String cannot be cast to [B"

[ https://issues.apache.org/jira/browse/KAFKA-4612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax resolved KAFKA-4612. Resolution: Not A Problem > Simple Kafka Streams app causes "ClassCastException:

[jira] [Commented] (KAFKA-3455) Connect custom processors with the streams DSL

[ https://issues.apache.org/jira/browse/KAFKA-3455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15847718#comment-15847718 ] Matthias J. Sax commented on KAFKA-3455: Just discovering this. I would close as "not a problem".

Re: [DISCUS] consuming messages is polling - is there a reason? new KIP for poll?

Also, have you looked at the use of the max wait time in fetch requests ( fetch.max.wait.ms for the new consumer)? The broker will hold the fetch in purgatory until data is available. Sort of lets you fake a push model. -Jason On Tue, Jan 31, 2017 at 2:29 PM, radai

Re: [DISCUS] consuming messages is polling - is there a reason? new KIP for poll?

minimizing the cost of clients is part of what makes kafka scale. a push model would shift a lot of tracking logic onto the broker. On Tue, Jan 31, 2017 at 2:47 AM, Alexander Binzberger < alexander.binzber...@wingcon.com> wrote: > way it seams like the protocol and the high-level consumer would

[GitHub] kafka pull request #2475: MINOR: Use an explicit `Errors` object when possib...

GitHub user vahidhashemian opened a pull request: https://github.com/apache/kafka/pull/2475 MINOR: Use an explicit `Errors` object when possible instead of a numeric error code You can merge this pull request into a Git repository by running: $ git pull

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

See Changes: [jason] MINOR: Logging improvements in consumer internals -- [...truncated 5326 lines...] kafka.api.SslEndToEndAuthorizationTest > testNoProduceWithDescribeAcl PASSED

[jira] (KAFKA-3959) __consumer_offsets wrong number of replicas at startup

[ https://issues.apache.org/jira/browse/KAFKA-3959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-3959: - Fix Version/s: (was: 0.10.2.0) 0.10.3.0 >

[jira] (KAFKA-4717) connect jars are missing LICENSE/NOTICE files

[ https://issues.apache.org/jira/browse/KAFKA-4717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava reassigned KAFKA-4717: Assignee: Ewen Cheslack-Postava > connect jars are missing LICENSE/NOTICE

[jira] (KAFKA-4717) connect jars are missing LICENSE/NOTICE files

[ https://issues.apache.org/jira/browse/KAFKA-4717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-4717: - Status: Patch Available (was: Open) > connect jars are missing LICENSE/NOTICE

[jira] (KAFKA-4039) Exit Strategy: using exceptions instead of inline invocation of exit/halt

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

[GitHub] kafka pull request #2474: KAFKA-4039: Fix deadlock during shutdown due to lo...

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/2474 KAFKA-4039: Fix deadlock during shutdown due to log truncation not allowed You can merge this pull request into a Git repository by running: $ git pull https://github.com/ijuma/kafka

[jira] (KAFKA-4717) connect jars are missing LICENSE/NOTICE files

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

[GitHub] kafka pull request #2473: KAFKA-4717: Use absolute paths to files in root di...

GitHub user ewencp opened a pull request: https://github.com/apache/kafka/pull/2473 KAFKA-4717: Use absolute paths to files in root directory so all jars include LICENSE and NOTICE files You can merge this pull request into a Git repository by running: $ git pull

[GitHub] kafka pull request #2469: MINOR: Logging improvements in consumer internals

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2469 --- 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] (KAFKA-4689) OffsetValidationTest fails validation with "Current position greater than the total number of consumed records"

[ https://issues.apache.org/jira/browse/KAFKA-4689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-4689: - Priority: Major (was: Blocker) > OffsetValidationTest fails validation with

[jira] (KAFKA-4689) OffsetValidationTest fails validation with "Current position greater than the total number of consumed records"

[ https://issues.apache.org/jira/browse/KAFKA-4689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-4689: - Fix Version/s: (was: 0.10.2.0) > OffsetValidationTest fails validation with

[jira] (KAFKA-4717) connect jars are missing LICENSE/NOTICE files

[ https://issues.apache.org/jira/browse/KAFKA-4717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-4717: - Fix Version/s: 0.10.2.0 > connect jars are missing LICENSE/NOTICE files >

[jira] (KAFKA-4717) connect jars are missing LICENSE/NOTICE files

[ https://issues.apache.org/jira/browse/KAFKA-4717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-4717: - Priority: Blocker (was: Major) > connect jars are missing LICENSE/NOTICE files >

[jira] (KAFKA-4717) connect jars are missing LICENSE/NOTICE files

dan norwood created KAFKA-4717: -- Summary: connect jars are missing LICENSE/NOTICE files Key: KAFKA-4717 URL: https://issues.apache.org/jira/browse/KAFKA-4717 Project: Kafka Issue Type: Bug

[jira] (KAFKA-1610) Local modifications to collections generated from mapValues will be lost

[ https://issues.apache.org/jira/browse/KAFKA-1610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15847355#comment-15847355 ] Mayuresh Gharat commented on KAFKA-1610: [~jozi-k] sure. The patch has been available but we

[jira] (KAFKA-3265) Create Java Admin Client

[ https://issues.apache.org/jira/browse/KAFKA-3265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15847277#comment-15847277 ] Colin P. McCabe edited comment on KAFKA-3265 at 1/31/17 6:50 PM: - I wrote

[jira] (KAFKA-3265) Create Java Admin Client

[ https://issues.apache.org/jira/browse/KAFKA-3265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15847277#comment-15847277 ] Colin P. McCabe edited comment on KAFKA-3265 at 1/31/17 6:49 PM: - I wrote

[jira] (KAFKA-3265) Create Java Admin Client

[ https://issues.apache.org/jira/browse/KAFKA-3265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin P. McCabe reassigned KAFKA-3265: -- Assignee: Colin P. McCabe (was: Grant Henke) > Create Java Admin Client >

[jira] (KAFKA-3265) Create Java Admin Client

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

[GitHub] kafka pull request #2472: KAFKA-3265: Create Java Admin Client

GitHub user cmccabe opened a pull request: https://github.com/apache/kafka/pull/2472 KAFKA-3265: Create Java Admin Client Create a Java AdminClient as described in KAFKA-3265 and KIP-4. Currently it supports getAllGroups, getAllBrokerVersions, deleteTopics, and

[jira] (KAFKA-3265) Create Java Admin Client

[ https://issues.apache.org/jira/browse/KAFKA-3265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15847277#comment-15847277 ] Colin P. McCabe commented on KAFKA-3265: Hi [~granthenke], I wrote a Java AdminClient. Check it

[jira] (KAFKA-4317) RocksDB checkpoint files lost on kill -9

[ https://issues.apache.org/jira/browse/KAFKA-4317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-4317: --- Labels: architecture needs-kip user-experience (was: architecture user-experience) >

[jira] (KAFKA-4317) RocksDB checkpoint files lost on kill -9

[ https://issues.apache.org/jira/browse/KAFKA-4317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy updated KAFKA-4317: -- Status: Patch Available (was: Open) > RocksDB checkpoint files lost on kill -9 >

[jira] (KAFKA-1610) Local modifications to collections generated from mapValues will be lost

[ https://issues.apache.org/jira/browse/KAFKA-1610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15847261#comment-15847261 ] Jozef Koval commented on KAFKA-1610: What is current status of this issue? There has not been any

[jira] (KAFKA-4317) RocksDB checkpoint files lost on kill -9

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

[GitHub] kafka pull request #2471: KAFKA-4317: Checkpoint State Stores on commit/flus...

GitHub user dguy opened a pull request: https://github.com/apache/kafka/pull/2471 KAFKA-4317: Checkpoint State Stores on commit/flush Currently the checkpoint file is deleted at state store initialization and it is only ever written again during a clean shutdown. This can result in

[jira] (KAFKA-2955) Add Prompt to kafka-console-producer

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

[GitHub] kafka pull request #1233: KAFKA-2955; Add a simple ">" prompt to console pro...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1233 --- 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] (KAFKA-2955) Add Prompt to kafka-console-producer

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

[jira] (KAFKA-4711) Change Default unclean.leader.election.enabled from True to False (KIP-106)

[ https://issues.apache.org/jira/browse/KAFKA-4711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15847106#comment-15847106 ] Ismael Juma edited comment on KAFKA-4711 at 1/31/17 4:50 PM: - Duplicate of

[jira] (KAFKA-4623) Change Default unclean.leader.election.enabled from True to False

[ https://issues.apache.org/jira/browse/KAFKA-4623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4623: --- Fix Version/s: 0.11.0.0 > Change Default unclean.leader.election.enabled from True to False >

[jira] (KAFKA-4711) Change Default unclean.leader.election.enabled from True to False (KIP-106)

[ https://issues.apache.org/jira/browse/KAFKA-4711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-4711. Resolution: Duplicate KAFKA-4623. > Change Default unclean.leader.election.enabled from True to

[jira] (KAFKA-4711) Change Default unclean.leader.election.enabled from True to False (KIP-106)

[ https://issues.apache.org/jira/browse/KAFKA-4711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15847098#comment-15847098 ] Sharad commented on KAFKA-4711: --- https://github.com/apache/kafka/pull/2470 > Change Default

[jira] (KAFKA-4623) Change Default unclean.leader.election.enabled from True to False

[ https://issues.apache.org/jira/browse/KAFKA-4623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15847100#comment-15847100 ] Sharad commented on KAFKA-4623: --- https://github.com/apache/kafka/pull/2470 > Change Default

[GitHub] kafka pull request #2470: Kafka-4711 :Change Default unclean.leader.election...

GitHub user sharad-develop opened a pull request: https://github.com/apache/kafka/pull/2470 Kafka-4711 :Change Default unclean.leader.election.enabled from True to False (KIP-106) Kafka-4711 :Change Default unclean.leader.election.enabled from True to False (KIP-106)

[GitHub] kafka pull request #2463: KAFKA-4706

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

Re: Rewind Kafka Stream consumer offset by timestamp

Thanks Matthias! My comments below. Regards, Jorge. El lun., 30 ene. 2017 a las 18:40, Matthias J. Sax () escribió: > It would be enough, IMHO :) > > However, we need to discuss some details about this. > > 1) we could extend the reset tool with an flag

Re: [DISCUSS] KIP-115: Enforce offsets.topic.replication.factor

Hi all, First of all, thanks Onur for fixing this. With regards to where we merge the code, my personal preference would be to merge it to trunk ASAP ((which means that it would be part of 0.10.3.0). Generally, I think we should be conservative when it comes to code merged right before the RC

Re: [DISCUSS] KIP-110: Add Codec for ZStandard Compression

No problem. I will elaborate my KIP with the updated benchmark & error cases. And here, I resend you the screenshot: ​ Best, Dongjin On Tue, Jan 31, 2017 at 7:42 PM, Ismael Juma wrote: > Thanks Dongjin. That seems to make things simpler indeed. It would be good > to update

Re: [DISCUSS] KIP-110: Add Codec for ZStandard Compression

Yes, I agree that the dataset being used in the comparison doesn't show the strength/weakness of the various algorithms (I actually thought that there was a bug initially). Maybe we could use the test suites mentioned in the following project: https://github.com/ning/jvm-compressor-benchmark

[DISCUS] consuming messages is polling - is there a reason? new KIP for poll?

Hi there, I realized that consuming messages is implemented as polling on protocol level. Is there a reason why the client has to ask for messages? Wouldn't it make more sense to push messages to consumers - at least to high-level ones? I would think about it like: Broker receives a new

Re: [DISCUSS] KIP-110: Add Codec for ZStandard Compression

Thanks Dongjin. That seems to make things simpler indeed. It would be good to update the KIP with the relevant details. I suggest describing each flow and the error that the user would see in each case. Also, you mentioned an attached screenshot, but it seems like there was nothing attached to

Re: [DISCUSS] KIP-110: Add Codec for ZStandard Compression

Hi Dongjin and good work on the KIP, I understand that ZStandard is generally considered an improvement over LZ4, but the benchmark you provided on the KIP-110 wiki doesn't really reflect that, and even makes a note that they are comparable: *> As you can see above, ZStandard shows outstanding

Re: [DISCUSS] KIP-110: Add Codec for ZStandard Compression

Ismael & All, After Inspecting the related code & commits, I concluded following: 1. We have to update the masking value which is used to retrieve the used codec id from the messages, to enable the retrieval of the 3rd bit of compression type field of the message. 2. The above task is already

Re: [DISCUSS] KIP-115: Enforce offsets.topic.replication.factor

I'm fine if it goes into 0.10.2.0 On Tue, Jan 31, 2017 at 8:53 AM, Onur Karaman wrote: > I get where Ewen's coming from but personally, I have trouble understanding > a use case where end users would specifically rely on existing behavior of > group coordination