Build failed in Jenkins: kafka-trunk-jdk11 #234

2019-01-21 Thread Apache Jenkins Server
See Changes: [ismael] KAFKA-7844: Use regular subproject for generator to fix *All targets -- [...truncated 2.27 MB...] org.apache.kafka.connect.json.JsonConverterTest >

[jira] [Resolved] (KAFKA-7844) Fix "Cannot lock buildSrc build lock as it has already been locked by this process" error in jarAll

2019-01-21 Thread Ismael Juma (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-7844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-7844. Resolution: Fixed > Fix "Cannot lock buildSrc build lock as it has already been locked by this > p

[jira] [Created] (KAFKA-7850) Remove deprecated KStreamTestDriver

2019-01-21 Thread Richard Yu (JIRA)
Richard Yu created KAFKA-7850: - Summary: Remove deprecated KStreamTestDriver Key: KAFKA-7850 URL: https://issues.apache.org/jira/browse/KAFKA-7850 Project: Kafka Issue Type: Improvement

Re: [VOTE] KIP-420: Add Single Value Fetch in Session Stores

2019-01-21 Thread Bill Bejeck
Thanks for the KIP Guozhang, +1 for me. -Bill On Sat, Jan 19, 2019 at 1:59 PM Matthias J. Sax wrote: > Thanks for the KIP Guozhang! > > Would it make sense to add a default implementation for the new method? > I am not sure, and I actually think it would not make sense: > > - Kafka Streams pro

Re: [DISCUSS] Notify SourceTask of ACK'd offsets, metadata

2019-01-21 Thread Ryanne Dolan
Andrew Schofield suggested we overload the commitRecord method instead of adding a new one. Thoughts? Ryanne On Thu, Jan 17, 2019, 5:34 PM Ryanne Dolan I had to change the KIP number (concurrency is hard!) so the link is now: > > > https://cwiki.apache.org/confluence/display/KAFKA/KIP-416%3A+Not

Re: [VOTE] KIP-416: Notify SourceTask of ACK'd offsets, metadata

2019-01-21 Thread Ryanne Dolan
Andrew, I agree it's a better commitRecord, but with the slightly different semantics you mentioned. I suppose we could document that well enough that reusing the same name would be fine. I'll resend the discussion email. Maybe it got lost somehow. Ryanne On Mon, Jan 21, 2019, 4:37 AM Andrew Sch

Build failed in Jenkins: kafka-2.1-jdk8 #111

2019-01-21 Thread Apache Jenkins Server
See Changes: [ismael] MINOR: Fix checkstyle error caused by #5781 -- [...truncated 686.79 KB...] kafka.security.auth.SimpleAclAuthorizerTest > testWritesLiteralAclChangeEven

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

2019-01-21 Thread Apache Jenkins Server
See

Build failed in Jenkins: kafka-trunk-jdk11 #233

2019-01-21 Thread Apache Jenkins Server
See Changes: [vahid.hashemian] Fix Documentation for cleanup.policy is out of date (#6181) -- [...truncated 2.27 MB...] org.apache.kafka.streams.test.OutputVerifierTest >

Re: [VOTE] KIP-396: Add Commit/List Offsets Operations to AdminClient

2019-01-21 Thread Ismael Juma
The KIP doesn't discuss the option of using KafkaConsumer directly as far as I can tell. We have tried to avoid having the same functionality in multiple clients so it would be good to explain why this is necessary here (not saying it isn't). Ismael On Mon, Jan 21, 2019, 10:29 AM Mickael Maison

Re: [VOTE] KIP-396: Add Commit/List Offsets Operations to AdminClient

2019-01-21 Thread Mickael Maison
Thanks Ryanne for the feedback, all suggestions sounded good, I've updated the KIP accordingly. On Mon, Jan 21, 2019 at 3:43 PM Ryanne Dolan wrote: > > +1 (non-binding) > > But I suggest: > > - drop "get" from getOffset, getTimestamp. > > - add to the motivation section why this is better than co

RE: [EXTERNAL] - Re: [DISCUSS] KIP-387: Fair Message Consumption Across Partitions in KafkaConsumer

2019-01-21 Thread ChienHsing Wu
Hi all, not sure what to do next as weeks have gone by, guys. --CH -Original Message- From: ChienHsing Wu Sent: Monday, January 14, 2019 9:13 AM To: dev@kafka.apache.org Subject: RE: [EXTERNAL] - Re: [DISCUSS] KIP-387: Fair Message Consumption Across Partitions in KafkaConsumer Hi, I

Re: [DISCUSS] KIP-390: Add producer option to adjust compression level

2019-01-21 Thread Ismael Juma
Thanks! Ismael On Mon, Jan 21, 2019 at 6:02 AM Dongjin Lee wrote: > Hi Ismael, > > After reviewing `LogValidator#validateMessagesAndAssignOffsetsCompressed`, > yes, you are right. If source codec and target codec is identical and the > magic is above 0, the broker can do an in-place assignment,

[jira] [Created] (KAFKA-7849) Warning when adding GlobalKTable

2019-01-21 Thread Dmitry Minkovsky (JIRA)
Dmitry Minkovsky created KAFKA-7849: --- Summary: Warning when adding GlobalKTable Key: KAFKA-7849 URL: https://issues.apache.org/jira/browse/KAFKA-7849 Project: Kafka Issue Type: Bug

Re: [VOTE] KIP-396: Add Commit/List Offsets Operations to AdminClient

2019-01-21 Thread Ryanne Dolan
+1 (non-binding) But I suggest: - drop "get" from getOffset, getTimestamp. - add to the motivation section why this is better than constructing a KafkaConsumer and using seek(), commit() etc. - add some rejected alternatives. Ryanne On Mon, Jan 21, 2019, 7:57 AM Dongjin Lee We have +4 non-

Re: [DISCUSS] KIP-390: Add producer option to adjust compression level

2019-01-21 Thread Dongjin Lee
Hi Ismael, After reviewing `LogValidator#validateMessagesAndAssignOffsetsCompressed`, yes, you are right. If source codec and target codec is identical and the magic is above 0, the broker can do an in-place assignment, without recompressing. Sorry for my misunderstanding. Since we don't need `co

Re: [VOTE] KIP-396: Add Commit/List Offsets Operations to AdminClient

2019-01-21 Thread Dongjin Lee
We have +4 non-binding for this vote. Is there any committer who is interested in this issue? Thanks, Dongjin On Mon, Jan 21, 2019 at 10:33 PM Andrew Schofield wrote: > +1 (non-binding). Thanks for the KIP. > > On 21/01/2019, 12:45, "Eno Thereska" wrote: > > +1 (non binding). Thanks. > >

Re: [VOTE] KIP-396: Add Commit/List Offsets Operations to AdminClient

2019-01-21 Thread Andrew Schofield
+1 (non-binding). Thanks for the KIP. On 21/01/2019, 12:45, "Eno Thereska" wrote: +1 (non binding). Thanks. On Mon, Jan 21, 2019 at 12:30 PM Mickael Maison wrote: > Bumping this thread. Considering this KIP is relatively straigh > forward, can we get some votes or

Re: [VOTE] KIP-396: Add Commit/List Offsets Operations to AdminClient

2019-01-21 Thread Eno Thereska
+1 (non binding). Thanks. On Mon, Jan 21, 2019 at 12:30 PM Mickael Maison wrote: > Bumping this thread. Considering this KIP is relatively straigh > forward, can we get some votes or feedback if you think it's not? > Thanks > > On Tue, Jan 8, 2019 at 5:40 PM Edoardo Comar wrote: > > > > +1 (non

Re: [VOTE] KIP-396: Add Commit/List Offsets Operations to AdminClient

2019-01-21 Thread Mickael Maison
Bumping this thread. Considering this KIP is relatively straigh forward, can we get some votes or feedback if you think it's not? Thanks On Tue, Jan 8, 2019 at 5:40 PM Edoardo Comar wrote: > > +1 (non-binding) > Thanks Mickael! > > On Tue, 8 Jan 2019 at 17:39, Patrik Kleindl wrote: > > > +1 (non

Build failed in Jenkins: kafka-trunk-jdk11 #232

2019-01-21 Thread Apache Jenkins Server
See Changes: [github] MINOR: increase timeouts for KafkaStreamsTest (#6178) -- [...truncated 2.27 MB...] kafka.utils.PasswordEncoderTest > testEncoderConfigChange PASSED

Build failed in Jenkins: kafka-2.1-jdk8 #110

2019-01-21 Thread Apache Jenkins Server
See Changes: [matthias] MINOR: Handle case where connector status endpoints returns 404 (#6176) -- [...truncated 915.53 KB...] kafka.server.KafkaConfigTest > testInterBroke

Jenkins build is back to normal : kafka-2.0-jdk8 #216

2019-01-21 Thread Apache Jenkins Server
See

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

2019-01-21 Thread Apache Jenkins Server
See Changes: [github] MINOR: increase timeouts for KafkaStreamsTest (#6178) -- [...truncated 2.27 MB...] org.apache.kafka.connect.transforms.MaskFieldTest > schemaless PAS

Re: [VOTE] KIP-416: Notify SourceTask of ACK'd offsets, metadata

2019-01-21 Thread Andrew Schofield
Hi, I'm not quite sure about the etiquette here but I wonder whether the KIP could be improved. I think I missed the DISCUSS thread. I think that really your recordLogged(SourceRecord, RecordMetadata) method is actually a better version of commitRecord() and perhaps it ought to be an overload.

Re: [DISCUSS] KIP-419 Safely notify Kafka Connect SourceTask is stopped

2019-01-21 Thread Andrew Schofield
Ryanne, Thanks for your comments. I think my overarching point is that the various states of a SourceTask and the transitions between them seem a bit loose and that makes it difficult to figure out when the resources held by a SourceTask can be safely released. Your "I can't tell from the docume

Build failed in Jenkins: kafka-trunk-jdk11 #231

2019-01-21 Thread Apache Jenkins Server
See Changes: [manikumar.reddy] MINOR: Rejoin split ssl principal mapping rules (#6099) -- [...truncated 2.27 MB...] org.apache.kafka.trogdor.agent.AgentTest > testCreate

Re: [VOTE] KIP-402: Improve fairness in SocketServer processors

2019-01-21 Thread Rajini Sivaram
Hi all, The vote has passed with 5 binding votes (Harsha, Gwen, Colin, Ismael, me). Thanks to everyone for the discussions and votes. I will update the KIP page and the PRs. Regards, Rajini On Wed, Jan 16, 2019 at 5:07 PM Ismael Juma wrote: > Thanks for the KIP, +1 (binding). > > Ismael > > O

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

2019-01-21 Thread Apache Jenkins Server
See Changes: [manikumar.reddy] MINOR: Rejoin split ssl principal mapping rules (#6099) -- [...truncated 2.26 MB...] org.apache.kafka.streams.test.OutputVerifierTest > sh

[jira] [Created] (KAFKA-7848) Idempotence producer keep retry on OutOfOrderSequenceException

2019-01-21 Thread zwangbo (JIRA)
zwangbo created KAFKA-7848: -- Summary: Idempotence producer keep retry on OutOfOrderSequenceException Key: KAFKA-7848 URL: https://issues.apache.org/jira/browse/KAFKA-7848 Project: Kafka Issue Type: