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

See Changes: [wangguoz] KAFKA-4986 Follow-up: cleanup unit tests and further comments addressed -- [...truncated 833.72 KB...] kafka.integration.SaslPlaintextTopicMetada

[jira] [Updated] (KAFKA-4593) Task migration during rebalance callback process could lead the obsoleted task's IllegalStateException

[ https://issues.apache.org/jira/browse/KAFKA-4593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-4593: - Description: 1. Assume 2 running threads A and B, and one task t1 jut for simplicity. 2. First reb

[jira] [Commented] (KAFKA-4593) Task migration during rebalance callback process could lead the obsoleted task's IllegalStateException

[ https://issues.apache.org/jira/browse/KAFKA-4593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15988354#comment-15988354 ] Guozhang Wang commented on KAFKA-4593: -- Yeah these two issues are not related, and al

[jira] [Updated] (KAFKA-4593) Task migration during rebalance callback process could lead the obsoleted task's IllegalStateException

[ https://issues.apache.org/jira/browse/KAFKA-4593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-4593: - Description: 1. Assume 2 running threads A and B, and one task t1 jut for simplicity. Thread A an

[jira] [Commented] (KAFKA-4772) Exploit #peek to implement #print() and other methods

[ https://issues.apache.org/jira/browse/KAFKA-4772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15988365#comment-15988365 ] james chien commented on KAFKA-4772: I think I know it. This idea is good, and we want

[jira] [Comment Edited] (KAFKA-4772) Exploit #peek to implement #print() and other methods

[ https://issues.apache.org/jira/browse/KAFKA-4772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15988365#comment-15988365 ] james chien edited comment on KAFKA-4772 at 4/28/17 7:37 AM: -

[jira] [Comment Edited] (KAFKA-4772) Exploit #peek to implement #print() and other methods

[ https://issues.apache.org/jira/browse/KAFKA-4772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15988365#comment-15988365 ] james chien edited comment on KAFKA-4772 at 4/28/17 7:37 AM: -

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

See Changes: [jason] KAFKA-5097; Add testFetchAfterPartitionWithFetchedRecordsIsUnassigned -- [...truncated 832.34 KB...] kafka.integration.SaslPlaintextTopicMetadataTest

[jira] [Updated] (KAFKA-4477) Node reduces its ISR to itself, and doesn't recover. Other nodes do not take leadership, cluster remains sick until node is restarted.

[ https://issues.apache.org/jira/browse/KAFKA-4477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arpan updated KAFKA-4477: - Attachment: server_3_74Server.log server_2_73_server.log server_1_72server.log Att

[jira] [Comment Edited] (KAFKA-4477) Node reduces its ISR to itself, and doesn't recover. Other nodes do not take leadership, cluster remains sick until node is restarted.

[ https://issues.apache.org/jira/browse/KAFKA-4477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15988460#comment-15988460 ] Arpan edited comment on KAFKA-4477 at 4/28/17 9:08 AM: --- Hi [~apurva]

[jira] [Comment Edited] (KAFKA-4477) Node reduces its ISR to itself, and doesn't recover. Other nodes do not take leadership, cluster remains sick until node is restarted.

[ https://issues.apache.org/jira/browse/KAFKA-4477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15988159#comment-15988159 ] Arpan edited comment on KAFKA-4477 at 4/28/17 9:08 AM: --- Hi Apurva, I

[jira] [Issue Comment Deleted] (KAFKA-4477) Node reduces its ISR to itself, and doesn't recover. Other nodes do not take leadership, cluster remains sick until node is restarted.

[ https://issues.apache.org/jira/browse/KAFKA-4477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arpan updated KAFKA-4477: - Comment: was deleted (was: Also not sure why I am unable to find this bug reference in release notes.) > Node r

[jira] [Comment Edited] (KAFKA-4477) Node reduces its ISR to itself, and doesn't recover. Other nodes do not take leadership, cluster remains sick until node is restarted.

[ https://issues.apache.org/jira/browse/KAFKA-4477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15988460#comment-15988460 ] Arpan edited comment on KAFKA-4477 at 4/28/17 9:13 AM: --- Hi [~apurva]

[jira] [Comment Edited] (KAFKA-4772) Exploit #peek to implement #print() and other methods

[ https://issues.apache.org/jira/browse/KAFKA-4772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15988365#comment-15988365 ] james chien edited comment on KAFKA-4772 at 4/28/17 9:19 AM: -

[jira] [Comment Edited] (KAFKA-4477) Node reduces its ISR to itself, and doesn't recover. Other nodes do not take leadership, cluster remains sick until node is restarted.

[ https://issues.apache.org/jira/browse/KAFKA-4477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15988460#comment-15988460 ] Arpan edited comment on KAFKA-4477 at 4/28/17 9:25 AM: --- Hi [~apurva]

[jira] [Updated] (KAFKA-4477) Node reduces its ISR to itself, and doesn't recover. Other nodes do not take leadership, cluster remains sick until node is restarted.

[ https://issues.apache.org/jira/browse/KAFKA-4477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arpan updated KAFKA-4477: - Attachment: 74_Server_Thread_Dump 73_Server_Thread_Dump.txt 72_Server_Thread_Dump.t

[GitHub] kafka pull request #2934: KAFKA-5059: [Follow Up] remove broken locking. Fix...

GitHub user dguy opened a pull request: https://github.com/apache/kafka/pull/2934 KAFKA-5059: [Follow Up] remove broken locking. Fix handleAddPartitions remove broken locking. fix handleAddPartitions after complete commit/abort respond with CONCURRENT_TRANSACTIONS in initPid You

[jira] [Commented] (KAFKA-5059) Implement Transactional Coordinator

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

[GitHub] kafka pull request #2930: MINOR: Make assignment expectation explicit in tes...

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

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

See Changes: [wangguoz] KAFKA-4986 Follow-up: cleanup unit tests and further comments addressed -- [...truncated 699.47 KB...] kafka.api.UserClientIdQuotaTest > testQuot

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

See Changes: [ismael] MINOR: Make assignment expectation explicit in -- [...truncated 755.55 KB...] kafka.coordinator.transaction.TransactionMarkerChannelManagerTest > sh

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

See Changes: [jason] KAFKA-5097; Add testFetchAfterPartitionWithFetchedRecordsIsUnassigned [ismael] MINOR: Make assignment expectation explicit in -- [...truncated 1.63 M

[GitHub] kafka pull request #2935: MINOR: onControllerResignation should be invoked i...

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/2935 MINOR: onControllerResignation should be invoked if triggerControllerMove is called This fixes a transient test failure due to a NPE in ControllerFailoverTest.testMetadataUpdate: ```text

[jira] [Commented] (KAFKA-3761) Controller has RunningAsBroker instead of RunningAsController state

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

[GitHub] kafka pull request #2936: MINOR: JoinGroupRequest V0 invalid rebalance timeo...

GitHub user edoardocomar opened a pull request: https://github.com/apache/kafka/pull/2936 MINOR: JoinGroupRequest V0 invalid rebalance timeout A JoinGroupRequest V0 built with the Builder had a rebalance timeout = -1 rather than equal to session timeout as it would have bee

RE: Kafka Connect and Partitions

Hi Gwen, Having added a custom partitioner (via the producer.partitioner.class property in worker.properties) that simply randomly selects a partition, the data is now written evenly across all the partitions :) The root of my confusion regarding why the default partitioner writes all data to

Re: Kafka Connect and Partitions

The source connector creates SourceRecord object and can set a number of fields, including the message's key and value, the Kafka topic name and, if desired, the Kafka topic partition number. If the connector does se the the topic partition to a non-null value, then that's the partition to which Ka

Re: [jira] [Commented] (KAFKA-4379) Remove caching of dirty and removedkeys from StoreChangeLogger

Bc Sent from my iPhone B > On 25-Apr-2017, at 10:21, ASF GitHub Bot (JIRA) wrote: > >This message is eligible for Automatic Cleanup! (j...@apache.org) Add > cleanup rule | More info > >[ > https://issues.apache.org/jira/browse/KAFKA-4379?page=com.atlassian.jira.plugin.system.issuetab

Splitting tasks in streams?

Hi community, I have a question regarding with streams library. Currently, in kafka-streams we run the whole topology in one instance and there can be several topologies or tasks in a single node. However, there can be use-cases with very complex topologies with costly operators. So, when we wan

RE: Kafka Connect and Partitions

Hi Randall, I'd prefer it if my source connector didn't explicitly set a partition number - it seems cleaner for this to be set by a partitioner based on information generated by the source, i.e. to keep these aspects cleanly decoupled. Re your final paragraph, I do understand that the source p

[jira] [Updated] (KAFKA-3704) Improve mechanism for compression stream block size selection in KafkaProducer

[ https://issues.apache.org/jira/browse/KAFKA-3704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3704: --- Description: As discovered in https://issues.apache.org/jira/browse/KAFKA-3565, the current default b

Re: Splitting tasks in streams?

Hi Jeyhun, You make a good observation and I think a discussion/contribution around this would be very much appreciated by the community. Are you thinking of a KIP perhaps? Eno > On 28 Apr 2017, at 16:13, Jeyhun Karimov wrote: > > Hi community, > > I have a question regarding with streams l

[GitHub] kafka pull request #2937: MINOR: Metrics recording level producer

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/2937 MINOR: Metrics recording level producer You can merge this pull request into a Git repository by running: $ git pull https://github.com/ijuma/kafka metrics-recording-level-producer Alternativel

Re: [DISCUSS] KIP-140: Add administrative RPCs for adding, deleting, and listing ACLs

Hi Jun, Thanks for the review. On Thu, Apr 27, 2017, at 14:21, Jun Rao wrote: > Hi, Colin, > > Thanks for the KIP. Looks good overall. Just a few minor comments. > > 1. The controller is responsible for managing the state of topics. So, it > makes sense for create/delete topic requests to be se

[jira] [Commented] (KAFKA-4772) Exploit #peek to implement #print() and other methods

[ https://issues.apache.org/jira/browse/KAFKA-4772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15989106#comment-15989106 ] Matthias J. Sax commented on KAFKA-4772: For {{KStream#peek()}} we don't need a us

Re: Splitting tasks in streams?

I guess you can do thus "manually" by splitting you code into multiple applications so you can scale each part independently. I am not against an improvement in Streams itself, but I am not sure how this could be done atm. -Matthias On 4/28/17 8:42 AM, Eno Thereska wrote: > Hi Jeyhun, > > You

Re: Splitting tasks in streams?

Hi Eno, Thanks for reply. For me it was important that the particular use-case can be involved within kafka-stream's boundaries. I would put this in future plans as I don't think now it is approproate time to introduce this feature in streams library. Currently implementing query optimization (lik

[jira] [Commented] (KAFKA-4772) Exploit #peek to implement #print() and other methods

[ https://issues.apache.org/jira/browse/KAFKA-4772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15989132#comment-15989132 ] james chien commented on KAFKA-4772: As you said, it seems like no issue exists anymor

[jira] [Created] (KAFKA-5141) WorkerTest.testCleanupTasksOnStop transient failure due to NPE

Ewen Cheslack-Postava created KAFKA-5141: Summary: WorkerTest.testCleanupTasksOnStop transient failure due to NPE Key: KAFKA-5141 URL: https://issues.apache.org/jira/browse/KAFKA-5141 Project:

[jira] [Commented] (KAFKA-4772) Exploit #peek to implement #print() and other methods

[ https://issues.apache.org/jira/browse/KAFKA-4772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15989231#comment-15989231 ] Matthias J. Sax commented on KAFKA-4772: There is still an issue -- but it's an in

[DISCUSS] KIP-145: Classloading Isolation in Connect

Hi everyone, we aim to address dependency conflicts in Kafka Connect soon by applying class loading isolation. Feel free to take a look at KIP-145 here: https://cwiki.apache.org/confluence/display/KAFKA/KIP-145+Classloading+Isolation+in+Connect which describes minimal required changes in the p

[GitHub] kafka pull request #2938: KAFKA-5096: Log invalid user configs and use defau...

GitHub user johnma14 opened a pull request: https://github.com/apache/kafka/pull/2938 KAFKA-5096: Log invalid user configs and use defaults Kafka Streams do not allow users to modify some consumer configurations. If the user modifies this property, currently an exception is throw

[jira] [Commented] (KAFKA-5096) Only log invalid user configs and overwrite with correct one

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

[jira] [Commented] (KAFKA-4740) Using new consumer API with a Deserializer that throws SerializationException can lead to infinite loop

[ https://issues.apache.org/jira/browse/KAFKA-4740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15989453#comment-15989453 ] Dong Lin commented on KAFKA-4740: - I realized that this is a known problem since Feb after

[GitHub] kafka pull request #2939: MINOR: Fix some lgtm.com alerts, ensuring certain ...

GitHub user adityasharad opened a pull request: https://github.com/apache/kafka/pull/2939 MINOR: Fix some lgtm.com alerts, ensuring certain input/output resources are closed. This PR uses the try-with-resources construct to ensure that certain input and output resources are always

[jira] [Commented] (KAFKA-5141) WorkerTest.testCleanupTasksOnStop transient failure due to NPE

[ https://issues.apache.org/jira/browse/KAFKA-5141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15989553#comment-15989553 ] Konstantine Karantasis commented on KAFKA-5141: --- Another one that looks simi

[jira] [Commented] (KAFKA-5141) WorkerTest.testCleanupTasksOnStop transient failure due to NPE

[ https://issues.apache.org/jira/browse/KAFKA-5141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15989554#comment-15989554 ] Konstantine Karantasis commented on KAFKA-5141: --- Another one that looks simi

[jira] [Assigned] (KAFKA-4785) Records from internal repartitioning topics should always use RecordMetadataTimestampExtractor

[ https://issues.apache.org/jira/browse/KAFKA-4785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeyhun Karimov reassigned KAFKA-4785: - Assignee: Jeyhun Karimov > Records from internal repartitioning topics should always use

[jira] [Commented] (KAFKA-4785) Records from internal repartitioning topics should always use RecordMetadataTimestampExtractor

[ https://issues.apache.org/jira/browse/KAFKA-4785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15989557#comment-15989557 ] Jeyhun Karimov commented on KAFKA-4785: --- [~mjsax] Do you think KAFKA-4144 is blockin

[jira] [Assigned] (KAFKA-4218) Enable access to key in ValueTransformer

[ https://issues.apache.org/jira/browse/KAFKA-4218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeyhun Karimov reassigned KAFKA-4218: - Assignee: Jeyhun Karimov > Enable access to key in ValueTransformer > ---

[GitHub] kafka pull request #2940: don't call the zookeeper host strings URLs

GitHub user travisfw opened a pull request: https://github.com/apache/kafka/pull/2940 don't call the zookeeper host strings URLs I spent a few minutes trying to guess what the scheme part might be. Documentation would be better if it doesn't say it is expecting a format it isn't ex

[jira] [Commented] (KAFKA-3266) Implement KIP-4 RPCs and APIs for creating, altering, and listing ACLs

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

[GitHub] kafka pull request #2941: KAFKA-3266: Implement KIP-140 RPCs and APIs for cr...

GitHub user cmccabe opened a pull request: https://github.com/apache/kafka/pull/2941 KAFKA-3266: Implement KIP-140 RPCs and APIs for creating, altering, and listing ACLs You can merge this pull request into a Git repository by running: $ git pull https://github.com/cmccabe/ka

[VOTE] KIP-140: Add administrative RPCs for adding, deleting, and listing ACLs

Hi all, I'd like to start the voting for KIP-140: Add administrative RPCs for adding, deleting, and listing ACLs. This provides an API for adding, deleting, and listing the access control lists (ACLs) which are used to control access on Kafka topics and brokers. The wiki page is here: https://cw

Re: [VOTE] KIP-140: Add administrative RPCs for adding, deleting, and listing ACLs

+1 From: Colin McCabe Sent: Saturday, April 29, 2017 1:09:25 AM To: dev@kafka.apache.org Subject: [VOTE] KIP-140: Add administrative RPCs for adding, deleting, and listing ACLs Hi all, I'd like to start the voting for KIP-140: Add administrative RPCs for

[jira] [Updated] (KAFKA-4208) Add Record Headers

[ https://issues.apache.org/jira/browse/KAFKA-4208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-4208: --- Resolution: Fixed Fix Version/s: 0.11.0.0 Status: Resolved (was: Patch Avail

[GitHub] kafka pull request #2772: KAFKA-4208: Add Record Headers

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2772 --- 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-4208) Add Record Headers

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

[jira] [Commented] (KAFKA-4785) Records from internal repartitioning topics should always use RecordMetadataTimestampExtractor

[ https://issues.apache.org/jira/browse/KAFKA-4785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15989725#comment-15989725 ] Matthias J. Sax commented on KAFKA-4785: Yes. This ticket requirs KAFKA-4144 to be

[jira] [Updated] (KAFKA-4195) support throttling on request rate

[ https://issues.apache.org/jira/browse/KAFKA-4195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4195: --- Status: In Progress (was: Patch Available) > support throttling on request rate > ---

[jira] [Updated] (KAFKA-4195) support throttling on request rate

[ https://issues.apache.org/jira/browse/KAFKA-4195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4195: --- Status: Patch Available (was: Open) > support throttling on request rate > --

[jira] [Updated] (KAFKA-4954) Implementation and unit tests for request handler thread utilization quota

[ https://issues.apache.org/jira/browse/KAFKA-4954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4954: --- Status: Patch Available (was: Open) > Implementation and unit tests for request handler thread utiliz

[jira] [Updated] (KAFKA-4955) Add network handler thread utilization to request quota calculation

[ https://issues.apache.org/jira/browse/KAFKA-4955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4955: --- Status: Patch Available (was: Open) > Add network handler thread utilization to request quota calcula

[jira] [Updated] (KAFKA-4925) Add a configurable delay to the initial consumer group rebalance

[ https://issues.apache.org/jira/browse/KAFKA-4925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4925: --- Status: Patch Available (was: Open) > Add a configurable delay to the initial consumer group rebalanc

[jira] [Commented] (KAFKA-4218) Enable access to key in ValueTransformer

[ https://issues.apache.org/jira/browse/KAFKA-4218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15989730#comment-15989730 ] Matthias J. Sax commented on KAFKA-4218: [~jeyhunkarimov], thanks for picking this

[jira] [Commented] (KAFKA-4772) Exploit #peek to implement #print() and other methods

[ https://issues.apache.org/jira/browse/KAFKA-4772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15989732#comment-15989732 ] james chien commented on KAFKA-4772: I think I got it, this JIRA is about replacing {`

[jira] [Comment Edited] (KAFKA-4772) Exploit #peek to implement #print() and other methods

[ https://issues.apache.org/jira/browse/KAFKA-4772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15989732#comment-15989732 ] james chien edited comment on KAFKA-4772 at 4/29/17 3:32 AM: -

[jira] [Comment Edited] (KAFKA-4218) Enable access to key in ValueTransformer

[ https://issues.apache.org/jira/browse/KAFKA-4218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15989730#comment-15989730 ] Matthias J. Sax edited comment on KAFKA-4218 at 4/29/17 3:32 AM: ---

[jira] [Comment Edited] (KAFKA-4772) Exploit #peek to implement #print() and other methods

[ https://issues.apache.org/jira/browse/KAFKA-4772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15989732#comment-15989732 ] james chien edited comment on KAFKA-4772 at 4/29/17 3:33 AM: -

[jira] [Comment Edited] (KAFKA-4772) Exploit #peek to implement #print() and other methods

[ https://issues.apache.org/jira/browse/KAFKA-4772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15989732#comment-15989732 ] james chien edited comment on KAFKA-4772 at 4/29/17 3:35 AM: -

[jira] [Comment Edited] (KAFKA-4772) Exploit #peek to implement #print() and other methods

[ https://issues.apache.org/jira/browse/KAFKA-4772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15989732#comment-15989732 ] james chien edited comment on KAFKA-4772 at 4/29/17 3:34 AM: -

[jira] [Comment Edited] (KAFKA-4772) Exploit #peek to implement #print() and other methods

[ https://issues.apache.org/jira/browse/KAFKA-4772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15989732#comment-15989732 ] james chien edited comment on KAFKA-4772 at 4/29/17 3:34 AM: -

[jira] [Comment Edited] (KAFKA-4772) Exploit #peek to implement #print() and other methods

[ https://issues.apache.org/jira/browse/KAFKA-4772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15989732#comment-15989732 ] james chien edited comment on KAFKA-4772 at 4/29/17 3:35 AM: -

[jira] [Comment Edited] (KAFKA-4772) Exploit #peek to implement #print() and other methods

[ https://issues.apache.org/jira/browse/KAFKA-4772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15989732#comment-15989732 ] james chien edited comment on KAFKA-4772 at 4/29/17 3:36 AM: -

Re: [DISCUSS] KIP 141 - ProducerRecordBuilder Interface

Hi Thanks for all your input. My initial intent was to just add a “timestamp” constructor for the ProducerRecord, and it seems greater changes are too contentious. I’ve just rolled back the PR to add the missing constructors, in the way Ismael suggested. Updated KIP here: https://cwiki.apache

[jira] [Commented] (KAFKA-4772) Exploit #peek to implement #print() and other methods

[ https://issues.apache.org/jira/browse/KAFKA-4772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15989741#comment-15989741 ] Matthias J. Sax commented on KAFKA-4772: Exactly. All those classes a quite simila

[jira] [Commented] (KAFKA-4772) Exploit #peek to implement #print() and other methods

[ https://issues.apache.org/jira/browse/KAFKA-4772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15989761#comment-15989761 ] james chien commented on KAFKA-4772: okay, I will start to resolve this issue. > Expl

[jira] [Comment Edited] (KAFKA-4772) Exploit #peek to implement #print() and other methods

[ https://issues.apache.org/jira/browse/KAFKA-4772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15989761#comment-15989761 ] james chien edited comment on KAFKA-4772 at 4/29/17 4:53 AM: -

Re: [DISCUSS] KIP 141 - ProducerRecordBuilder Interface

+1 N.b. it is a shame we don't work on the contention to work a better way forwards. From: Stephane Maarek Sent: Saturday, April 29, 2017 4:39:32 AM To: dev@kafka.apache.org Subject: Re: [DISCUSS] KIP 141 - ProducerRecordBuilder Interface Hi Thanks for

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

See Changes: [jason] KAFKA-4208; Add Record Headers -- [...truncated 2.40 MB...] org.apache.kafka.streams.state.internals.StoreChangeLoggerTest > testAddRemove PASSED or

Re: [DISCUSS] KIP 141 - ProducerRecordBuilder Interface

Probably should remove the words in the kip the other constructors are going to be deprecated if they aren't any more with just the tactical change Sent using OWA for iPhone From: Michael Pearce Sent: Saturday, April 29, 2017 6:04:00 AM To: dev@kafka.apac

Re: [DISCUSS] KIP 141 - ProducerRecordBuilder Interface

This is ref to this section that's still there " The ProducerRecord constructors will all be deprecated, except the main long explicit one: " Sent using OWA for iPhone From: Michael Pearce Sent: Saturday, April 29, 2017 6:17:04 AM To: dev@kafka.apache.or

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

See

Re: [VOTE] KIP-140: Add administrative RPCs for adding, deleting, and listing ACLs

+1 On 29 Apr 2017, 9:51 AM +0900, Michael Pearce , wrote: > +1 > > From: Colin McCabe Sent: Saturday, April 29, 2017 1:09:25 AM > To: dev@kafka.apache.org > Subject: [VOTE] KIP-140: Add administrative RPCs for adding, deleting, and > listing ACLs > > Hi a