[jira] [Created] (KAFKA-5340) Add additional test cases for batch splitting to ensure idempotent/transactional metadata is preserved

Jason Gustafson created KAFKA-5340: -- Summary: Add additional test cases for batch splitting to ensure idempotent/transactional metadata is preserved Key: KAFKA-5340 URL:

[jira] [Commented] (KAFKA-5093) Load only batch header when rebuilding producer ID map

[ https://issues.apache.org/jira/browse/KAFKA-5093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16027696#comment-16027696 ] Umesh Chaudhary commented on KAFKA-5093: No worries at all [~hachikuji] :) > Load only batch

[jira] [Commented] (KAFKA-5338) There is a Misspell in ResetIntegrationTest

[ https://issues.apache.org/jira/browse/KAFKA-5338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16027695#comment-16027695 ] Matthias J. Sax commented on KAFKA-5338: [~guozhang] Can you add [~hejiefang] to contributor list,

[jira] [Updated] (KAFKA-5338) There is a Misspell in ResetIntegrationTest

[ https://issues.apache.org/jira/browse/KAFKA-5338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-5338: --- Fix Version/s: 0.11.0.0 > There is a Misspell in ResetIntegrationTest >

[jira] [Updated] (KAFKA-5338) There is a Misspell in ResetIntegrationTest

[ https://issues.apache.org/jira/browse/KAFKA-5338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-5338: --- Status: Patch Available (was: Open) > There is a Misspell in ResetIntegrationTest >

[jira] [Updated] (KAFKA-5338) There is a Misspell in ResetIntegrationTest

[ https://issues.apache.org/jira/browse/KAFKA-5338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-5338: --- Affects Version/s: (was: 0.11.1.0) 0.10.2.1 > There is a Misspell

Re: [DISCUSS]: KIP-149: Enabling key access in ValueTransformer, ValueMapper, and ValueJoiner

Thanks Jeyhun. About ValueTransformer: I don't think we can remove it. Note, ValueTransformer allows to attach a state and also allows to register punctuations. Both those features will not be available via withKey() interfaces. -Matthias On 5/27/17 1:25 PM, Jeyhun Karimov wrote: > Hi

[jira] [Issue Comment Deleted] (KAFKA-4660) Improve test coverage KafkaStreams

[ https://issues.apache.org/jira/browse/KAFKA-4660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-4660: --- Comment: was deleted (was: [~damianguy] Should we just close this as `toString()` is going to

[jira] [Commented] (KAFKA-4660) Improve test coverage KafkaStreams

[ https://issues.apache.org/jira/browse/KAFKA-4660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16027693#comment-16027693 ] Matthias J. Sax commented on KAFKA-4660: [~damianguy] Should we just close this as `toString()` is

Re: KIP-162: Enable topic deletion by default

Sure, that sounds good. I suggested that to keep command line behavior consistent. Plus, removal of ACL access is something that can be easily undone, but topic deletion is not reversible. So, perhaps a new follow-up JIRA to this KIP to add the confirmation for topic deletion. Thanks. --Vahid

[jira] [Created] (KAFKA-5339) Transactions system test with hard broker bounces fails sporadically

Apurva Mehta created KAFKA-5339: --- Summary: Transactions system test with hard broker bounces fails sporadically Key: KAFKA-5339 URL: https://issues.apache.org/jira/browse/KAFKA-5339 Project: Kafka

[jira] [Commented] (KAFKA-4340) Change the default value of log.message.timestamp.difference.max.ms to the same as log.retention.ms

[ https://issues.apache.org/jira/browse/KAFKA-4340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16027616#comment-16027616 ] Jun Rao commented on KAFKA-4340: [~edenhill], I wasn't suggesting that this commit is a breaking change.

Re: Efficient way of Searching Messages By Timestamp - Kafka

Hi Team , Any help here Pls ? Cheers, Senthil On Sat, May 27, 2017 at 8:25 PM, SenthilKumar K wrote: > Hello Kafka Developers , Users , > > We are exploring the SearchMessageByTimestamp feature in Kafka for our > use case . > > Use Case : Kafka will be realtime

Re: [DISCUSS]: KIP-149: Enabling key access in ValueTransformer, ValueMapper, and ValueJoiner

Hi Matthias, Thanks for your comments. I tested the deep copy approach. It has significant overhead. Especially for "light" and stateless operators it slows down the topology significantly (> 20% ). I think "warning" users about not-changing the key is better warning them about possible

[jira] [Updated] (KAFKA-5093) Load only batch header when rebuilding producer ID map

[ https://issues.apache.org/jira/browse/KAFKA-5093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-5093: --- Assignee: Jason Gustafson Status: Patch Available (was: Open) > Load only batch header

[jira] [Commented] (KAFKA-5093) Load only batch header when rebuilding producer ID map

[ https://issues.apache.org/jira/browse/KAFKA-5093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16027555#comment-16027555 ] Jason Gustafson commented on KAFKA-5093: [~umesh9...@gmail.com] Apologies. I decided to pick this

[jira] [Commented] (KAFKA-5093) Load only batch header when rebuilding producer ID map

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

[GitHub] kafka pull request #3160: KAFKA-5093: Avoid loading full batch data when pos...

GitHub user hachikuji opened a pull request: https://github.com/apache/kafka/pull/3160 KAFKA-5093: Avoid loading full batch data when possible when iterating FileRecords You can merge this pull request into a Git repository by running: $ git pull

[jira] [Commented] (KAFKA-5155) Messages can be deleted prematurely when some producers use timestamps and some not

[ https://issues.apache.org/jira/browse/KAFKA-5155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16027521#comment-16027521 ] Michal Borowiecki commented on KAFKA-5155: -- Hi [~plavjanik], do you care to submit a pull request

Re: [DISCUSS] KIP-147: Add missing type parameters to StateStoreSupplier factories and KGroupedStream/Table methods

Hi all, I've updated the KIP to reflect the proposed backwards-compatible approach: https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=69408481 Given the vast area of APIs affected, I think the PR is easier to read than the code excerpts in the KIP itself:

Re: KIP-162: Enable topic deletion by default

Agreed and updated the KIP accordingly. Thank you! On Sat, May 27, 2017 at 1:25 AM Guozhang Wang wrote: > I'd say just remove those two lines. > > On Fri, May 26, 2017 at 7:55 AM, Gwen Shapira wrote: > > > This was a discussion, not a vote (sorry for

Re: KIP-162: Enable topic deletion by default

Thanks Vahid, Do you mind if we leave the command-line out of scope for this? I can see why adding confirmations, options to bypass confirmations, etc would be an improvement. However, I've seen no complaints about the current behavior of the command-line and the KIP doesn't change it at all. So

Re: KIP-162: Enable topic deletion by default

This KIP only changes a configuration default, so the two changes seem independent to me. And since both changes will be included in the release following 0.11 (October) and no sooner, I don't know if the order matters that much. Am I missing anything regarding KAFKA-4893 that means KIP-162

Re: [DISCUSS]: KIP-159: Introducing Rich functions to Streams

Hi, Thanks for your comments. I will refer the overall approach as rich functions until we find a better name. I think there are some pros and cons of the approach you described. Pros is that it is simple, has clear boundaries, avoids misunderstanding of term "function". So you propose sth

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

See Changes: [ismael] MINOR: Remove unused method parameter in `SimpleAclAuthorizer` -- [...truncated 2.90 MB...] kafka.api.AuthorizerIntegrationTest >

Efficient way of Searching Messages By Timestamp - Kafka

Hello Kafka Developers , Users , We are exploring the SearchMessageByTimestamp feature in Kafka for our use case . Use Case : Kafka will be realtime message bus , users should be able to pull Logs by specifying start_date and end_date or Pull me last five minutes data etc ... I did POC

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

See

Build failed in Jenkins: kafka-0.11.0-jdk7 #41

See Changes: [ismael] MINOR: Cleanup in tests to avoid threads being left behind -- [...truncated 902.84 KB...] kafka.controller.ControllerEventManagerTest >

[jira] [Commented] (KAFKA-5338) There is a Misspell in ResetIntegrationTest

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

[GitHub] kafka pull request #3159: [KAFKA-5338]There is a Misspell in ResetIntegratio...

GitHub user hejiefang opened a pull request: https://github.com/apache/kafka/pull/3159 [KAFKA-5338]There is a Misspell in ResetIntegrationTest You can merge this pull request into a Git repository by running: $ git pull https://github.com/hejiefang/kafka KAFKA-5338

[GitHub] kafka pull request #3147: MINOR: Remove unused method parameter in `SimpleAc...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3147 --- 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 #3146: MINOR: Cleanup in tests to avoid threads being lef...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3146 --- 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-4340) Change the default value of log.message.timestamp.difference.max.ms to the same as log.retention.ms

[ https://issues.apache.org/jira/browse/KAFKA-4340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16027366#comment-16027366 ] Magnus Edenhill commented on KAFKA-4340: Since this is a change to the protocol API (change of

[jira] [Updated] (KAFKA-5338) There is a Misspell in ResetIntegrationTest

[ https://issues.apache.org/jira/browse/KAFKA-5338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] hejiefang updated KAFKA-5338: - Affects Version/s: 0.11.1.0 > There is a Misspell in ResetIntegrationTest >

[jira] [Created] (KAFKA-5338) There is a Misspell in ResetIntegrationTest

hejiefang created KAFKA-5338: Summary: There is a Misspell in ResetIntegrationTest Key: KAFKA-5338 URL: https://issues.apache.org/jira/browse/KAFKA-5338 Project: Kafka Issue Type: Bug

[jira] [Commented] (KAFKA-5093) Load only batch header when rebuilding producer ID map

[ https://issues.apache.org/jira/browse/KAFKA-5093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16027362#comment-16027362 ] Umesh Chaudhary commented on KAFKA-5093: Tried to co-relate it with KIP but was unable to locate

[jira] [Resolved] (KAFKA-5078) PartitionRecords.fetchRecords(...) should defer exception to the next call if iterator has already moved across any valid record

[ https://issues.apache.org/jira/browse/KAFKA-5078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin resolved KAFKA-5078. - Resolution: Fixed > PartitionRecords.fetchRecords(...) should defer exception to the next call if

[jira] [Updated] (KAFKA-5078) PartitionRecords.fetchRecords(...) should defer exception to the next call if iterator has already moved across any valid record

[ https://issues.apache.org/jira/browse/KAFKA-5078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-5078: Fix Version/s: 0.11.0.0 > PartitionRecords.fetchRecords(...) should defer exception to the next

[jira] [Updated] (KAFKA-5326) Log offset index resize cause empty index file

[ https://issues.apache.org/jira/browse/KAFKA-5326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ma Tianchi updated KAFKA-5326: -- Status: Patch Available (was: Open) > Log offset index resize cause empty index file >

[jira] [Updated] (KAFKA-5319) Add a tool to make cluster replica and leader balance

[ https://issues.apache.org/jira/browse/KAFKA-5319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ma Tianchi updated KAFKA-5319: -- Attachment: KAFKA-5319.patch > Add a tool to make cluster replica and leader balance >

[jira] [Updated] (KAFKA-5319) Add a tool to make cluster replica and leader balance

[ https://issues.apache.org/jira/browse/KAFKA-5319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ma Tianchi updated KAFKA-5319: -- Labels: patch (was: ) Reviewer: (was: xuzq) Status: Patch Available (was: Reopened) >