date:20190422

[jira] [Created] (KAFKA-8273) Admin client doesn't reestablish connection on Broker restart

2019-04-22 Thread Christian Yotov (JIRA)

Christian Yotov created KAFKA-8273:
--

 Summary: Admin client doesn't reestablish connection on Broker 
restart
 Key: KAFKA-8273
 URL: https://issues.apache.org/jira/browse/KAFKA-8273
 Project: Kafka
  Issue Type: Bug
Reporter: Christian Yotov


*Steps to reproduce:*
 # Setup Admin Client to use SSL connection
 # Execute Request against broker(i.e `describeTopics`)
 # Restart Kafka Broker
 # Execute Request against broker again

*Current Result:*

No request is being executed(tested with `tcpdump`) and timeout exception is 
being thrown.

Exception:
{code:java}
{"thread":"Kafka Liveness 
Thread","level":"ERROR","loggerName":"com.axway.hada.messaging.kafka.health.KafkaBaseHealthThread","message":"Failed
 to execute request on time against 
Kafka.","thrown":{"commonElementCount":0,"name":"java.util.concurrent.TimeoutException","extendedStackTrace":"java.util.concurrent.TimeoutException:
 null\n\tat 
org.apache.kafka.common.internals.KafkaFutureImpl$SingleWaiter.await(KafkaFutureImpl.java:108)
 ~[kafka-clients-2.1.1.jar:?]\n\tat 
org.apache.kafka.common.internals.KafkaFutureImpl.get(KafkaFutureImpl.java:274) 
~[kafka-clients-2.1.1.jar:?]\n\tat 
com.axway.hada.messaging.kafka.health.KafkaBaseHealthThread.run(KafkaBaseHealthThread.java:47)
 
[messaging-1.0.0.89d269c3.jar:?]\n"},"endOfBatch":false,"loggerFqcn":"org.apache.logging.slf4j.Log4jLogger","instant":{"epochSecond":1555939865,"nanoOfSecond":50200},"threadId":31,"threadPriority":5}
 {"thread":"Kafka Liveness 
Thread","level":"DEBUG","loggerName":"org.apache.kafka.clients.admin.KafkaAdminClient","message":"[AdminClient
 clientId=adminclient-2] Queueing Call(callName=describeTopics, 
deadlineMs=1555939869502) with a timeout 2000 ms from 
now.","endOfBatch":false,"loggerFqcn":"org.apache.kafka.common.utils.LogContext$LocationAwareKafkaLogger","instant":{"epochSecond":1555939867,"nanoOfSecond":50200},"threadId":31,"threadPriority":5}
{code}
*NOTE:* Issue cannot be reproduced with PLAINTEXT connection.

*Workaround:* If Admin client is recreated connection can be reestablished

 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (KAFKA-8274) Old Committed messages got replayed after Kafka cluster Restart

2019-04-22 Thread Hrishikesh tiwary (JIRA)

Hrishikesh tiwary created KAFKA-8274:


 Summary: Old Committed messages got replayed after Kafka cluster 
Restart
 Key: KAFKA-8274
 URL: https://issues.apache.org/jira/browse/KAFKA-8274
 Project: Kafka
  Issue Type: Bug
  Components: consumer
Affects Versions: 1.0.0
 Environment: PROD
Reporter: Hrishikesh tiwary


I got a very serious issue in PROD Env . after restarting the Kafka cluster my 
old committed messages by same group if got replayed.

Its very shocking that if messages are already committed  by a group id then 
how comes same messages will be replayed by same group id.

I have a consumer which runs in web based application, at start up it starts 
the consumer by providing a group id. there is only one group id for the given 
web app.

 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: [VOTE] KIP-446: Add changelog topic configuration to KTable suppress

2019-04-22 Thread John Roesler

Hi Maarten,

Congratulations, your KIP has 3 binding votes, no vetoes, and has been open
for over 72 hours, so you can close the vote and submit a PR for review!

The way to close the vote is you just reply to this thread and tally up the
votes, and say that the KIP vote has passed (see the other vote threads for
examples). Then, you can update:
* your KIP wiki to change the status to "Adopted"
* the main KIP page to move your KIP to the "Adopted" section (It should be
in the "under discussion" section
* the Kafka Streams page, to move your KIP to the "Adopted" section (
https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Streams)

Looking forward to the PR!

-John

On Thu, Apr 18, 2019 at 7:58 PM Matthias J. Sax 
wrote:

> Thanks a lot for the KIP!
>
>
> +1 (binding)
>
>
> -Matthias
>
> On 4/18/19 12:31 PM, Guozhang Wang wrote:
> > +1 (binding).
> >
> > Thanks.
> >
> > On Thu, Apr 18, 2019 at 10:48 AM John Roesler  wrote:
> >
> >> Thanks, Maarten!
> >>
> >> +1 (non-binding)
> >>
> >> -John
> >>
> >> On Wed, Apr 17, 2019 at 1:45 PM Bill Bejeck  wrote:
> >>
> >>> Thanks for the KIP.
> >>>
> >>> +1(binding)
> >>>
> >>> -Bill
> >>>
> >>> On Wed, Apr 17, 2019 at 12:58 PM Bruno Cadonna 
> >> wrote:
> >>>
>  Hi Maarten Duijn,
> 
>  Thank you for driving this.
> 
>  +1 (non-binding)
> 
>  Best,
>  Bruno
> 
>  On Wed, Apr 17, 2019 at 8:21 AM Maarten Duijn 
>  wrote:
> 
> > Hello all,
> >
> > There has been informal agreement so I would like to call for a vote
> >> on
> > KIP-446: Add changelog topic configuration to KTable suppress. This
> >>> will
> > allow users to configure internal topics created by the suppress
> >>> operator
> > via the streams DSL.
> >
> > KIP:
> >
> 
> >>>
> >>
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-446%3A+Add+changelog+topic+configuration+to+KTable+suppress
> > JIRA: https://issues.apache.org/jira/browse/KAFKA-8147<
> > https://issues.apache.org/jira/browse/KAFKA-8029>
> > PR: will follow shortly
> >
> > Cheers,
> > Maarten
> >
> 
> >>>
> >>
> >
> >
>
>

[jira] [Created] (KAFKA-8275) NetworkClient leastLoadedNode selection should consider throttled nodes

2019-04-22 Thread Jason Gustafson (JIRA)

Jason Gustafson created KAFKA-8275:
--

 Summary: NetworkClient leastLoadedNode selection should consider 
throttled nodes
 Key: KAFKA-8275
 URL: https://issues.apache.org/jira/browse/KAFKA-8275
 Project: Kafka
  Issue Type: Bug
Reporter: Jason Gustafson
Assignee: Jason Gustafson


The leastLoadedNode() function is intended to find any available node. It is 
smart in the sense that it considers the number of inflight requests and 
reconnect backoff, but it has not been updated to take into account client 
throttling. If we have an available node which is not throttled, we should use 
it.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: [DISCUSS] KIP-440: Extend Connect Converter to support headers

2019-04-22 Thread Randall Hauch

Thanks for updating the KIP. It looks good to me, and since there haven't
been any other issue mentioned in this month-long thread, it's probably
fine to start a vote.

Best regards,

Randall

On Tue, Apr 2, 2019 at 3:12 PM Randall Hauch  wrote:

> Thanks for the submission, Yaroslav -- and for building on the suggestion
> of Jeremy C in https://issues.apache.org/jira/browse/KAFKA-7273. This is
> a nice and simple approach that is backward compatible.
>
> The KIP looks good so far, but I do have two specific suggestions to make
> things just a bit more explicit. First, both the "Public API" and "Proposed
> Changes" sections could be more explicit that the methods in the proposal
> are being added; as it's currently written a reader must infer that.
> Second, the "Proposed Changes" section needs to more clearly specify that
> the WorkerSourceTask will now use the new fromConnectData method with the
> headers instead of the existing method, and that the WorkerSinkTask will
> now use the toConnectData method with the headers instead of the existing
> method.
>
> Best regards,
>
> Randall
>
>
> On Mon, Mar 11, 2019 at 11:01 PM Yaroslav Tkachenko 
> wrote:
>
>> Hello,
>>
>> I'd like to propose a KIP that extends Kafka Connect Converter interface:
>>
>> https://cwiki.apache.org/confluence/display/KAFKA/KIP-440%3A+Extend+Connect+Converter+to+support+headers
>>
>> Thanks for considering!
>>
>> --
>> Yaroslav Tkachenko
>> sap1ens.com
>>
>

[jira] [Created] (KAFKA-8276) Schema Registry Security settings as Props

2019-04-22 Thread Karthik Murugesan (JIRA)

Karthik Murugesan created KAFKA-8276:


 Summary: Schema Registry Security settings as Props
 Key: KAFKA-8276
 URL: https://issues.apache.org/jira/browse/KAFKA-8276
 Project: Kafka
  Issue Type: Improvement
  Components: clients
Affects Versions: 2.2.0, 2.0.0, 1.0.0
Reporter: Karthik Murugesan
 Fix For: 2.1.1, 2.2.0, 2.1.0, 2.0.0, 1.1.0, 1.0.1, 1.0.0


Take Schema Registry Security properties from the Properties File for C3, and 
from the Producer/Consumer Properties instead of setting it as JVM Props 
(-Djavax.net.ssl.*). This forces devs to import the certs to the cacerts of jvm 
keystore.

confluent.controlcenter.schema.registry.url=https:/schema.registry.local.com:8081
 confluent.controlcenter.schema.registry.security.protocol=SSL
 
confluent.controlcenter.schema.registry.ssl.keystore.location=/var/private/ssl/Keystore.jks
 confluent.controlcenter.schema.registry.ssl.keystore.password=
 
confluent.controlcenter.schema.registry.ssl.truststore.location=/var/private/ssl/Truststore.jks
 confluent.controlcenter.schema.registry.ssl.truststore.password=
 confluent.controlcenter.schema.registry.ssl.key.password=

 

 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: [DISCUSS] KIP-440: Extend Connect Converter to support headers

2019-04-22 Thread Konstantine Karantasis

Thanks for the KIP Yaroslav!

Apologies for the late comment. However, after reading the KIP it's still
not very clear to me what happens to the existing
HeaderConverter interface and what's the expectation for existing code
implementing this interface out there.

Looking at the PR I see that the existing code is leaving the existing
connect headers conversion unaffected. I'd expect by reading the KIP to
understand what's the interplay of the current proposal with the existing
implementation of KIP-145 that introduced headers in Connect.

Thanks,
Konstantine

On Mon, Apr 22, 2019 at 9:07 AM Randall Hauch  wrote:

> Thanks for updating the KIP. It looks good to me, and since there haven't
> been any other issue mentioned in this month-long thread, it's probably
> fine to start a vote.
>
> Best regards,
>
> Randall
>
> On Tue, Apr 2, 2019 at 3:12 PM Randall Hauch  wrote:
>
> > Thanks for the submission, Yaroslav -- and for building on the suggestion
> > of Jeremy C in https://issues.apache.org/jira/browse/KAFKA-7273. This is
> > a nice and simple approach that is backward compatible.
> >
> > The KIP looks good so far, but I do have two specific suggestions to make
> > things just a bit more explicit. First, both the "Public API" and
> "Proposed
> > Changes" sections could be more explicit that the methods in the proposal
> > are being added; as it's currently written a reader must infer that.
> > Second, the "Proposed Changes" section needs to more clearly specify that
> > the WorkerSourceTask will now use the new fromConnectData method with the
> > headers instead of the existing method, and that the WorkerSinkTask will
> > now use the toConnectData method with the headers instead of the existing
> > method.
> >
> > Best regards,
> >
> > Randall
> >
> >
> > On Mon, Mar 11, 2019 at 11:01 PM Yaroslav Tkachenko 
> > wrote:
> >
> >> Hello,
> >>
> >> I'd like to propose a KIP that extends Kafka Connect Converter
> interface:
> >>
> >>
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-440%3A+Extend+Connect+Converter+to+support+headers
> >>
> >> Thanks for considering!
> >>
> >> --
> >> Yaroslav Tkachenko
> >> sap1ens.com
> >>
> >
>

Re: [VOTE] KIP-421: Automatically resolve external configurations.

2019-04-22 Thread TEJAL ADSUL

Hi Folks,

Just a reminder that I will be closing the vote for KIP-421 by today EOD, 
please cast your votes by today.

Thanks Colin, Randall, Gwen for the votes.

Thanks,
Tejal



On 2019/04/19 22:43:25, "Colin McCabe"  wrote: 
> +1.  Thanks, Tejal.
> 
> best,
> Colin
> 
> On Thu, Apr 18, 2019, at 15:02, TEJAL ADSUL wrote:
> > Hi All,
> > 
> > As we have reached a consensus on the design, I would like to start a 
> > vote for KIP-421. Below are the links for this proposal:
> > 
> > KIP Link: 
> > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=100829515
> > DiscussionThread: 
> > https://lists.apache.org/thread.html/a2f834d876e9f8fb3977db794bf161818c97f7f481edd1b10449d89f@%3Cdev.kafka.apache.org%3E
> > 
> > Thanks,
> > Tejal
> >
>

Re: [DISCUSS] KIP-440: Extend Connect Converter to support headers

2019-04-22 Thread Randall Hauch

Konstantine raises a good point. Which `Headers` is being referenced in the
API? The Connect `org.apache.kafka.connect.header.Headers` would correspond
to what was already deserialized by the `HeaderConverter` or what will yet
be serialized by the `HeaderConverter`. Alternatively, the common `
org.apache.kafka.common.header.Headers` would correspond to the raw header
pairs from the underlying Kafka record.

So, we probably want to be a bit more specific, and also mention why. And
we probably want to mention the other approach in the rejected alternatives.

Best regards,

Randall

On Mon, Apr 22, 2019 at 11:59 AM Konstantine Karantasis <
konstant...@confluent.io> wrote:

> Thanks for the KIP Yaroslav!
>
> Apologies for the late comment. However, after reading the KIP it's still
> not very clear to me what happens to the existing
> HeaderConverter interface and what's the expectation for existing code
> implementing this interface out there.
>
> Looking at the PR I see that the existing code is leaving the existing
> connect headers conversion unaffected. I'd expect by reading the KIP to
> understand what's the interplay of the current proposal with the existing
> implementation of KIP-145 that introduced headers in Connect.
>
> Thanks,
> Konstantine
>
> On Mon, Apr 22, 2019 at 9:07 AM Randall Hauch  wrote:
>
> > Thanks for updating the KIP. It looks good to me, and since there haven't
> > been any other issue mentioned in this month-long thread, it's probably
> > fine to start a vote.
> >
> > Best regards,
> >
> > Randall
> >
> > On Tue, Apr 2, 2019 at 3:12 PM Randall Hauch  wrote:
> >
> > > Thanks for the submission, Yaroslav -- and for building on the
> suggestion
> > > of Jeremy C in https://issues.apache.org/jira/browse/KAFKA-7273. This
> is
> > > a nice and simple approach that is backward compatible.
> > >
> > > The KIP looks good so far, but I do have two specific suggestions to
> make
> > > things just a bit more explicit. First, both the "Public API" and
> > "Proposed
> > > Changes" sections could be more explicit that the methods in the
> proposal
> > > are being added; as it's currently written a reader must infer that.
> > > Second, the "Proposed Changes" section needs to more clearly specify
> that
> > > the WorkerSourceTask will now use the new fromConnectData method with
> the
> > > headers instead of the existing method, and that the WorkerSinkTask
> will
> > > now use the toConnectData method with the headers instead of the
> existing
> > > method.
> > >
> > > Best regards,
> > >
> > > Randall
> > >
> > >
> > > On Mon, Mar 11, 2019 at 11:01 PM Yaroslav Tkachenko <
> sapie...@gmail.com>
> > > wrote:
> > >
> > >> Hello,
> > >>
> > >> I'd like to propose a KIP that extends Kafka Connect Converter
> > interface:
> > >>
> > >>
> >
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-440%3A+Extend+Connect+Converter+to+support+headers
> > >>
> > >> Thanks for considering!
> > >>
> > >> --
> > >> Yaroslav Tkachenko
> > >> sap1ens.com
> > >>
> > >
> >
>

Re: [DISCUSS] KIP-440: Extend Connect Converter to support headers

2019-04-22 Thread sapiensy

Hi Konstantine, Randall,

As you can see in the updated Converter interface, it always operates on 
`org.apache.kafka.common.header.Headers`. 

WorkerSinkTask simply uses Kafka message headers and passes them to the 
`toConnectData` method.

WorkerSourceTask leverages header converter to extract RecordHeaders, which 
implements Headers interface. Then RecordHeaders are passed to the 
`fromConnectData` method.

So header converter is used as a way to get headers when converting data from 
internal Connect format to Kafka messages (cause there is no other way to get 
the headers in this case).

I can add this to the KIP if it's helpful.

Randall, what is the alternative approach you're referring to?

On 2019/04/22 18:09:24, Randall Hauch  wrote: 
> Konstantine raises a good point. Which `Headers` is being referenced in the
> API? The Connect `org.apache.kafka.connect.header.Headers` would correspond
> to what was already deserialized by the `HeaderConverter` or what will yet
> be serialized by the `HeaderConverter`. Alternatively, the common `
> org.apache.kafka.common.header.Headers` would correspond to the raw header
> pairs from the underlying Kafka record.
> 
> So, we probably want to be a bit more specific, and also mention why. And
> we probably want to mention the other approach in the rejected alternatives.
> 
> Best regards,
> 
> Randall
> 
> On Mon, Apr 22, 2019 at 11:59 AM Konstantine Karantasis <
> konstant...@confluent.io> wrote:
> 
> > Thanks for the KIP Yaroslav!
> >
> > Apologies for the late comment. However, after reading the KIP it's still
> > not very clear to me what happens to the existing
> > HeaderConverter interface and what's the expectation for existing code
> > implementing this interface out there.
> >
> > Looking at the PR I see that the existing code is leaving the existing
> > connect headers conversion unaffected. I'd expect by reading the KIP to
> > understand what's the interplay of the current proposal with the existing
> > implementation of KIP-145 that introduced headers in Connect.
> >
> > Thanks,
> > Konstantine
> >
> > On Mon, Apr 22, 2019 at 9:07 AM Randall Hauch  wrote:
> >
> > > Thanks for updating the KIP. It looks good to me, and since there haven't
> > > been any other issue mentioned in this month-long thread, it's probably
> > > fine to start a vote.
> > >
> > > Best regards,
> > >
> > > Randall
> > >
> > > On Tue, Apr 2, 2019 at 3:12 PM Randall Hauch  wrote:
> > >
> > > > Thanks for the submission, Yaroslav -- and for building on the
> > suggestion
> > > > of Jeremy C in https://issues.apache.org/jira/browse/KAFKA-7273. This
> > is
> > > > a nice and simple approach that is backward compatible.
> > > >
> > > > The KIP looks good so far, but I do have two specific suggestions to
> > make
> > > > things just a bit more explicit. First, both the "Public API" and
> > > "Proposed
> > > > Changes" sections could be more explicit that the methods in the
> > proposal
> > > > are being added; as it's currently written a reader must infer that.
> > > > Second, the "Proposed Changes" section needs to more clearly specify
> > that
> > > > the WorkerSourceTask will now use the new fromConnectData method with
> > the
> > > > headers instead of the existing method, and that the WorkerSinkTask
> > will
> > > > now use the toConnectData method with the headers instead of the
> > existing
> > > > method.
> > > >
> > > > Best regards,
> > > >
> > > > Randall
> > > >
> > > >
> > > > On Mon, Mar 11, 2019 at 11:01 PM Yaroslav Tkachenko <
> > sapie...@gmail.com>
> > > > wrote:
> > > >
> > > >> Hello,
> > > >>
> > > >> I'd like to propose a KIP that extends Kafka Connect Converter
> > > interface:
> > > >>
> > > >>
> > >
> > https://cwiki.apache.org/confluence/display/KAFKA/KIP-440%3A+Extend+Connect+Converter+to+support+headers
> > > >>
> > > >> Thanks for considering!
> > > >>
> > > >> --
> > > >> Yaroslav Tkachenko
> > > >> sap1ens.com
> > > >>
> > > >
> > >
> >
>

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

2019-04-22 Thread Apache Jenkins Server

See 


Changes:

[github] MINOR: Add unit test for SerDe auto-configuration (#6610)

--
[...truncated 2.38 MB...]
org.apache.kafka.streams.test.OutputVerifierTest > 
shouldPassIfKeyAndValueAndTimestampIsEqualWithNullForCompareKeyValueTimestampWithProducerRecord
 PASSED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldFailIfValueIsDifferentWithNullForCompareKeyValueWithProducerRecord STARTED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldFailIfValueIsDifferentWithNullForCompareKeyValueWithProducerRecord PASSED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldFailIfValueIsDifferentForCompareKeyValueTimestampWithProducerRecord 
STARTED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldFailIfValueIsDifferentForCompareKeyValueTimestampWithProducerRecord PASSED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldNotAllowNullProducerRecordWithExpectedRecordForCompareValueTimestamp 
STARTED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldNotAllowNullProducerRecordWithExpectedRecordForCompareValueTimestamp 
PASSED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldNotAllowNullExpectedRecordForCompareValue STARTED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldNotAllowNullExpectedRecordForCompareValue PASSED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldFailIfValueIsDifferentWithNullReversForCompareKeyValueTimestampWithProducerRecord
 STARTED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldFailIfValueIsDifferentWithNullReversForCompareKeyValueTimestampWithProducerRecord
 PASSED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldNotAllowNullProducerRecordForCompareKeyValue STARTED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldNotAllowNullProducerRecordForCompareKeyValue PASSED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldFailIfValueIsDifferentWithNullReversForCompareKeyValueWithProducerRecord 
STARTED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldFailIfValueIsDifferentWithNullReversForCompareKeyValueWithProducerRecord 
PASSED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldPassIfKeyAndValueAndTimestampIsEqualForCompareKeyValueTimestamp STARTED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldPassIfKeyAndValueAndTimestampIsEqualForCompareKeyValueTimestamp PASSED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldFailIfValueIsDifferentWithNullForCompareKeyValueTimestampWithProducerRecord
 STARTED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldFailIfValueIsDifferentWithNullForCompareKeyValueTimestampWithProducerRecord
 PASSED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldFailIfKeyIsDifferentWithNullReversForCompareKeyValueWithProducerRecord 
STARTED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldFailIfKeyIsDifferentWithNullReversForCompareKeyValueWithProducerRecord 
PASSED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldPassIfKeyAndValueIsEqualWithNullForCompareKeyValueWithProducerRecord 
STARTED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldPassIfKeyAndValueIsEqualWithNullForCompareKeyValueWithProducerRecord 
PASSED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldFailIfKeyIsDifferentWithNullForCompareKeyValueTimestampWithProducerRecord 
STARTED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldFailIfKeyIsDifferentWithNullForCompareKeyValueTimestampWithProducerRecord 
PASSED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldFailIfValueIsDifferentForCompareKeyValueTimestamp STARTED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldFailIfValueIsDifferentForCompareKeyValueTimestamp PASSED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldPassIfValueAndTimestampIsEqualForCompareValueTimestampWithProducerRecord 
STARTED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldPassIfValueAndTimestampIsEqualForCompareValueTimestampWithProducerRecord 
PASSED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldFailIfValueIsDifferentWithNullReversForCompareKeyValueTimestamp STARTED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldFailIfValueIsDifferentWithNullReversForCompareKeyValueTimestamp PASSED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldFailIfValueIsDifferentWithNullReverseForCompareValueTimestampWithProducerRecord
 STARTED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldFailIfValueIsDifferentWithNullReverseForCompareValueTimestampWithProducerRecord
 PASSED

org.apache.kafka.streams.internals.KeyValueStoreFacadeTest > shouldReturnIsOpen 
STARTED

org.apache.kafka.streams.internals.KeyValueStoreFacadeTest > shouldReturnIsOpen 
PASSED

org.apache.kafka.streams.internals.KeyValueStoreFacadeTest > 
shouldDeleteAndReturnPlainValue STARTED

org.apache.kafka.streams.internals.KeyValu

Re: [DISCUSS] KIP-440: Extend Connect Converter to support headers

2019-04-22 Thread Randall Hauch

I think it would be helpful to clarify this in the KIP, just so that
readers are aware that the headers will be the raw header bytes that are
the same as what is in the Kafka record.

The alternative I was referring to is exposing the Connect `Headers`
interface, which is different.

On Mon, Apr 22, 2019 at 1:45 PM sapie...@gmail.com 
wrote:

> Hi Konstantine, Randall,
>
> As you can see in the updated Converter interface, it always operates on
> `org.apache.kafka.common.header.Headers`.
>
> WorkerSinkTask simply uses Kafka message headers and passes them to the
> `toConnectData` method.
>
> WorkerSourceTask leverages header converter to extract RecordHeaders,
> which implements Headers interface. Then RecordHeaders are passed to the
> `fromConnectData` method.
>
> So header converter is used as a way to get headers when converting data
> from internal Connect format to Kafka messages (cause there is no other way
> to get the headers in this case).
>
> I can add this to the KIP if it's helpful.
>
> Randall, what is the alternative approach you're referring to?
>
> On 2019/04/22 18:09:24, Randall Hauch  wrote:
> > Konstantine raises a good point. Which `Headers` is being referenced in
> the
> > API? The Connect `org.apache.kafka.connect.header.Headers` would
> correspond
> > to what was already deserialized by the `HeaderConverter` or what will
> yet
> > be serialized by the `HeaderConverter`. Alternatively, the common `
> > org.apache.kafka.common.header.Headers` would correspond to the raw
> header
> > pairs from the underlying Kafka record.
> >
> > So, we probably want to be a bit more specific, and also mention why. And
> > we probably want to mention the other approach in the rejected
> alternatives.
> >
> > Best regards,
> >
> > Randall
> >
> > On Mon, Apr 22, 2019 at 11:59 AM Konstantine Karantasis <
> > konstant...@confluent.io> wrote:
> >
> > > Thanks for the KIP Yaroslav!
> > >
> > > Apologies for the late comment. However, after reading the KIP it's
> still
> > > not very clear to me what happens to the existing
> > > HeaderConverter interface and what's the expectation for existing code
> > > implementing this interface out there.
> > >
> > > Looking at the PR I see that the existing code is leaving the existing
> > > connect headers conversion unaffected. I'd expect by reading the KIP to
> > > understand what's the interplay of the current proposal with the
> existing
> > > implementation of KIP-145 that introduced headers in Connect.
> > >
> > > Thanks,
> > > Konstantine
> > >
> > > On Mon, Apr 22, 2019 at 9:07 AM Randall Hauch 
> wrote:
> > >
> > > > Thanks for updating the KIP. It looks good to me, and since there
> haven't
> > > > been any other issue mentioned in this month-long thread, it's
> probably
> > > > fine to start a vote.
> > > >
> > > > Best regards,
> > > >
> > > > Randall
> > > >
> > > > On Tue, Apr 2, 2019 at 3:12 PM Randall Hauch 
> wrote:
> > > >
> > > > > Thanks for the submission, Yaroslav -- and for building on the
> > > suggestion
> > > > > of Jeremy C in https://issues.apache.org/jira/browse/KAFKA-7273.
> This
> > > is
> > > > > a nice and simple approach that is backward compatible.
> > > > >
> > > > > The KIP looks good so far, but I do have two specific suggestions
> to
> > > make
> > > > > things just a bit more explicit. First, both the "Public API" and
> > > > "Proposed
> > > > > Changes" sections could be more explicit that the methods in the
> > > proposal
> > > > > are being added; as it's currently written a reader must infer
> that.
> > > > > Second, the "Proposed Changes" section needs to more clearly
> specify
> > > that
> > > > > the WorkerSourceTask will now use the new fromConnectData method
> with
> > > the
> > > > > headers instead of the existing method, and that the WorkerSinkTask
> > > will
> > > > > now use the toConnectData method with the headers instead of the
> > > existing
> > > > > method.
> > > > >
> > > > > Best regards,
> > > > >
> > > > > Randall
> > > > >
> > > > >
> > > > > On Mon, Mar 11, 2019 at 11:01 PM Yaroslav Tkachenko <
> > > sapie...@gmail.com>
> > > > > wrote:
> > > > >
> > > > >> Hello,
> > > > >>
> > > > >> I'd like to propose a KIP that extends Kafka Connect Converter
> > > > interface:
> > > > >>
> > > > >>
> > > >
> > >
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-440%3A+Extend+Connect+Converter+to+support+headers
> > > > >>
> > > > >> Thanks for considering!
> > > > >>
> > > > >> --
> > > > >> Yaroslav Tkachenko
> > > > >> sap1ens.com
> > > > >>
> > > > >
> > > >
> > >
> >
>

[jira] [Created] (KAFKA-8277) Fix NPE in ConnectHeaders

2019-04-22 Thread Randall Hauch (JIRA)

Randall Hauch created KAFKA-8277:


 Summary: Fix NPE in ConnectHeaders
 Key: KAFKA-8277
 URL: https://issues.apache.org/jira/browse/KAFKA-8277
 Project: Kafka
  Issue Type: Bug
  Components: KafkaConnect
Affects Versions: 1.1.0
Reporter: Randall Hauch
 Fix For: 1.1.2, 2.0.2, 2.3.0, 2.1.2, 2.2.1


Replace {{headers.isEmpty()}} by calls to {{isEmpty()}} as the latter does a 
null check on heathers (that is lazily created).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (KAFKA-8277) Fix NPE in ConnectHeaders

2019-04-22 Thread Randall Hauch (JIRA)



 [ 
https://issues.apache.org/jira/browse/KAFKA-8277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Randall Hauch resolved KAFKA-8277.
--
Resolution: Fixed

> Fix NPE in ConnectHeaders
> -
>
> Key: KAFKA-8277
> URL: https://issues.apache.org/jira/browse/KAFKA-8277
> Project: Kafka
>  Issue Type: Bug
>  Components: KafkaConnect
>Affects Versions: 1.1.0
>Reporter: Randall Hauch
>Priority: Major
> Fix For: 1.1.2, 2.0.2, 2.3.0, 2.1.2, 2.2.1
>
>
> Replace {{headers.isEmpty()}} by calls to {{isEmpty()}} as the latter does a 
> null check on heathers (that is lazily created).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: [ANNOUNCE] New Kafka PMC member: Sriharsh Chintalapan

2019-04-22 Thread Colin McCabe

Congratulations, Harsh!

cheers,
Colin


On Thu, Apr 18, 2019, at 11:46, Jun Rao wrote:
> Hi, Everyone,
> 
> Sriharsh Chintalapan has been active in the Kafka community since he became
> a Kafka committer in 2015. I am glad to announce that Harsh is now a member
> of Kafka PM
> 
> Congratulations, Harsh!
> 
> Jun
>

[jira] [Resolved] (KAFKA-8204) Streams may flush state stores in the incorrect order

2019-04-22 Thread Guozhang Wang (JIRA)



 [ 
https://issues.apache.org/jira/browse/KAFKA-8204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guozhang Wang resolved KAFKA-8204.
--
   Resolution: Fixed
Fix Version/s: (was: 2.1.2)
   (was: 2.0.2)
   (was: 1.1.2)
   2.3.0

The latest PR has been merged to 2.2 / trunk, we will add more to fixed 
versions as we cherry-pick it to older branches via different PRs.

> Streams may flush state stores in the incorrect order
> -
>
> Key: KAFKA-8204
> URL: https://issues.apache.org/jira/browse/KAFKA-8204
> Project: Kafka
>  Issue Type: Improvement
>  Components: streams
>Affects Versions: 1.1.0, 1.1.1, 2.0.0, 2.0.1, 2.1.0, 2.2.0, 2.1.1
>Reporter: John Roesler
>Assignee: John Roesler
>Priority: Blocker
> Fix For: 2.3.0, 2.2.1
>
>
> Cached state stores may forward records during a flush call, so Streams 
> should flush the stores in topological order. Otherwise, Streams may flush a 
> downstream store before an upstream one, resulting in sink results being 
> committed without the corresponding state changelog updates being committed.
> This behavior is partly responsible for the bug reported in KAFKA-7895 .
> The fix is simply to flush the stores in topological order, then when the 
> upstream store forwards records to a downstream stateful processor, the 
> corresponding state changes will be correctly flushed as well.
> An alternative would be to repeatedly call flush on all state stores until 
> they report there is nothing left to flush, but this requires a public API 
> change to enable state stores to report whether they need a flush or not.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: [DISCUSS] KIP-458: Connector Client Config Override Policy

2019-04-22 Thread Chris Egerton

Hi Magesh,

This is an exciting KIP! I have a few questions/comments but overall I like
the direction it's headed in and hope to see it included in the Connect
framework soon.

1. With the proposed "consumer.", "producer.", and "admin." prefixes, how
will this interact with connectors such as the upcoming Mirror Maker 2.0
(KIP-382) that already support properties with those prefixes? Would it be
possible for a user to configure MM2 with those properties without them
being interpreted as Connect client overrides, without isolating MM2 onto
its own cluster and using the IgnoreConnectorClientConfigPolicy policy?
2. Is the IgnoreConnectorClientConfigPolicy class necessary? The default
for the connector.client.config.policy property could simply be null
instead of a new policy that, as far as I can tell, isn't an actual policy
in that its validate(...) method is never invoked and instead represents a
special case to the Connect framework that says "Drop all overrides and
never use me".
3. The PrincipalConnectorClientConfigPolicy seems like a specific instance
of a more general use case: allow exactly a small set of overrides and no
others. Why not generalize here and create a policy that accepts a list of
allowed overrides during configuration?

Thanks again for the KIP.

Cheers,

Chris

On Fri, Apr 19, 2019 at 2:53 PM Magesh Nandakumar 
wrote:

> Hi all,
>
> I've posted "KIP-458: Connector Client Config Override Policy", which
> allows users to override the connector client configurations based on a
> policy defined by the administrator.
>
> The KIP can be found at
>
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-458%3A+Connector+Client+Config+Override+Policy
> .
>
> Looking forward for the discussion on the KIP and all of your thoughts &
> feedback on this enhancement to Connect.
>
> Thanks,
> Magesh
>

Re: [VOTE] KIP-421: Automatically resolve external configurations.

2019-04-22 Thread Dongjin Lee

I just read the KIP. +1.

Currently:

Binding: +2 (Colin, Gwen)
Non-binding: +2 (Randall, Dongjin)

Thanks,
Dongjin

On Mon, Apr 22, 2019 at 10:26 AM TEJAL ADSUL  wrote:

> Hi Folks,
>
> Just a reminder that I will be closing the vote for KIP-421 by today EOD,
> please cast your votes by today.
>
> Thanks Colin, Randall, Gwen for the votes.
>
> Thanks,
> Tejal
>
>
>
> On 2019/04/19 22:43:25, "Colin McCabe"  wrote:
> > +1.  Thanks, Tejal.
> >
> > best,
> > Colin
> >
> > On Thu, Apr 18, 2019, at 15:02, TEJAL ADSUL wrote:
> > > Hi All,
> > >
> > > As we have reached a consensus on the design, I would like to start a
> > > vote for KIP-421. Below are the links for this proposal:
> > >
> > > KIP Link:
> > >
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=100829515
> > > DiscussionThread:
> > >
> https://lists.apache.org/thread.html/a2f834d876e9f8fb3977db794bf161818c97f7f481edd1b10449d89f@%3Cdev.kafka.apache.org%3E
> > >
> > > Thanks,
> > > Tejal
> > >
> >
>


-- 
*Dongjin Lee*

*A hitchhiker in the mathematical world.*
*github:  github.com/dongjinleekr
linkedin: kr.linkedin.com/in/dongjinleekr
speakerdeck: speakerdeck.com/dongjin
*

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

2019-04-22 Thread Apache Jenkins Server

See 


Changes:

[github] MINOR: Use https instead of http in links (#6477)

[github] MINOR: log which signals are handled on startup (#6620)

--
[...truncated 4.77 MB...]
org.apache.kafka.streams.test.OutputVerifierTest > 
shouldFailIfKeyIsDifferentWithNullReversForCompareKeyValue PASSED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldPassIfKeyAndValueIsEqualForCompareKeyValueWithProducerRecord STARTED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldPassIfKeyAndValueIsEqualForCompareKeyValueWithProducerRecord PASSED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldFailIfValueIsDifferentForCompareKeyValueWithProducerRecord STARTED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldFailIfValueIsDifferentForCompareKeyValueWithProducerRecord PASSED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldFailIfValueIsDifferentForCompareValueTimestamp STARTED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldFailIfValueIsDifferentForCompareValueTimestamp PASSED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldNotAllowNullProducerRecordForCompareValue STARTED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldNotAllowNullProducerRecordForCompareValue PASSED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldFailIfValueIsDifferentWithNullForCompareValueTimestamp STARTED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldFailIfValueIsDifferentWithNullForCompareValueTimestamp PASSED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldFailIfKeyIsDifferentForCompareKeyValueTimestamp STARTED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldFailIfKeyIsDifferentForCompareKeyValueTimestamp PASSED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldFailIfKeyIsDifferentForCompareKeyValueTimestampWithProducerRecord STARTED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldFailIfKeyIsDifferentForCompareKeyValueTimestampWithProducerRecord PASSED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldPassIfValueIsEqualWithNullForCompareValueWithProducerRecord STARTED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldPassIfValueIsEqualWithNullForCompareValueWithProducerRecord PASSED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldFailIfValueIsDifferentWithNullReverseForCompareValueTimestamp STARTED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldFailIfValueIsDifferentWithNullReverseForCompareValueTimestamp PASSED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldFailIfValueIsDifferentWithNullReverseForCompareValue STARTED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldFailIfValueIsDifferentWithNullReverseForCompareValue PASSED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldFailIfTimestampIsDifferentForCompareValueTimestamp STARTED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldFailIfTimestampIsDifferentForCompareValueTimestamp PASSED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldPassIfKeyAndValueAndTimestampIsEqualWithNullForCompareKeyValueTimestampWithProducerRecord
 STARTED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldPassIfKeyAndValueAndTimestampIsEqualWithNullForCompareKeyValueTimestampWithProducerRecord
 PASSED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldFailIfValueIsDifferentWithNullForCompareKeyValueWithProducerRecord STARTED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldFailIfValueIsDifferentWithNullForCompareKeyValueWithProducerRecord PASSED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldFailIfValueIsDifferentForCompareKeyValueTimestampWithProducerRecord 
STARTED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldFailIfValueIsDifferentForCompareKeyValueTimestampWithProducerRecord PASSED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldNotAllowNullProducerRecordWithExpectedRecordForCompareValueTimestamp 
STARTED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldNotAllowNullProducerRecordWithExpectedRecordForCompareValueTimestamp 
PASSED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldNotAllowNullExpectedRecordForCompareValue STARTED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldNotAllowNullExpectedRecordForCompareValue PASSED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldFailIfValueIsDifferentWithNullReversForCompareKeyValueTimestampWithProducerRecord
 STARTED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldFailIfValueIsDifferentWithNullReversForCompareKeyValueTimestampWithProducerRecord
 PASSED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldNotAllowNullProducerRecordForCompareKeyValue STARTED

org.apache.kafka.streams.test.OutputVerifierTest > 
shouldNotAllowNullProducerRecordForCompareKeyValue PASSED

org.apache.kafka.streams.test.OutputVerifierTest >

Build failed in Jenkins: kafka-2.0-jdk8 #253

2019-04-22 Thread Apache Jenkins Server

See 


Changes:

[rhauch] KAFKA-8277: Fix NPEs in several methods of ConnectHeaders (#6550)

--
[...truncated 440.23 KB...]
kafka.log.LogCleanerManagerTest > 
testLogsWithSegmentsToDeleteShouldNotConsiderCleanupPolicyDeleteLogs PASSED

kafka.log.LogCleanerManagerTest > testCleanableOffsetsForShortTime STARTED

kafka.log.LogCleanerManagerTest > testCleanableOffsetsForShortTime PASSED

kafka.log.LogCleanerManagerTest > testDoneCleaning STARTED

kafka.log.LogCleanerManagerTest > testDoneCleaning PASSED

kafka.log.LogCleanerManagerTest > testDoneDeleting STARTED

kafka.log.LogCleanerManagerTest > testDoneDeleting PASSED

kafka.log.ProducerStateManagerTest > 
testProducerSequenceWithWrapAroundBatchRecord STARTED

kafka.log.ProducerStateManagerTest > 
testProducerSequenceWithWrapAroundBatchRecord PASSED

kafka.log.ProducerStateManagerTest > testCoordinatorFencing STARTED

kafka.log.ProducerStateManagerTest > testCoordinatorFencing PASSED

kafka.log.ProducerStateManagerTest > testTruncate STARTED

kafka.log.ProducerStateManagerTest > testTruncate PASSED

kafka.log.ProducerStateManagerTest > testLoadFromTruncatedSnapshotFile STARTED

kafka.log.ProducerStateManagerTest > testLoadFromTruncatedSnapshotFile PASSED

kafka.log.ProducerStateManagerTest > testRemoveExpiredPidsOnReload STARTED

kafka.log.ProducerStateManagerTest > testRemoveExpiredPidsOnReload PASSED

kafka.log.ProducerStateManagerTest > 
testOutOfSequenceAfterControlRecordEpochBump STARTED

kafka.log.ProducerStateManagerTest > 
testOutOfSequenceAfterControlRecordEpochBump PASSED

kafka.log.ProducerStateManagerTest > testFirstUnstableOffsetAfterTruncation 
STARTED

kafka.log.ProducerStateManagerTest > testFirstUnstableOffsetAfterTruncation 
PASSED

kafka.log.ProducerStateManagerTest > testTakeSnapshot STARTED

kafka.log.ProducerStateManagerTest > testTakeSnapshot PASSED

kafka.log.ProducerStateManagerTest > testDeleteSnapshotsBefore STARTED

kafka.log.ProducerStateManagerTest > testDeleteSnapshotsBefore PASSED

kafka.log.ProducerStateManagerTest > 
testNonMatchingTxnFirstOffsetMetadataNotCached STARTED

kafka.log.ProducerStateManagerTest > 
testNonMatchingTxnFirstOffsetMetadataNotCached PASSED

kafka.log.ProducerStateManagerTest > testAppendEmptyControlBatch STARTED

kafka.log.ProducerStateManagerTest > testAppendEmptyControlBatch PASSED

kafka.log.ProducerStateManagerTest > testFirstUnstableOffsetAfterEviction 
STARTED

kafka.log.ProducerStateManagerTest > testFirstUnstableOffsetAfterEviction PASSED

kafka.log.ProducerStateManagerTest > testNoValidationOnFirstEntryWhenLoadingLog 
STARTED

kafka.log.ProducerStateManagerTest > testNoValidationOnFirstEntryWhenLoadingLog 
PASSED

kafka.log.ProducerStateManagerTest > testLoadFromEmptySnapshotFile STARTED

kafka.log.ProducerStateManagerTest > testLoadFromEmptySnapshotFile PASSED

kafka.log.ProducerStateManagerTest > 
testProducersWithOngoingTransactionsDontExpire STARTED

kafka.log.ProducerStateManagerTest > 
testProducersWithOngoingTransactionsDontExpire PASSED

kafka.log.ProducerStateManagerTest > testBasicIdMapping STARTED

kafka.log.ProducerStateManagerTest > testBasicIdMapping PASSED

kafka.log.ProducerStateManagerTest > updateProducerTransactionState STARTED

kafka.log.ProducerStateManagerTest > updateProducerTransactionState PASSED

kafka.log.ProducerStateManagerTest > testRecoverFromSnapshot STARTED

kafka.log.ProducerStateManagerTest > testRecoverFromSnapshot PASSED

kafka.log.ProducerStateManagerTest > testPrepareUpdateDoesNotMutate STARTED

kafka.log.ProducerStateManagerTest > testPrepareUpdateDoesNotMutate PASSED

kafka.log.ProducerStateManagerTest > 
testSequenceNotValidatedForGroupMetadataTopic STARTED

kafka.log.ProducerStateManagerTest > 
testSequenceNotValidatedForGroupMetadataTopic PASSED

kafka.log.ProducerStateManagerTest > testLastStableOffsetCompletedTxn STARTED

kafka.log.ProducerStateManagerTest > testLastStableOffsetCompletedTxn PASSED

kafka.log.ProducerStateManagerTest > 
testLoadFromSnapshotRemovesNonRetainedProducers STARTED

kafka.log.ProducerStateManagerTest > 
testLoadFromSnapshotRemovesNonRetainedProducers PASSED

kafka.log.ProducerStateManagerTest > testFirstUnstableOffset STARTED

kafka.log.ProducerStateManagerTest > testFirstUnstableOffset PASSED

kafka.log.ProducerStateManagerTest > testTxnFirstOffsetMetadataCached STARTED

kafka.log.ProducerStateManagerTest > testTxnFirstOffsetMetadataCached PASSED

kafka.log.ProducerStateManagerTest > testCoordinatorFencedAfterReload STARTED

kafka.log.ProducerStateManagerTest > testCoordinatorFencedAfterReload PASSED

kafka.log.ProducerStateManagerTest > testControlRecordBumpsEpoch STARTED

kafka.log.ProducerStateManagerTest > testControlRecordBumpsEpoch PASSED

kafka.log.ProducerStateManagerTest > 
testAcceptAppendWithoutProducerStateOnReplica STARTED

kafka.log.ProducerStateManagerTest > 
testAcceptAppendWithoutProduce

Build failed in Jenkins: kafka-1.1-jdk7 #261

2019-04-22 Thread Apache Jenkins Server

See 


Changes:

[rhauch] KAFKA-8277: Fix NPEs in several methods of ConnectHeaders (#6550)

--
[...truncated 426.29 KB...]
kafka.server.KafkaConfigTest > testValidCompressionType PASSED

kafka.server.KafkaConfigTest > testUncleanElectionInvalid STARTED

kafka.server.KafkaConfigTest > testUncleanElectionInvalid PASSED

kafka.server.KafkaConfigTest > testListenerNamesWithAdvertisedListenerUnset 
STARTED

kafka.server.KafkaConfigTest > testListenerNamesWithAdvertisedListenerUnset 
PASSED

kafka.server.KafkaConfigTest > testLogRetentionTimeBothMinutesAndMsProvided 
STARTED

kafka.server.KafkaConfigTest > testLogRetentionTimeBothMinutesAndMsProvided 
PASSED

kafka.server.KafkaConfigTest > testLogRollTimeMsProvided STARTED

kafka.server.KafkaConfigTest > testLogRollTimeMsProvided PASSED

kafka.server.KafkaConfigTest > testUncleanLeaderElectionDefault STARTED

kafka.server.KafkaConfigTest > testUncleanLeaderElectionDefault PASSED

kafka.server.KafkaConfigTest > testInvalidAdvertisedListenersProtocol STARTED

kafka.server.KafkaConfigTest > testInvalidAdvertisedListenersProtocol PASSED

kafka.server.KafkaConfigTest > testUncleanElectionEnabled STARTED

kafka.server.KafkaConfigTest > testUncleanElectionEnabled PASSED

kafka.server.KafkaConfigTest > testInterBrokerVersionMessageFormatCompatibility 
STARTED

kafka.server.KafkaConfigTest > testInterBrokerVersionMessageFormatCompatibility 
PASSED

kafka.server.KafkaConfigTest > testAdvertisePortDefault STARTED

kafka.server.KafkaConfigTest > testAdvertisePortDefault PASSED

kafka.server.KafkaConfigTest > testVersionConfiguration STARTED

kafka.server.KafkaConfigTest > testVersionConfiguration PASSED

kafka.server.KafkaConfigTest > testEqualAdvertisedListenersProtocol STARTED

kafka.server.KafkaConfigTest > testEqualAdvertisedListenersProtocol PASSED

kafka.server.CreateTopicsRequestTest > testValidCreateTopicsRequests STARTED

kafka.server.CreateTopicsRequestTest > testValidCreateTopicsRequests PASSED

kafka.server.CreateTopicsRequestTest > testErrorCreateTopicsRequests STARTED

kafka.server.CreateTopicsRequestTest > testErrorCreateTopicsRequests PASSED

kafka.server.CreateTopicsRequestTest > testInvalidCreateTopicsRequests STARTED

kafka.server.CreateTopicsRequestTest > testInvalidCreateTopicsRequests PASSED

kafka.server.CreateTopicsRequestTest > testNotController STARTED

kafka.server.CreateTopicsRequestTest > testNotController PASSED

kafka.server.CreateTopicsRequestWithPolicyTest > testValidCreateTopicsRequests 
STARTED

kafka.server.CreateTopicsRequestWithPolicyTest > testValidCreateTopicsRequests 
PASSED

kafka.server.CreateTopicsRequestWithPolicyTest > testErrorCreateTopicsRequests 
STARTED

kafka.server.CreateTopicsRequestWithPolicyTest > testErrorCreateTopicsRequests 
PASSED

kafka.server.SaslApiVersionsRequestTest > 
testApiVersionsRequestWithUnsupportedVersion STARTED

kafka.server.SaslApiVersionsRequestTest > 
testApiVersionsRequestWithUnsupportedVersion PASSED

kafka.server.SaslApiVersionsRequestTest > 
testApiVersionsRequestBeforeSaslHandshakeRequest STARTED

kafka.server.SaslApiVersionsRequestTest > 
testApiVersionsRequestBeforeSaslHandshakeRequest PASSED

kafka.server.SaslApiVersionsRequestTest > 
testApiVersionsRequestAfterSaslHandshakeRequest STARTED

kafka.server.SaslApiVersionsRequestTest > 
testApiVersionsRequestAfterSaslHandshakeRequest PASSED

kafka.server.LogDirFailureTest > testIOExceptionDuringLogRoll STARTED

kafka.server.LogDirFailureTest > testIOExceptionDuringLogRoll PASSED

kafka.server.LogDirFailureTest > testIOExceptionDuringCheckpoint STARTED

kafka.server.LogDirFailureTest > testIOExceptionDuringCheckpoint PASSED

kafka.server.LogDirFailureTest > 
brokerWithOldInterBrokerProtocolShouldHaltOnLogDirFailure STARTED

kafka.server.LogDirFailureTest > 
brokerWithOldInterBrokerProtocolShouldHaltOnLogDirFailure PASSED

kafka.server.LogDirFailureTest > 
testReplicaFetcherThreadAfterLogDirFailureOnFollower STARTED

kafka.server.LogDirFailureTest > 
testReplicaFetcherThreadAfterLogDirFailureOnFollower PASSED

kafka.server.AlterReplicaLogDirsRequestTest > testAlterReplicaLogDirsRequest 
STARTED

kafka.server.AlterReplicaLogDirsRequestTest > testAlterReplicaLogDirsRequest 
PASSED

kafka.server.AlterReplicaLogDirsRequestTest > 
testAlterReplicaLogDirsRequestErrorCode STARTED

kafka.server.AlterReplicaLogDirsRequestTest > 
testAlterReplicaLogDirsRequestErrorCode PASSED

kafka.server.ServerGenerateBrokerIdTest > testGetSequenceIdMethod STARTED

kafka.server.ServerGenerateBrokerIdTest > testGetSequenceIdMethod PASSED

kafka.server.ServerGenerateBrokerIdTest > testBrokerMetadataOnIdCollision 
STARTED

kafka.server.ServerGenerateBrokerIdTest > testBrokerMetadataOnIdCollision PASSED

kafka.server.ServerGenerateBrokerIdTest > testAutoGenerateBrokerId STARTED

kafka.server.ServerGenerateBrokerIdTest > testAutoGenerateBrokerId PASSED

kaf

Re: [VOTE] KIP-421: Automatically resolve external configurations.

2019-04-22 Thread TEJAL ADSUL

Hi all,

This KIP passes with three +1 (binding) - thanks Colin, Randall and Gwen!

For those interested, feel free to check out and join the ongoing PR review
here: https://github.com/apache/kafka/pull/6467

Thanks,
Tejal

On 2019/04/22 17:26:05, TEJAL ADSUL  wrote: 
> Hi Folks,
> 
> Just a reminder that I will be closing the vote for KIP-421 by today EOD, 
> please cast your votes by today.
> 
> Thanks Colin, Randall, Gwen for the votes.
> 
> Thanks,
> Tejal
> 
> 
> 
> On 2019/04/19 22:43:25, "Colin McCabe"  wrote: 
> > +1.  Thanks, Tejal.
> > 
> > best,
> > Colin
> > 
> > On Thu, Apr 18, 2019, at 15:02, TEJAL ADSUL wrote:
> > > Hi All,
> > > 
> > > As we have reached a consensus on the design, I would like to start a 
> > > vote for KIP-421. Below are the links for this proposal:
> > > 
> > > KIP Link: 
> > > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=100829515
> > > DiscussionThread: 
> > > https://lists.apache.org/thread.html/a2f834d876e9f8fb3977db794bf161818c97f7f481edd1b10449d89f@%3Cdev.kafka.apache.org%3E
> > > 
> > > Thanks,
> > > Tejal
> > >
> > 
>

Build failed in Jenkins: kafka-2.2-jdk8 #88

2019-04-22 Thread Apache Jenkins Server

See 


Changes:

[rhauch] KAFKA-8277: Fix NPEs in several methods of ConnectHeaders (#6550)

[wangguoz] KAFKA-8204: fix Streams store flush order (#6555)

--
[...truncated 2.70 MB...]
kafka.controller.PartitionLeaderElectionAlgorithmsTest > 
testOfflinePartitionLeaderElectionLastIsrOfflineUncleanLeaderElectionEnabled 
STARTED

kafka.controller.PartitionLeaderElectionAlgorithmsTest > 
testOfflinePartitionLeaderElectionLastIsrOfflineUncleanLeaderElectionEnabled 
PASSED

kafka.controller.PartitionLeaderElectionAlgorithmsTest > 
testPreferredReplicaPartitionLeaderElectionPreferredReplicaNotInIsrNotLive 
STARTED

kafka.controller.PartitionLeaderElectionAlgorithmsTest > 
testPreferredReplicaPartitionLeaderElectionPreferredReplicaNotInIsrNotLive 
PASSED

kafka.controller.PartitionLeaderElectionAlgorithmsTest > 
testOfflinePartitionLeaderElectionLastIsrOfflineUncleanLeaderElectionDisabled 
STARTED

kafka.controller.PartitionLeaderElectionAlgorithmsTest > 
testOfflinePartitionLeaderElectionLastIsrOfflineUncleanLeaderElectionDisabled 
PASSED

kafka.controller.PartitionStateMachineTest > 
testNonexistentPartitionToNewPartitionTransition STARTED

kafka.controller.PartitionStateMachineTest > 
testNonexistentPartitionToNewPartitionTransition PASSED

kafka.controller.PartitionStateMachineTest > 
testNewPartitionToOnlinePartitionTransitionErrorCodeFromCreateStates STARTED

kafka.controller.PartitionStateMachineTest > 
testNewPartitionToOnlinePartitionTransitionErrorCodeFromCreateStates PASSED

kafka.controller.PartitionStateMachineTest > 
testOfflinePartitionToNonexistentPartitionTransition STARTED

kafka.controller.PartitionStateMachineTest > 
testOfflinePartitionToNonexistentPartitionTransition PASSED

kafka.controller.PartitionStateMachineTest > 
testOnlinePartitionToOfflineTransition STARTED

kafka.controller.PartitionStateMachineTest > 
testOnlinePartitionToOfflineTransition PASSED

kafka.controller.PartitionStateMachineTest > 
testNewPartitionToOfflinePartitionTransition STARTED

kafka.controller.PartitionStateMachineTest > 
testNewPartitionToOfflinePartitionTransition PASSED

kafka.controller.PartitionStateMachineTest > testUpdatingOfflinePartitionsCount 
STARTED

kafka.controller.PartitionStateMachineTest > testUpdatingOfflinePartitionsCount 
PASSED

kafka.controller.PartitionStateMachineTest > 
testInvalidNonexistentPartitionToOnlinePartitionTransition STARTED

kafka.controller.PartitionStateMachineTest > 
testInvalidNonexistentPartitionToOnlinePartitionTransition PASSED

kafka.controller.PartitionStateMachineTest > 
testInvalidNonexistentPartitionToOfflinePartitionTransition STARTED

kafka.controller.PartitionStateMachineTest > 
testInvalidNonexistentPartitionToOfflinePartitionTransition PASSED

kafka.controller.PartitionStateMachineTest > 
testOnlinePartitionToOnlineTransition STARTED

kafka.controller.PartitionStateMachineTest > 
testOnlinePartitionToOnlineTransition PASSED

kafka.controller.PartitionStateMachineTest > 
testNewPartitionToOnlinePartitionTransitionZkUtilsExceptionFromCreateStates 
STARTED

kafka.controller.PartitionStateMachineTest > 
testNewPartitionToOnlinePartitionTransitionZkUtilsExceptionFromCreateStates 
PASSED

kafka.controller.PartitionStateMachineTest > 
testInvalidNewPartitionToNonexistentPartitionTransition STARTED

kafka.controller.PartitionStateMachineTest > 
testInvalidNewPartitionToNonexistentPartitionTransition PASSED

kafka.controller.PartitionStateMachineTest > 
testNewPartitionToOnlinePartitionTransition STARTED

kafka.controller.PartitionStateMachineTest > 
testNewPartitionToOnlinePartitionTransition PASSED

kafka.controller.PartitionStateMachineTest > 
testInvalidOnlinePartitionToNewPartitionTransition STARTED

kafka.controller.PartitionStateMachineTest > 
testInvalidOnlinePartitionToNewPartitionTransition PASSED

kafka.controller.PartitionStateMachineTest > 
testUpdatingOfflinePartitionsCountDuringTopicDeletion STARTED

kafka.controller.PartitionStateMachineTest > 
testUpdatingOfflinePartitionsCountDuringTopicDeletion PASSED

kafka.controller.PartitionStateMachineTest > 
testOfflinePartitionToOnlinePartitionTransitionErrorCodeFromStateLookup STARTED

kafka.controller.PartitionStateMachineTest > 
testOfflinePartitionToOnlinePartitionTransitionErrorCodeFromStateLookup PASSED

kafka.controller.PartitionStateMachineTest > 
testOnlinePartitionToOnlineTransitionForControlledShutdown STARTED

kafka.controller.PartitionStateMachineTest > 
testOnlinePartitionToOnlineTransitionForControlledShutdown PASSED

kafka.controller.PartitionStateMachineTest > 
testOfflinePartitionToOnlinePartitionTransitionZkUtilsExceptionFromStateLookup 
STARTED

kafka.controller.PartitionStateMachineTest > 
testOfflinePartitionToOnlinePartitionTransitionZkUtilsExceptionFromStateLookup 
PASSED

kafka.controller.PartitionStateMachineTest > 
testNoOfflinePartitionsChangeForTopicsBeingDeleted S

Re: [ANNOUNCE] New Kafka PMC member: Matthias J. Sax

2019-04-22 Thread Becket Qin

Congrats, Matthias!

On Sat, Apr 20, 2019 at 10:28 AM Matthias J. Sax 
wrote:

> Thank you all!
>
> -Matthias
>
>
> On 4/19/19 3:58 PM, Lei Chen wrote:
> > Congratulations Matthias! Well deserved!
> >
> > -Lei
> >
> > On Fri, Apr 19, 2019 at 2:55 PM James Cheng  > > wrote:
> >
> > Congrats!!
> >
> > -James
> >
> > Sent from my iPhone
> >
> > > On Apr 18, 2019, at 2:35 PM, Guozhang Wang  > > wrote:
> > >
> > > Hello Everyone,
> > >
> > > I'm glad to announce that Matthias J. Sax is now a member of Kafka
> > PMC.
> > >
> > > Matthias has been a committer since Jan. 2018, and since then he
> > continued
> > > to be active in the community and made significant contributions
> the
> > > project.
> > >
> > >
> > > Congratulations to Matthias!
> > >
> > > -- Guozhang
> >
>
>

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

2019-04-22 Thread Apache Jenkins Server

See 


Changes:

[rhauch] KAFKA-8277: Fix NPEs in several methods of ConnectHeaders (#6550)

[wangguoz] KAFKA-8204: fix Streams store flush order (#6555)

[github] MINOR: Move log statement stating producer closed after possible

--
[...truncated 2.38 MB...]
org.apache.kafka.connect.converters.FloatConverterTest > 
testSerializingIncorrectHeader STARTED

org.apache.kafka.connect.converters.FloatConverterTest > 
testSerializingIncorrectHeader PASSED

org.apache.kafka.connect.converters.FloatConverterTest > 
testDeserializingDataWithTooManyBytes STARTED

org.apache.kafka.connect.converters.FloatConverterTest > 
testDeserializingDataWithTooManyBytes PASSED

org.apache.kafka.connect.converters.FloatConverterTest > 
testConvertingSamplesToAndFromBytes STARTED

org.apache.kafka.connect.converters.FloatConverterTest > 
testConvertingSamplesToAndFromBytes PASSED

org.apache.kafka.connect.converters.ByteArrayConverterTest > 
testFromConnectSchemaless STARTED

org.apache.kafka.connect.converters.ByteArrayConverterTest > 
testFromConnectSchemaless PASSED

org.apache.kafka.connect.converters.ByteArrayConverterTest > testToConnectNull 
STARTED

org.apache.kafka.connect.converters.ByteArrayConverterTest > testToConnectNull 
PASSED

org.apache.kafka.connect.converters.ByteArrayConverterTest > 
testFromConnectBadSchema STARTED

org.apache.kafka.connect.converters.ByteArrayConverterTest > 
testFromConnectBadSchema PASSED

org.apache.kafka.connect.converters.ByteArrayConverterTest > 
testFromConnectNull STARTED

org.apache.kafka.connect.converters.ByteArrayConverterTest > 
testFromConnectNull PASSED

org.apache.kafka.connect.converters.ByteArrayConverterTest > testToConnect 
STARTED

org.apache.kafka.connect.converters.ByteArrayConverterTest > testToConnect 
PASSED

org.apache.kafka.connect.converters.ByteArrayConverterTest > testFromConnect 
STARTED

org.apache.kafka.connect.converters.ByteArrayConverterTest > testFromConnect 
PASSED

org.apache.kafka.connect.converters.ByteArrayConverterTest > 
testFromConnectInvalidValue STARTED

org.apache.kafka.connect.converters.ByteArrayConverterTest > 
testFromConnectInvalidValue PASSED

> Task :streams:streams-scala:test

org.apache.kafka.streams.scala.WordCountTest > testShouldCountWordsMaterialized 
STARTED

org.apache.kafka.streams.scala.WordCountTest > testShouldCountWordsMaterialized 
PASSED

org.apache.kafka.streams.scala.WordCountTest > testShouldCountWordsJava STARTED

org.apache.kafka.streams.scala.WordCountTest > testShouldCountWordsJava PASSED

org.apache.kafka.streams.scala.WordCountTest > testShouldCountWords STARTED

org.apache.kafka.streams.scala.WordCountTest > testShouldCountWords PASSED

org.apache.kafka.streams.scala.kstream.KTableTest > filter a KTable should 
filter records satisfying the predicate STARTED

org.apache.kafka.streams.scala.kstream.KTableTest > filter a KTable should 
filter records satisfying the predicate PASSED

org.apache.kafka.streams.scala.kstream.KTableTest > filterNot a KTable should 
filter records not satisfying the predicate STARTED

org.apache.kafka.streams.scala.kstream.KTableTest > filterNot a KTable should 
filter records not satisfying the predicate PASSED

org.apache.kafka.streams.scala.kstream.KTableTest > join 2 KTables should join 
correctly records STARTED

org.apache.kafka.streams.scala.kstream.KTableTest > join 2 KTables should join 
correctly records PASSED

org.apache.kafka.streams.scala.kstream.KTableTest > join 2 KTables with a 
Materialized should join correctly records and state store STARTED

org.apache.kafka.streams.scala.kstream.KTableTest > join 2 KTables with a 
Materialized should join correctly records and state store PASSED

org.apache.kafka.streams.scala.kstream.KTableTest > windowed KTable#suppress 
should correctly suppress results using Suppressed.untilTimeLimit STARTED

org.apache.kafka.streams.scala.kstream.KTableTest > windowed KTable#suppress 
should correctly suppress results using Suppressed.untilTimeLimit PASSED

org.apache.kafka.streams.scala.kstream.KTableTest > windowed KTable#suppress 
should correctly suppress results using Suppressed.untilWindowCloses STARTED

org.apache.kafka.streams.scala.kstream.KTableTest > windowed KTable#suppress 
should correctly suppress results using Suppressed.untilWindowCloses PASSED

org.apache.kafka.streams.scala.kstream.KTableTest > session windowed 
KTable#suppress should correctly suppress results using 
Suppressed.untilWindowCloses STARTED

org.apache.kafka.streams.scala.kstream.KTableTest > session windowed 
KTable#suppress should correctly suppress results using 
Suppressed.untilWindowCloses PASSED

org.apache.kafka.streams.scala.kstream.KTableTest > non-windowed 
KTable#suppress should correctly suppress results using 
Suppressed.untilTimeLimit STARTED

org.apache.kafka.streams.scala.kstream.KTableTest > non-windowed 
KTable#suppress sho

Re: [ANNOUNCE] New Kafka PMC member: Sriharsh Chintalapan

2019-04-22 Thread Becket Qin

Congrats, Harsh!

On Tue, Apr 23, 2019 at 5:41 AM Colin McCabe  wrote:

> Congratulations, Harsh!
>
> cheers,
> Colin
>
>
> On Thu, Apr 18, 2019, at 11:46, Jun Rao wrote:
> > Hi, Everyone,
> >
> > Sriharsh Chintalapan has been active in the Kafka community since he
> became
> > a Kafka committer in 2015. I am glad to announce that Harsh is now a
> member
> > of Kafka PM
> >
> > Congratulations, Harsh!
> >
> > Jun
> >
>

Re: [VOTE] KIP-421: Automatically resolve external configurations.

2019-04-22 Thread Colin McCabe

Hi Dongjin,

Thanks for checking out the KIP.

Randall is a committer, actually.  He was added two months ago.  It looks like 
he isn't on the committers page yet, though.

Randall, can you add your name to https://kafka.apache.org/committers.html to 
help prevent confusion in the future?

best,
Colin


On Mon, Apr 22, 2019, at 16:44, Dongjin Lee wrote:
> I just read the KIP. +1.
> 
> Currently:
> 
> Binding: +2 (Colin, Gwen)
> Non-binding: +2 (Randall, Dongjin)
> 
> Thanks,
> Dongjin
> 
> On Mon, Apr 22, 2019 at 10:26 AM TEJAL ADSUL  wrote:
> 
> > Hi Folks,
> >
> > Just a reminder that I will be closing the vote for KIP-421 by today EOD,
> > please cast your votes by today.
> >
> > Thanks Colin, Randall, Gwen for the votes.
> >
> > Thanks,
> > Tejal
> >
> >
> >
> > On 2019/04/19 22:43:25, "Colin McCabe"  wrote:
> > > +1.  Thanks, Tejal.
> > >
> > > best,
> > > Colin
> > >
> > > On Thu, Apr 18, 2019, at 15:02, TEJAL ADSUL wrote:
> > > > Hi All,
> > > >
> > > > As we have reached a consensus on the design, I would like to start a
> > > > vote for KIP-421. Below are the links for this proposal:
> > > >
> > > > KIP Link:
> > > >
> > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=100829515
> > > > DiscussionThread:
> > > >
> > https://lists.apache.org/thread.html/a2f834d876e9f8fb3977db794bf161818c97f7f481edd1b10449d89f@%3Cdev.kafka.apache.org%3E
> > > >
> > > > Thanks,
> > > > Tejal
> > > >
> > >
> >
> 
> 
> -- 
> *Dongjin Lee*
> 
> *A hitchhiker in the mathematical world.*
> *github:  github.com/dongjinleekr
> linkedin: kr.linkedin.com/in/dongjinleekr
> speakerdeck: speakerdeck.com/dongjin
> *
>

Build failed in Jenkins: kafka-2.2-jdk8 #89

2019-04-22 Thread Apache Jenkins Server

See 


Changes:

[bbejeck] KAFKA-7895: fix Suppress changelog restore (#6536) (#6615)

--
[...truncated 2.70 MB...]
kafka.controller.PartitionStateMachineTest > 
testOnlinePartitionToOnlineTransitionForControlledShutdown PASSED

kafka.controller.PartitionStateMachineTest > 
testOfflinePartitionToOnlinePartitionTransitionZkUtilsExceptionFromStateLookup 
STARTED

kafka.controller.PartitionStateMachineTest > 
testOfflinePartitionToOnlinePartitionTransitionZkUtilsExceptionFromStateLookup 
PASSED

kafka.controller.PartitionStateMachineTest > 
testNoOfflinePartitionsChangeForTopicsBeingDeleted STARTED

kafka.controller.PartitionStateMachineTest > 
testNoOfflinePartitionsChangeForTopicsBeingDeleted PASSED

kafka.controller.PartitionStateMachineTest > 
testInvalidOnlinePartitionToNonexistentPartitionTransition STARTED

kafka.controller.PartitionStateMachineTest > 
testInvalidOnlinePartitionToNonexistentPartitionTransition PASSED

kafka.controller.PartitionStateMachineTest > 
testInvalidOfflinePartitionToNewPartitionTransition STARTED

kafka.controller.PartitionStateMachineTest > 
testInvalidOfflinePartitionToNewPartitionTransition PASSED

kafka.controller.PartitionStateMachineTest > 
testOfflinePartitionToOnlinePartitionTransition STARTED

kafka.controller.PartitionStateMachineTest > 
testOfflinePartitionToOnlinePartitionTransition PASSED

kafka.controller.ControllerEventManagerTest > testEventThatThrowsException 
STARTED

kafka.controller.ControllerEventManagerTest > testEventThatThrowsException 
PASSED

kafka.controller.ControllerEventManagerTest > testSuccessfulEvent STARTED

kafka.controller.ControllerEventManagerTest > testSuccessfulEvent PASSED

kafka.controller.ControllerFailoverTest > testHandleIllegalStateException 
STARTED

kafka.controller.ControllerFailoverTest > testHandleIllegalStateException PASSED

kafka.network.SocketServerTest > testGracefulClose STARTED

kafka.network.SocketServerTest > testGracefulClose PASSED

kafka.network.SocketServerTest > 
testSendActionResponseWithThrottledChannelWhereThrottlingAlreadyDone STARTED

kafka.network.SocketServerTest > 
testSendActionResponseWithThrottledChannelWhereThrottlingAlreadyDone PASSED

kafka.network.SocketServerTest > controlThrowable STARTED

kafka.network.SocketServerTest > controlThrowable PASSED

kafka.network.SocketServerTest > testRequestMetricsAfterStop STARTED

kafka.network.SocketServerTest > testRequestMetricsAfterStop PASSED

kafka.network.SocketServerTest > testConnectionIdReuse STARTED

kafka.network.SocketServerTest > testConnectionIdReuse PASSED

kafka.network.SocketServerTest > testClientDisconnectionUpdatesRequestMetrics 
STARTED

kafka.network.SocketServerTest > testClientDisconnectionUpdatesRequestMetrics 
PASSED

kafka.network.SocketServerTest > testProcessorMetricsTags STARTED

kafka.network.SocketServerTest > testProcessorMetricsTags PASSED

kafka.network.SocketServerTest > testMaxConnectionsPerIp STARTED

kafka.network.SocketServerTest > testMaxConnectionsPerIp PASSED

kafka.network.SocketServerTest > testConnectionId STARTED

kafka.network.SocketServerTest > testConnectionId PASSED

kafka.network.SocketServerTest > 
testBrokerSendAfterChannelClosedUpdatesRequestMetrics STARTED

kafka.network.SocketServerTest > 
testBrokerSendAfterChannelClosedUpdatesRequestMetrics PASSED

kafka.network.SocketServerTest > testNoOpAction STARTED

kafka.network.SocketServerTest > testNoOpAction PASSED

kafka.network.SocketServerTest > simpleRequest STARTED

kafka.network.SocketServerTest > simpleRequest PASSED

kafka.network.SocketServerTest > closingChannelException STARTED

kafka.network.SocketServerTest > closingChannelException PASSED

kafka.network.SocketServerTest > 
testSendActionResponseWithThrottledChannelWhereThrottlingInProgress STARTED

kafka.network.SocketServerTest > 
testSendActionResponseWithThrottledChannelWhereThrottlingInProgress PASSED

kafka.network.SocketServerTest > testIdleConnection STARTED

kafka.network.SocketServerTest > testIdleConnection PASSED

kafka.network.SocketServerTest > 
testClientDisconnectionWithStagedReceivesFullyProcessed STARTED

kafka.network.SocketServerTest > 
testClientDisconnectionWithStagedReceivesFullyProcessed PASSED

kafka.network.SocketServerTest > testZeroMaxConnectionsPerIp STARTED

kafka.network.SocketServerTest > testZeroMaxConnectionsPerIp PASSED

kafka.network.SocketServerTest > testMetricCollectionAfterShutdown STARTED

kafka.network.SocketServerTest > testMetricCollectionAfterShutdown PASSED

kafka.network.SocketServerTest > testSessionPrincipal STARTED

kafka.network.SocketServerTest > testSessionPrincipal PASSED

kafka.network.SocketServerTest > configureNewConnectionException STARTED

kafka.network.SocketServerTest > configureNewConnectionException PASSED

kafka.network.SocketServerTest > testMaxConnectionsPerIpOverrides STARTED

kafka.network.SocketServerTest > test

Re: [VOTE] KIP-446: Add changelog topic configuration to KTable suppress

2019-04-22 Thread Maarten Duijn

Hi Everyone,

This KIP passes with three binding +1 votes from Matthias, Bill, and Guozhang 
and two non-binding +1 from votes from John and Bruno.
I would like to thank everyone for the feedback and votes, with special thanks 
to John for guiding me through my first KIP!

A very early stage PR is available at https://github.com/apache/kafka/pull/6593.

Cheers,
Maarten

On Mon, 22 Apr 2019 07:55 AM John Roesler 
wrote:

> Hi Maarten,
>
> Congratulations, your KIP has 3 binding votes, no vetoes, and has been open
> for over 72 hours, so you can close the vote and submit a PR for review!
>
> The way to close the vote is you just reply to this thread and tally up the
> votes, and say that the KIP vote has passed (see the other vote threads for
> examples). Then, you can update:
> * your KIP wiki to change the status to "Adopted"
> * the main KIP page to move your KIP to the "Adopted" section (It should be
> in the "under discussion" section
> * the Kafka Streams page, to move your KIP to the "Adopted" section (
> https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Streams)
>
> Looking forward to the PR!
>
> -John
>
> On Thu, Apr 18, 2019 at 7:58 PM Matthias J. Sax 
> wrote:
>
>>Thanks a lot for the KIP!
>>
>>
>> +1 (binding)
>>
>>
>> -Matthias
>>
>> On 4/18/19 12:31 PM, Guozhang Wang wrote:
>> > +1 (binding).
>> >
>> > Thanks.
>> >
>> > On Thu, Apr 18, 2019 at 10:48 AM John Roesler  wrote:
>> >
>> >> Thanks, Maarten!
>> >>
>> >> +1 (non-binding)
>> >>
>> >> -John
>> >>
>> >> On Wed, Apr 17, 2019 at 1:45 PM Bill Bejeck  wrote:
>> >>
>> >>> Thanks for the KIP.
>> >>>
>> >>> +1(binding)
>> >>>
>> >>> -Bill
>> >>>
>> >>> On Wed, Apr 17, 2019 at 12:58 PM Bruno Cadonna 
>> >> wrote:
>> >>>
>>  Hi Maarten Duijn,
>> 
>>  Thank you for driving this.
>> 
>>  +1 (non-binding)
>> 
>>  Best,
>>  Bruno
>> 
>>  On Wed, Apr 17, 2019 at 8:21 AM Maarten Duijn 
>>  wrote:
>> 
>> > Hello all,
>> >
>> > There has been informal agreement so I would like to call for a vote
>> >> on
>> > KIP-446: Add changelog topic configuration to KTable suppress. This
>> >>> will
>> > allow users to configure internal topics created by the suppress
>> >>> operator
>> > via the streams DSL.
>> >
>> > KIP:
>> >
>> 
>> >>>
>> >>
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-446%3A+Add+changelog+topic+configuration+to+KTable+suppress
>> > JIRA: https://issues.apache.org/jira/browse/KAFKA-8147<
>> > https://issues.apache.org/jira/browse/KAFKA-8029>
>> > PR: will follow shortly
>> >
>> > Cheers,
>> > Maarten
>> >
>> 
>> >>>
>> >>
>> >
>> >
>>
>>

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

2019-04-22 Thread Apache Jenkins Server

See 


Changes:

[rhauch] MINOR: Add support for Standalone Connect configs in Rest Server

[rhauch] MINOR: Correct RestServerTest formatting

--
[...truncated 465.56 KB...]

kafka.admin.PreferredReplicaElectionCommandTest > 
testBasicPreferredReplicaElection STARTED

kafka.admin.PreferredReplicaElectionCommandTest > 
testBasicPreferredReplicaElection PASSED

kafka.admin.PreferredReplicaElectionCommandTest > testPreferredReplicaJsonData 
STARTED

kafka.admin.PreferredReplicaElectionCommandTest > testPreferredReplicaJsonData 
PASSED

kafka.admin.DelegationTokenCommandTest > testDelegationTokenRequests STARTED

kafka.admin.DelegationTokenCommandTest > testDelegationTokenRequests PASSED

kafka.admin.BrokerApiVersionsCommandTest > checkBrokerApiVersionCommandOutput 
STARTED

kafka.admin.BrokerApiVersionsCommandTest > checkBrokerApiVersionCommandOutput 
PASSED

kafka.admin.DeleteTopicTest > testDeleteTopicWithCleaner STARTED

kafka.admin.DeleteTopicTest > testDeleteTopicWithCleaner PASSED

kafka.admin.DeleteTopicTest > testResumeDeleteTopicOnControllerFailover STARTED

kafka.admin.DeleteTopicTest > testResumeDeleteTopicOnControllerFailover PASSED

kafka.admin.DeleteTopicTest > testResumeDeleteTopicWithRecoveredFollower STARTED

kafka.admin.DeleteTopicTest > testResumeDeleteTopicWithRecoveredFollower PASSED

kafka.admin.DeleteTopicTest > testDeleteTopicAlreadyMarkedAsDeleted STARTED

kafka.admin.DeleteTopicTest > testDeleteTopicAlreadyMarkedAsDeleted PASSED

kafka.admin.DeleteTopicTest > testIncreasePartitionCountDuringDeleteTopic 
STARTED

kafka.admin.DeleteTopicTest > testIncreasePartitionCountDuringDeleteTopic PASSED

kafka.admin.DeleteTopicTest > testPartitionReassignmentDuringDeleteTopic STARTED

kafka.admin.DeleteTopicTest > testPartitionReassignmentDuringDeleteTopic PASSED

kafka.admin.DeleteTopicTest > testDeleteNonExistingTopic STARTED

kafka.admin.DeleteTopicTest > testDeleteNonExistingTopic PASSED

kafka.admin.DeleteTopicTest > testRecreateTopicAfterDeletion STARTED

kafka.admin.DeleteTopicTest > testRecreateTopicAfterDeletion PASSED

kafka.admin.DeleteTopicTest > testDisableDeleteTopic STARTED

kafka.admin.DeleteTopicTest > testDisableDeleteTopic PASSED

kafka.admin.DeleteTopicTest > testAddPartitionDuringDeleteTopic STARTED

kafka.admin.DeleteTopicTest > testAddPartitionDuringDeleteTopic PASSED

kafka.admin.DeleteTopicTest > testDeleteTopicWithAllAliveReplicas STARTED

kafka.admin.DeleteTopicTest > testDeleteTopicWithAllAliveReplicas PASSED

kafka.admin.DeleteTopicTest > testDeleteTopicDuringAddPartition STARTED

kafka.admin.DeleteTopicTest > testDeleteTopicDuringAddPartition PASSED

kafka.admin.DeleteTopicTest > testDeletingPartiallyDeletedTopic STARTED

kafka.admin.DeleteTopicTest > testDeletingPartiallyDeletedTopic PASSED

kafka.admin.AdminTest > testGetBrokerMetadatas STARTED

kafka.admin.AdminTest > testGetBrokerMetadatas PASSED

kafka.admin.AdminTest > testBootstrapClientIdConfig STARTED

kafka.admin.AdminTest > testBootstrapClientIdConfig PASSED

kafka.admin.AdminTest > testManualReplicaAssignment STARTED

kafka.admin.AdminTest > testManualReplicaAssignment PASSED

kafka.admin.AdminTest > testConcurrentTopicCreation STARTED

kafka.admin.AdminTest > testConcurrentTopicCreation PASSED

kafka.admin.AdminTest > testTopicCreationWithCollision STARTED

kafka.admin.AdminTest > testTopicCreationWithCollision PASSED

kafka.admin.AdminTest > testTopicCreationInZK STARTED

kafka.admin.AdminTest > testTopicCreationInZK PASSED

kafka.admin.AclCommandTest > testAclCliWithAuthorizer STARTED

kafka.admin.AclCommandTest > testAclCliWithAuthorizer PASSED

kafka.admin.AclCommandTest > testInvalidAuthorizerProperty STARTED

kafka.admin.AclCommandTest > testInvalidAuthorizerProperty PASSED

kafka.admin.AclCommandTest > testAclsOnPrefixedResourcesWithAdminAPI STARTED

kafka.admin.AclCommandTest > testAclsOnPrefixedResourcesWithAdminAPI PASSED

kafka.admin.AclCommandTest > testPatternTypes STARTED

kafka.admin.AclCommandTest > testPatternTypes PASSED

kafka.admin.AclCommandTest > testProducerConsumerCliWithAdminAPI STARTED

kafka.admin.AclCommandTest > testProducerConsumerCliWithAdminAPI PASSED

kafka.admin.AclCommandTest > testAclsOnPrefixedResourcesWithAuthorizer STARTED

kafka.admin.AclCommandTest > testAclsOnPrefixedResourcesWithAuthorizer PASSED

kafka.admin.AclCommandTest > testProducerConsumerCliWithAuthorizer STARTED

kafka.admin.AclCommandTest > testProducerConsumerCliWithAuthorizer PASSED

kafka.admin.AclCommandTest > testAclCliWithAdminAPI STARTED

kafka.admin.AclCommandTest > testAclCliWithAdminAPI PASSED

kafka.admin.ConfigCommandTest > testScramCredentials STARTED

kafka.admin.ConfigCommandTest > testScramCredentials PASSED

kafka.admin.ConfigCommandTest > shouldParseArgumentsForTopicsEntityType STARTED

kafka.admin.ConfigCommandTest > shouldParseArgumentsForTopicsEntityType PASSED

Build failed in Jenkins: kafka-2.0-jdk8 #254

2019-04-22 Thread Apache Jenkins Server

See 


Changes:

[rhauch] MINOR: Add support for Standalone Connect configs in Rest Server

[rhauch] MINOR: Correct RestServerTest formatting

--
[...truncated 435.98 KB...]
kafka.controller.ReplicaStateMachineTest > 
testInvalidOfflineReplicaToNonexistentReplicaTransition PASSED

kafka.controller.ReplicaStateMachineTest > 
testInvalidOnlineReplicaToReplicaDeletionIneligibleTransition STARTED

kafka.controller.ReplicaStateMachineTest > 
testInvalidOnlineReplicaToReplicaDeletionIneligibleTransition PASSED

kafka.controller.ReplicaStateMachineTest > 
testInvalidReplicaDeletionSuccessfulToReplicaDeletionStartedTransition STARTED

kafka.controller.ReplicaStateMachineTest > 
testInvalidReplicaDeletionSuccessfulToReplicaDeletionStartedTransition PASSED

kafka.controller.ReplicaStateMachineTest > 
testInvalidNewReplicaToReplicaDeletionSuccessfulTransition STARTED

kafka.controller.ReplicaStateMachineTest > 
testInvalidNewReplicaToReplicaDeletionSuccessfulTransition PASSED

kafka.controller.ReplicaStateMachineTest > 
testInvalidReplicaDeletionIneligibleToReplicaDeletionStartedTransition STARTED

kafka.controller.ReplicaStateMachineTest > 
testInvalidReplicaDeletionIneligibleToReplicaDeletionStartedTransition PASSED

kafka.controller.ReplicaStateMachineTest > 
testInvalidReplicaDeletionStartedToOfflineReplicaTransition STARTED

kafka.controller.ReplicaStateMachineTest > 
testInvalidReplicaDeletionStartedToOfflineReplicaTransition PASSED

kafka.controller.ReplicaStateMachineTest > 
testInvalidNewReplicaToReplicaDeletionStartedTransition STARTED

kafka.controller.ReplicaStateMachineTest > 
testInvalidNewReplicaToReplicaDeletionStartedTransition PASSED

kafka.controller.ReplicaStateMachineTest > 
testOnlineReplicaToOnlineReplicaTransition STARTED

kafka.controller.ReplicaStateMachineTest > 
testOnlineReplicaToOnlineReplicaTransition PASSED

kafka.controller.ReplicaStateMachineTest > 
testInvalidNewReplicaToReplicaDeletionIneligibleTransition STARTED

kafka.controller.ReplicaStateMachineTest > 
testInvalidNewReplicaToReplicaDeletionIneligibleTransition PASSED

kafka.controller.ReplicaStateMachineTest > 
testInvalidNonexistentReplicaToOfflineReplicaTransition STARTED

kafka.controller.ReplicaStateMachineTest > 
testInvalidNonexistentReplicaToOfflineReplicaTransition PASSED

kafka.controller.ReplicaStateMachineTest > 
testReplicaDeletionStartedToReplicaDeletionSuccessfulTransition STARTED

kafka.controller.ReplicaStateMachineTest > 
testReplicaDeletionStartedToReplicaDeletionSuccessfulTransition PASSED

kafka.controller.ReplicaStateMachineTest > 
testInvalidNonexistentReplicaToOnlineReplicaTransition STARTED

kafka.controller.ReplicaStateMachineTest > 
testInvalidNonexistentReplicaToOnlineReplicaTransition PASSED

kafka.controller.ReplicaStateMachineTest > 
testInvalidOnlineReplicaToNewReplicaTransition STARTED

kafka.controller.ReplicaStateMachineTest > 
testInvalidOnlineReplicaToNewReplicaTransition PASSED

kafka.controller.ReplicaStateMachineTest > 
testReplicaDeletionStartedToReplicaDeletionIneligibleTransition STARTED

kafka.controller.ReplicaStateMachineTest > 
testReplicaDeletionStartedToReplicaDeletionIneligibleTransition PASSED

kafka.controller.ReplicaStateMachineTest > 
testInvalidReplicaDeletionSuccessfulToOfflineReplicaTransition STARTED

kafka.controller.ReplicaStateMachineTest > 
testInvalidReplicaDeletionSuccessfulToOfflineReplicaTransition PASSED

kafka.controller.ReplicaStateMachineTest > 
testInvalidReplicaDeletionIneligibleToNewReplicaTransition STARTED

kafka.controller.ReplicaStateMachineTest > 
testInvalidReplicaDeletionIneligibleToNewReplicaTransition PASSED

kafka.controller.ReplicaStateMachineTest > 
testReplicaDeletionIneligibleToOnlineReplicaTransition STARTED

kafka.controller.ReplicaStateMachineTest > 
testReplicaDeletionIneligibleToOnlineReplicaTransition PASSED

kafka.controller.ReplicaStateMachineTest > 
testInvalidReplicaDeletionStartedToNewReplicaTransition STARTED

kafka.controller.ReplicaStateMachineTest > 
testInvalidReplicaDeletionStartedToNewReplicaTransition PASSED

kafka.controller.ReplicaStateMachineTest > 
testInvalidNonexistentReplicaToReplicaDeletionSuccessfulTransition STARTED

kafka.controller.ReplicaStateMachineTest > 
testInvalidNonexistentReplicaToReplicaDeletionSuccessfulTransition PASSED

kafka.controller.ReplicaStateMachineTest > 
testNewReplicaToOnlineReplicaTransition STARTED

kafka.controller.ReplicaStateMachineTest > 
testNewReplicaToOnlineReplicaTransition PASSED

kafka.controller.ControllerFailoverTest > testHandleIllegalStateException 
STARTED

kafka.controller.ControllerFailoverTest > testHandleIllegalStateException PASSED

kafka.controller.ControllerEventManagerTest > testEventThatThrowsException 
STARTED

kafka.controller.ControllerEventManagerTest > testEventThatThrowsException 
PASSED

kafka.controller.ControllerEventManagerTest > testSuc

[jira] [Created] (KAFKA-8273) Admin client doesn't reestablish connection on Broker restart

[jira] [Created] (KAFKA-8274) Old Committed messages got replayed after Kafka cluster Restart

Re: [VOTE] KIP-446: Add changelog topic configuration to KTable suppress

[jira] [Created] (KAFKA-8275) NetworkClient leastLoadedNode selection should consider throttled nodes

Re: [DISCUSS] KIP-440: Extend Connect Converter to support headers

[jira] [Created] (KAFKA-8276) Schema Registry Security settings as Props

Re: [DISCUSS] KIP-440: Extend Connect Converter to support headers

Re: [VOTE] KIP-421: Automatically resolve external configurations.

Re: [DISCUSS] KIP-440: Extend Connect Converter to support headers

Re: [DISCUSS] KIP-440: Extend Connect Converter to support headers

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

Re: [DISCUSS] KIP-440: Extend Connect Converter to support headers

[jira] [Created] (KAFKA-8277) Fix NPE in ConnectHeaders

[jira] [Resolved] (KAFKA-8277) Fix NPE in ConnectHeaders

Re: [ANNOUNCE] New Kafka PMC member: Sriharsh Chintalapan

[jira] [Resolved] (KAFKA-8204) Streams may flush state stores in the incorrect order

Re: [DISCUSS] KIP-458: Connector Client Config Override Policy

Re: [VOTE] KIP-421: Automatically resolve external configurations.

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

Build failed in Jenkins: kafka-2.0-jdk8 #253

Build failed in Jenkins: kafka-1.1-jdk7 #261

Re: [VOTE] KIP-421: Automatically resolve external configurations.

Build failed in Jenkins: kafka-2.2-jdk8 #88

Re: [ANNOUNCE] New Kafka PMC member: Matthias J. Sax

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

Re: [ANNOUNCE] New Kafka PMC member: Sriharsh Chintalapan

Re: [VOTE] KIP-421: Automatically resolve external configurations.

Build failed in Jenkins: kafka-2.2-jdk8 #89

Re: [VOTE] KIP-446: Add changelog topic configuration to KTable suppress

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

Build failed in Jenkins: kafka-2.0-jdk8 #254

31 matches

Site Navigation

Mail list logo

Footer information