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

[Apache Jenkins Server]

See 


Changes:

[ismael] KAFKA-5856; Add AdminClient.createPartitions() (KIP-195)

--
[...truncated 352.30 KB...]

kafka.coordinator.transaction.TransactionCoordinatorTest > 
shouldRespondWithNotCoordinatorOnInitPidWhenNotCoordinator STARTED

kafka.coordinator.transaction.TransactionCoordinatorTest > 
shouldRespondWithNotCoordinatorOnInitPidWhenNotCoordinator PASSED

kafka.coordinator.transaction.TransactionCoordinatorTest > 
shouldRespondWithConcurrentTransactionOnAddPartitionsWhenStateIsPrepareAbort 
STARTED

kafka.coordinator.transaction.TransactionCoordinatorTest > 
shouldRespondWithConcurrentTransactionOnAddPartitionsWhenStateIsPrepareAbort 
PASSED

kafka.coordinator.transaction.TransactionCoordinatorTest > 
shouldInitPidWithEpochZeroForNewTransactionalId STARTED

kafka.coordinator.transaction.TransactionCoordinatorTest > 
shouldInitPidWithEpochZeroForNewTransactionalId PASSED

kafka.coordinator.transaction.ProducerIdManagerTest > testExceedProducerIdLimit 
STARTED

kafka.coordinator.transaction.ProducerIdManagerTest > testExceedProducerIdLimit 
PASSED

kafka.coordinator.transaction.ProducerIdManagerTest > testGetProducerId STARTED

kafka.coordinator.transaction.ProducerIdManagerTest > testGetProducerId PASSED

kafka.coordinator.transaction.TransactionMarkerChannelManagerTest > 
shouldSaveForLaterWhenLeaderUnknownButNotAvailable STARTED

kafka.coordinator.transaction.TransactionMarkerChannelManagerTest > 
shouldSaveForLaterWhenLeaderUnknownButNotAvailable PASSED

kafka.coordinator.transaction.TransactionMarkerChannelManagerTest > 
shouldGenerateEmptyMapWhenNoRequestsOutstanding STARTED

kafka.coordinator.transaction.TransactionMarkerChannelManagerTest > 
shouldGenerateEmptyMapWhenNoRequestsOutstanding PASSED

kafka.coordinator.transaction.TransactionMarkerChannelManagerTest > 
shouldCreateMetricsOnStarting STARTED

kafka.coordinator.transaction.TransactionMarkerChannelManagerTest > 
shouldCreateMetricsOnStarting PASSED

kafka.coordinator.transaction.TransactionMarkerChannelManagerTest > 
shouldAbortAppendToLogOnEndTxnWhenNotCoordinatorError STARTED

kafka.coordinator.transaction.TransactionMarkerChannelManagerTest > 
shouldAbortAppendToLogOnEndTxnWhenNotCoordinatorError PASSED

kafka.coordinator.transaction.TransactionMarkerChannelManagerTest > 
shouldRetryAppendToLogOnEndTxnWhenCoordinatorNotAvailableError STARTED

kafka.coordinator.transaction.TransactionMarkerChannelManagerTest > 
shouldRetryAppendToLogOnEndTxnWhenCoordinatorNotAvailableError PASSED

kafka.coordinator.transaction.TransactionMarkerChannelManagerTest > 
shouldCompleteAppendToLogOnEndTxnWhenSendMarkersSucceed STARTED

kafka.coordinator.transaction.TransactionMarkerChannelManagerTest > 
shouldCompleteAppendToLogOnEndTxnWhenSendMarkersSucceed PASSED

kafka.coordinator.transaction.TransactionMarkerChannelManagerTest > 
shouldGenerateRequestPerPartitionPerBroker STARTED

kafka.coordinator.transaction.TransactionMarkerChannelManagerTest > 
shouldGenerateRequestPerPartitionPerBroker PASSED

kafka.coordinator.transaction.TransactionMarkerChannelManagerTest > 
shouldRemoveMarkersForTxnPartitionWhenPartitionEmigrated STARTED

kafka.coordinator.transaction.TransactionMarkerChannelManagerTest > 
shouldRemoveMarkersForTxnPartitionWhenPartitionEmigrated PASSED

kafka.coordinator.transaction.TransactionMarkerChannelManagerTest > 
shouldSkipSendMarkersWhenLeaderNotFound STARTED

kafka.coordinator.transaction.TransactionMarkerChannelManagerTest > 
shouldSkipSendMarkersWhenLeaderNotFound PASSED

kafka.coordinator.transaction.TransactionLogTest > shouldReadWriteMessages 
STARTED

kafka.coordinator.transaction.TransactionLogTest > shouldReadWriteMessages 
PASSED

kafka.coordinator.transaction.TransactionLogTest > 
shouldThrowExceptionWriteInvalidTxn STARTED

kafka.coordinator.transaction.TransactionLogTest > 
shouldThrowExceptionWriteInvalidTxn PASSED

kafka.coordinator.transaction.TransactionStateManagerTest > 
testAppendTransactionToLogWhileProducerFenced STARTED

kafka.coordinator.transaction.TransactionStateManagerTest > 
testAppendTransactionToLogWhileProducerFenced PASSED

kafka.coordinator.transaction.TransactionStateManagerTest > 
testCompleteTransitionWhenAppendSucceeded STARTED

kafka.coordinator.transaction.TransactionStateManagerTest > 
testCompleteTransitionWhenAppendSucceeded PASSED

kafka.coordinator.transaction.TransactionStateManagerTest > 
testAppendFailToCoordinatorNotAvailableError STARTED

kafka.coordinator.transaction.TransactionStateManagerTest > 
testAppendFailToCoordinatorNotAvailableError PASSED

kafka.coordinator.transaction.TransactionStateManagerTest > 
testAppendFailToUnknownError STARTED

kafka.coordinator.transaction.TransactionStateManagerTest > 
testAppendFailToUnknownError PASSED

kafka.coordinator.transaction.TransactionStateManagerTest > 

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

[Apache Jenkins Server]

See 


Changes:

[ismael] MINOR: Upgrade to Gradle 4.2

[rajinisivaram] KAFKA-5854; Handle SASL authentication failures as non-retriable

--
[...truncated 3.69 MB...]
org.apache.kafka.streams.StreamsConfigTest > 
shouldOverrideStreamsDefaultProducerConfigs PASSED

org.apache.kafka.streams.StreamsConfigTest > 
shouldSupportPrefixedPropertiesThatAreNotPartOfProducerConfig STARTED

org.apache.kafka.streams.StreamsConfigTest > 
shouldSupportPrefixedPropertiesThatAreNotPartOfProducerConfig PASSED

org.apache.kafka.streams.StreamsConfigTest > 
shouldBeBackwardsCompatibleWithDeprecatedConfigs STARTED

org.apache.kafka.streams.StreamsConfigTest > 
shouldBeBackwardsCompatibleWithDeprecatedConfigs PASSED

org.apache.kafka.streams.StreamsConfigTest > 
shouldBeSupportNonPrefixedConsumerConfigs STARTED

org.apache.kafka.streams.StreamsConfigTest > 
shouldBeSupportNonPrefixedConsumerConfigs PASSED

org.apache.kafka.streams.StreamsConfigTest > 
shouldOverrideStreamsDefaultConsumerConifgsOnRestoreConsumer STARTED

org.apache.kafka.streams.StreamsConfigTest > 
shouldOverrideStreamsDefaultConsumerConifgsOnRestoreConsumer PASSED

org.apache.kafka.streams.StreamsConfigTest > shouldAcceptExactlyOnce STARTED

org.apache.kafka.streams.StreamsConfigTest > shouldAcceptExactlyOnce PASSED

org.apache.kafka.streams.StreamsConfigTest > 
shouldSetInternalLeaveGroupOnCloseConfigToFalseInConsumer STARTED

org.apache.kafka.streams.StreamsConfigTest > 
shouldSetInternalLeaveGroupOnCloseConfigToFalseInConsumer PASSED

org.apache.kafka.streams.StreamsConfigTest > 
shouldSupportPrefixedPropertiesThatAreNotPartOfConsumerConfig STARTED

org.apache.kafka.streams.StreamsConfigTest > 
shouldSupportPrefixedPropertiesThatAreNotPartOfConsumerConfig PASSED

org.apache.kafka.streams.StreamsConfigTest > 
shouldResetToDefaultIfRestoreConsumerAutoCommitIsOverridden STARTED

org.apache.kafka.streams.StreamsConfigTest > 
shouldResetToDefaultIfRestoreConsumerAutoCommitIsOverridden PASSED

org.apache.kafka.streams.StreamsConfigTest > 
shouldSpecifyCorrectValueSerdeClassOnError STARTED

org.apache.kafka.streams.StreamsConfigTest > 
shouldSpecifyCorrectValueSerdeClassOnError PASSED

org.apache.kafka.streams.StreamsConfigTest > 
shouldSpecifyCorrectValueSerdeClassOnErrorUsingDeprecatedConfigs STARTED

org.apache.kafka.streams.StreamsConfigTest > 
shouldSpecifyCorrectValueSerdeClassOnErrorUsingDeprecatedConfigs PASSED

org.apache.kafka.streams.StreamsConfigTest > 
shouldResetToDefaultIfConsumerIsolationLevelIsOverriddenIfEosEnabled STARTED

org.apache.kafka.streams.StreamsConfigTest > 
shouldResetToDefaultIfConsumerIsolationLevelIsOverriddenIfEosEnabled PASSED

org.apache.kafka.streams.StreamsConfigTest > 
shouldNotOverrideUserConfigCommitIntervalMsIfExactlyOnceEnabled STARTED

org.apache.kafka.streams.StreamsConfigTest > 
shouldNotOverrideUserConfigCommitIntervalMsIfExactlyOnceEnabled PASSED

org.apache.kafka.streams.StreamsConfigTest > 
shouldSupportMultipleBootstrapServers STARTED

org.apache.kafka.streams.StreamsConfigTest > 
shouldSupportMultipleBootstrapServers PASSED

org.apache.kafka.streams.StreamsConfigTest > 
shouldThrowStreamsExceptionIfKeySerdeConfigFails STARTED

org.apache.kafka.streams.StreamsConfigTest > 
shouldThrowStreamsExceptionIfKeySerdeConfigFails PASSED

org.apache.kafka.streams.StreamsConfigTest > 
shouldSupportNonPrefixedProducerConfigs STARTED

org.apache.kafka.streams.StreamsConfigTest > 
shouldSupportNonPrefixedProducerConfigs PASSED

org.apache.kafka.streams.StreamsConfigTest > testGetRestoreConsumerConfigs 
STARTED

org.apache.kafka.streams.StreamsConfigTest > testGetRestoreConsumerConfigs 
PASSED

org.apache.kafka.streams.StreamsConfigTest > 
shouldThrowExceptionIfBootstrapServersIsNotSet STARTED

org.apache.kafka.streams.StreamsConfigTest > 
shouldThrowExceptionIfBootstrapServersIsNotSet PASSED

org.apache.kafka.streams.StreamsConfigTest > 
shouldSpecifyCorrectKeySerdeClassOnErrorUsingDeprecatedConfigs STARTED

org.apache.kafka.streams.StreamsConfigTest > 
shouldSpecifyCorrectKeySerdeClassOnErrorUsingDeprecatedConfigs PASSED

org.apache.kafka.streams.StreamsConfigTest > 
shouldBeSupportNonPrefixedRestoreConsumerConfigs STARTED

org.apache.kafka.streams.StreamsConfigTest > 
shouldBeSupportNonPrefixedRestoreConsumerConfigs PASSED

org.apache.kafka.streams.StreamsConfigTest > 
shouldSupportPrefixedRestoreConsumerConfigs STARTED

org.apache.kafka.streams.StreamsConfigTest > 
shouldSupportPrefixedRestoreConsumerConfigs PASSED

org.apache.kafka.streams.StreamsConfigTest > 
shouldThrowExceptionIfApplicationIdIsNotSet STARTED

org.apache.kafka.streams.StreamsConfigTest > 
shouldThrowExceptionIfApplicationIdIsNotSet PASSED

org.apache.kafka.streams.StreamsConfigTest > 
shouldResetToDefaultIfProducerMaxInFlightRequestPerConnectionsIsOverriddenIfEosEnabled
 STARTED

org.apache.kafka.streams.StreamsConfigTest > 

[GitHub] kafka pull request #3930: KAFKA-5856; AdminClient.createPartitions() follow-...

[ijuma]

GitHub user ijuma opened a pull request:

https://github.com/apache/kafka/pull/3930

KAFKA-5856; AdminClient.createPartitions() follow-up (KIP-195)

- Remove DelayedCreatePartitions to reduce code duplication
- Avoid unnecessary ZK calls (call it once per request instead
of once per topic, if possible)
- Simplify code
- A few minor clean-ups

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/ijuma/kafka 
kafka-5856-admin-client-creation-partitions

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/3930.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #3930






---

Build failed in Jenkins: kafka-trunk-jdk9 #39

[Apache Jenkins Server]

See 


Changes:

[ismael] KAFKA-5856; Add AdminClient.createPartitions() (KIP-195)

--
[...truncated 1.02 MB...]
org.apache.kafka.clients.producer.internals.SenderTest > 
testClusterAuthorizationExceptionInInitProducerIdRequest STARTED

org.apache.kafka.clients.producer.internals.SenderTest > 
testClusterAuthorizationExceptionInInitProducerIdRequest PASSED

org.apache.kafka.clients.producer.internals.SenderTest > 
testUnsupportedVersionInProduceRequest STARTED

org.apache.kafka.clients.producer.internals.SenderTest > 
testUnsupportedVersionInProduceRequest PASSED

org.apache.kafka.clients.producer.internals.SenderTest > 
testCorrectHandlingOfOutOfOrderResponsesWhenSecondSucceeds STARTED

org.apache.kafka.clients.producer.internals.SenderTest > 
testCorrectHandlingOfOutOfOrderResponsesWhenSecondSucceeds PASSED

org.apache.kafka.clients.producer.internals.SenderTest > 
testUnknownProducerErrorShouldBeRetriedForFutureBatchesWhenFirstFails STARTED

org.apache.kafka.clients.producer.internals.SenderTest > 
testUnknownProducerErrorShouldBeRetriedForFutureBatchesWhenFirstFails PASSED

org.apache.kafka.clients.producer.internals.SenderTest > 
testUnsupportedForMessageFormatInProduceRequest STARTED

org.apache.kafka.clients.producer.internals.SenderTest > 
testUnsupportedForMessageFormatInProduceRequest PASSED

org.apache.kafka.clients.producer.internals.SenderTest > testSimple STARTED

org.apache.kafka.clients.producer.internals.SenderTest > testSimple PASSED

org.apache.kafka.clients.producer.internals.SenderTest > 
testSequenceNumberIncrement STARTED

org.apache.kafka.clients.producer.internals.SenderTest > 
testSequenceNumberIncrement PASSED

org.apache.kafka.clients.producer.internals.SenderTest > 
testIdempotenceWithMultipleInflightsRetriedInOrder STARTED

org.apache.kafka.clients.producer.internals.SenderTest > 
testIdempotenceWithMultipleInflightsRetriedInOrder PASSED

org.apache.kafka.clients.producer.internals.ProducerInterceptorsTest > 
testOnAcknowledgementWithErrorChain STARTED

org.apache.kafka.clients.producer.internals.ProducerInterceptorsTest > 
testOnAcknowledgementWithErrorChain PASSED

org.apache.kafka.clients.producer.internals.ProducerInterceptorsTest > 
testOnAcknowledgementChain STARTED

org.apache.kafka.clients.producer.internals.ProducerInterceptorsTest > 
testOnAcknowledgementChain PASSED

org.apache.kafka.clients.producer.internals.ProducerInterceptorsTest > 
testOnSendChain STARTED

org.apache.kafka.clients.producer.internals.ProducerInterceptorsTest > 
testOnSendChain PASSED

org.apache.kafka.clients.producer.internals.RecordAccumulatorTest > 
testSplitBatchOffAccumulator STARTED

org.apache.kafka.clients.producer.internals.RecordAccumulatorTest > 
testSplitBatchOffAccumulator PASSED

org.apache.kafka.clients.producer.internals.RecordAccumulatorTest > 
testRetryBackoff STARTED

org.apache.kafka.clients.producer.internals.RecordAccumulatorTest > 
testRetryBackoff PASSED

org.apache.kafka.clients.producer.internals.RecordAccumulatorTest > 
testNextReadyCheckDelay STARTED

org.apache.kafka.clients.producer.internals.RecordAccumulatorTest > 
testNextReadyCheckDelay PASSED

org.apache.kafka.clients.producer.internals.RecordAccumulatorTest > 
testStressfulSituation STARTED

org.apache.kafka.clients.producer.internals.RecordAccumulatorTest > 
testStressfulSituation PASSED

org.apache.kafka.clients.producer.internals.RecordAccumulatorTest > 
testAppendLargeNonCompressed STARTED

org.apache.kafka.clients.producer.internals.RecordAccumulatorTest > 
testAppendLargeNonCompressed PASSED

org.apache.kafka.clients.producer.internals.RecordAccumulatorTest > 
testAwaitFlushComplete STARTED

org.apache.kafka.clients.producer.internals.RecordAccumulatorTest > 
testAwaitFlushComplete PASSED

org.apache.kafka.clients.producer.internals.RecordAccumulatorTest > testFlush 
STARTED

org.apache.kafka.clients.producer.internals.RecordAccumulatorTest > testFlush 
PASSED

org.apache.kafka.clients.producer.internals.RecordAccumulatorTest > testFull 
STARTED

org.apache.kafka.clients.producer.internals.RecordAccumulatorTest > testFull 
PASSED

org.apache.kafka.clients.producer.internals.RecordAccumulatorTest > 
testSplitFrequency STARTED

org.apache.kafka.clients.producer.internals.RecordAccumulatorTest > 
testSplitFrequency PASSED

org.apache.kafka.clients.producer.internals.RecordAccumulatorTest > 
testAbortUnsentBatches STARTED

org.apache.kafka.clients.producer.internals.RecordAccumulatorTest > 
testAbortUnsentBatches PASSED

org.apache.kafka.clients.producer.internals.RecordAccumulatorTest > 
testIdempotenceWithOldMagic STARTED

org.apache.kafka.clients.producer.internals.RecordAccumulatorTest > 
testIdempotenceWithOldMagic PASSED

org.apache.kafka.clients.producer.internals.RecordAccumulatorTest > 
testAppendLargeOldMessageFormatNonCompressed STARTED

[GitHub] kafka pull request #3870: KAFKA-5856: Add AdminClient.createPartitions()

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/kafka/pull/3870


---

[GitHub] kafka pull request #3865: KAFKA-5793: Tighten up the semantics of the OutOfO...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/kafka/pull/3865


---

[GitHub] kafka pull request #3929: Minor: tighten up the check of partition states in...

[junrao]

GitHub user junrao opened a pull request:

https://github.com/apache/kafka/pull/3929

Minor: tighten up the check of partition states in AbstractFetcherThread



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/junrao/kafka 
minor-change-abstractfetcherthread

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/3929.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #3929


commit 73c3232c981f7608e9b1ef8f084c6c43b4389dfd
Author: Jun Rao 
Date:   2017-09-21T01:20:26Z

Minor: tighten up the check of partition states in AbstractFetcherThread




---

[GitHub] kafka-site issue #82: Adding minor style changes

[manjuapu]

Github user manjuapu commented on the issue:

https://github.com/apache/kafka-site/pull/82
  
@guozhangwang @dguy can you please delete this PR?


---

[jira] [Created] (KAFKA-5950) AdminClient should retry based on returned error codes

[Ismael Juma (JIRA)]

Ismael Juma created KAFKA-5950:
--

 Summary: AdminClient should retry based on returned error codes
 Key: KAFKA-5950
 URL: https://issues.apache.org/jira/browse/KAFKA-5950
 Project: Kafka
  Issue Type: Bug
Reporter: Ismael Juma
 Fix For: 1.1.0


The AdminClient only retries if the request fails with a retriable error. If a 
response is returned, then a retry is never attempted. This is inconsistent 
with other clients that check the error codes in the response and retry for 
each retriable error code.

We should consider if it makes sense to adopt this behaviour in the AdminClient 
so that users don't have to do it themselves.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: 1.0.0 KIPs Update

[Ismael Juma]

Yes, although it would have to be reviewed and merged by next Wednesday.

Ismael

On Thu, Sep 21, 2017 at 12:17 AM, James Cheng  wrote:

> Thanks Ismael. Yes, you're right, PR 3799 is purely a refactoring.
>
> There are new subtasks of https://issues.apache.org/jira/browse/KAFKA-3480
>  that I haven't yet
> filed, that I want to work on. They will add auto generation of metrics
> documentation for more areas of the codebase. So I was trying to figure out
> what were my chances of getting them into 1.0.0, to help me prioritize when
> I should work on them.
>
> But to your general point, it sounds like if I make my case and the
> community agrees that its worth the cost/benefit, that it might be eligible
> to get into 1.0.0. Sounds perfect. Thanks!
>
> -James
>
> > On Sep 20, 2017, at 3:14 PM, Ismael Juma  wrote:
> >
> > Hi James,
> >
> > Isn't PR 3799 purely a code refactoring (i.e. no change in behaviour)? If
> > so, it would probably land in trunk only after today. If it's new
> > functionality, then it depends on size, risk and importance. If you think
> > it's important and should target 1.0.0, feel free to make your case in
> the
> > JIRA or PR.
> >
> > Thanks,
> > Ismael
> >
> > On Wed, Sep 20, 2017 at 10:59 PM, James Cheng 
> wrote:
> >
> >> Hi. I'm a little unclear on what types of things are subject to the
> >> "Feature Freeze" today (Sept 20th).
> >>
> >> For changes such as https://github.com/apache/kafka/pull/3799 <
> >> https://github.com/apache/kafka/pull/3799> and
> https://issues.apache.org/
> >> jira/browse/KAFKA-3480  jira/browse/KAFKA-3480>
> >> that don't require KIPs, is today the freeze date? If I have PR created
> but
> >> not yet reviewed, does that mean it is eligible to get into 1.0.0?
> >>
> >> And if I have a PR that comes AFTER today, does that mean it is NOT
> >> eligible for 1.0.0?
> >>
> >> Thanks!
> >>
> >> -James
> >>
> >>> On Sep 11, 2017, at 12:14 PM, Guozhang Wang 
> wrote:
> >>>
> >>> Sure! Please feel free to update the wiki.
> >>>
> >>>
> >>> Guozhang
> >>>
> >>> On Mon, Sep 11, 2017 at 9:28 AM, Rajini Sivaram <
> rajinisiva...@gmail.com
> >>>
> >>> wrote:
> >>>
>  Hi Guozhang,
> 
>  Can KIP-188 be added to the list, please? The vote has passed and PR
> >> should
>  be ready soon.
> 
>  Thank you,
> 
>  Rajini
> 
>  On Thu, Sep 7, 2017 at 10:28 PM, Guozhang Wang 
> >> wrote:
> 
> > Actually my bad, there is already a voting thread and you asked
> people
> >> to
> > recast a vote on a small change.
> >
> > On Thu, Sep 7, 2017 at 2:27 PM, Guozhang Wang 
>  wrote:
> >
> >> Hi Tom,
> >>
> >> It seems KIP-183 is still in the discussion phase, and voting has
> not
> > been
> >> started?
> >>
> >>
> >> Guozhang
> >>
> >>
> >> On Thu, Sep 7, 2017 at 1:13 AM, Tom Bentley 
> > wrote:
> >>
> >>> Would it be possible to add KIP-183 to the list too, please?
> >>>
> >>> Thanks,
> >>>
> >>> Tom
> >>>
> >>> On 6 September 2017 at 22:04, Guozhang Wang 
>  wrote:
> >>>
>  Hi Vahid,
> 
>  Yes I have just added it while sending this email :)
> 
> 
>  Guozhang
> 
>  On Wed, Sep 6, 2017 at 1:54 PM, Vahid S Hashemian <
>  vahidhashem...@us.ibm.com
> > wrote:
> 
> > Hi Guozhang,
> >
> > Thanks for the heads-up.
> >
> > Can KIP-163 be added to the list?
> > The proposal for this KIP is accepted, and the PR is ready for
> > review.
> >
> > Thanks.
> > --Vahid
> >
> >
> >
> > From:   Guozhang Wang 
> > To: "dev@kafka.apache.org" 
> > Date:   09/06/2017 01:45 PM
> > Subject:1.0.0 KIPs Update
> >
> >
> >
> > Hello folks,
> >
> > This is a heads up on 1.0.0 progress:
> >
> > https://urldefense.proofpoint.com/v2/url?u=https-3A__cwiki.a
> > pache.org_confluence_pages_viewpage.action-3FpageId-3D717649
> > 13=DwIBaQ=jf_iaSHvJObTbx-siA1ZOg=Q_itwloTQj3_
> > xUKl7Nzswo6KE4Nj-kjJc7uSVcviKUc=bLvgeykOujjty9joOuWXD4wZab
> > o1CV0pULY4eqBxqzk=90UN7ejzCQmdPOyRR_
>  2z304xLUSBCtOYi0KqhAo4EyU=
> >
> >
> > We have one week left towards the KIP deadline, which is Sept.
>  13th.
>  There
> > are still a lot of KIPs that under discussion / voting process.
>  For
> >>> the
> > KIP
> > proposer, please keep in mind that the voting has to be done
>  before
> >>> the
> > 

[jira] [Created] (KAFKA-5949) User Callback Exceptions need to be handled properly

[Matthias J. Sax (JIRA)]

Matthias J. Sax created KAFKA-5949:
--

 Summary: User Callback Exceptions need to be handled properly
 Key: KAFKA-5949
 URL: https://issues.apache.org/jira/browse/KAFKA-5949
 Project: Kafka
  Issue Type: Sub-task
  Components: streams
Reporter: Matthias J. Sax
Assignee: Matthias J. Sax


In Streams, we allow to register multiple user callbacks. We need to handle 
those exceptions gracefully, by catching and wrapping with a StreamsException.

- TimestampExtractor
- DeserailizationHandler
- StateRestoreListener



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Jenkins build is back to normal : kafka-trunk-jdk7 #2792

[Apache Jenkins Server]

See 

[GitHub] kafka pull request #3928: KAFKA-5947: Handle authentication failure in admin...

[rajinisivaram]

GitHub user rajinisivaram opened a pull request:

https://github.com/apache/kafka/pull/3928

KAFKA-5947: Handle authentication failure in admin client, txn producer

1. Raise AuthenticationException for authentication failures in admin client
2. Handle AuthenticationException as a fatal error for transactional 
producer
3. Add comments to authentication exceptions

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/rajinisivaram/kafka KAFKA-5947-auth-failure

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/3928.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #3928


commit 764f38785f83a95f840c398c9ef2f557e67fe07a
Author: Rajini Sivaram 
Date:   2017-09-20T15:27:23Z

KAFKA-5947: Handle authentication exceptions in admin client and txn
producer




---

Re: 1.0.0 KIPs Update

[James Cheng]

Thanks Ismael. Yes, you're right, PR 3799 is purely a refactoring.

There are new subtasks of https://issues.apache.org/jira/browse/KAFKA-3480 
 that I haven't yet filed, 
that I want to work on. They will add auto generation of metrics documentation 
for more areas of the codebase. So I was trying to figure out what were my 
chances of getting them into 1.0.0, to help me prioritize when I should work on 
them.

But to your general point, it sounds like if I make my case and the community 
agrees that its worth the cost/benefit, that it might be eligible to get into 
1.0.0. Sounds perfect. Thanks!

-James

> On Sep 20, 2017, at 3:14 PM, Ismael Juma  wrote:
> 
> Hi James,
> 
> Isn't PR 3799 purely a code refactoring (i.e. no change in behaviour)? If
> so, it would probably land in trunk only after today. If it's new
> functionality, then it depends on size, risk and importance. If you think
> it's important and should target 1.0.0, feel free to make your case in the
> JIRA or PR.
> 
> Thanks,
> Ismael
> 
> On Wed, Sep 20, 2017 at 10:59 PM, James Cheng  wrote:
> 
>> Hi. I'm a little unclear on what types of things are subject to the
>> "Feature Freeze" today (Sept 20th).
>> 
>> For changes such as https://github.com/apache/kafka/pull/3799 <
>> https://github.com/apache/kafka/pull/3799> and https://issues.apache.org/
>> jira/browse/KAFKA-3480 
>> that don't require KIPs, is today the freeze date? If I have PR created but
>> not yet reviewed, does that mean it is eligible to get into 1.0.0?
>> 
>> And if I have a PR that comes AFTER today, does that mean it is NOT
>> eligible for 1.0.0?
>> 
>> Thanks!
>> 
>> -James
>> 
>>> On Sep 11, 2017, at 12:14 PM, Guozhang Wang  wrote:
>>> 
>>> Sure! Please feel free to update the wiki.
>>> 
>>> 
>>> Guozhang
>>> 
>>> On Mon, Sep 11, 2017 at 9:28 AM, Rajini Sivaram >> 
>>> wrote:
>>> 
 Hi Guozhang,
 
 Can KIP-188 be added to the list, please? The vote has passed and PR
>> should
 be ready soon.
 
 Thank you,
 
 Rajini
 
 On Thu, Sep 7, 2017 at 10:28 PM, Guozhang Wang 
>> wrote:
 
> Actually my bad, there is already a voting thread and you asked people
>> to
> recast a vote on a small change.
> 
> On Thu, Sep 7, 2017 at 2:27 PM, Guozhang Wang 
 wrote:
> 
>> Hi Tom,
>> 
>> It seems KIP-183 is still in the discussion phase, and voting has not
> been
>> started?
>> 
>> 
>> Guozhang
>> 
>> 
>> On Thu, Sep 7, 2017 at 1:13 AM, Tom Bentley 
> wrote:
>> 
>>> Would it be possible to add KIP-183 to the list too, please?
>>> 
>>> Thanks,
>>> 
>>> Tom
>>> 
>>> On 6 September 2017 at 22:04, Guozhang Wang 
 wrote:
>>> 
 Hi Vahid,
 
 Yes I have just added it while sending this email :)
 
 
 Guozhang
 
 On Wed, Sep 6, 2017 at 1:54 PM, Vahid S Hashemian <
 vahidhashem...@us.ibm.com
> wrote:
 
> Hi Guozhang,
> 
> Thanks for the heads-up.
> 
> Can KIP-163 be added to the list?
> The proposal for this KIP is accepted, and the PR is ready for
> review.
> 
> Thanks.
> --Vahid
> 
> 
> 
> From:   Guozhang Wang 
> To: "dev@kafka.apache.org" 
> Date:   09/06/2017 01:45 PM
> Subject:1.0.0 KIPs Update
> 
> 
> 
> Hello folks,
> 
> This is a heads up on 1.0.0 progress:
> 
> https://urldefense.proofpoint.com/v2/url?u=https-3A__cwiki.a
> pache.org_confluence_pages_viewpage.action-3FpageId-3D717649
> 13=DwIBaQ=jf_iaSHvJObTbx-siA1ZOg=Q_itwloTQj3_
> xUKl7Nzswo6KE4Nj-kjJc7uSVcviKUc=bLvgeykOujjty9joOuWXD4wZab
> o1CV0pULY4eqBxqzk=90UN7ejzCQmdPOyRR_
 2z304xLUSBCtOYi0KqhAo4EyU=
> 
> 
> We have one week left towards the KIP deadline, which is Sept.
 13th.
 There
> are still a lot of KIPs that under discussion / voting process.
 For
>>> the
> KIP
> proposer, please keep in mind that the voting has to be done
 before
>>> the
> deadline in order to be added into the coming release.
> 
> 
> Thanks,
> -- Guozhang
> 
> 
> 
> 
> 
 
 
 --
 -- Guozhang
 
>>> 
>> 
>> 
>> 
>> --
>> -- Guozhang
>> 
> 
> 
> 
> --
> -- Guozhang
> 
 
>>> 
>>> 
>>> 
>>> --
>>> -- Guozhang
>> 
>> 

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

[Apache Jenkins Server]

See 

[GitHub] kafka-site pull request #82: Adding minor style changes

[manjuapu]

GitHub user manjuapu opened a pull request:

https://github.com/apache/kafka-site/pull/82

Adding minor style changes



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/manjuapu/kafka-site cust

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka-site/pull/82.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #82


commit eda1f81ea42e3567bfc287b97ef0e3f67dfe0102
Author: Manjula K 
Date:   2017-09-19T23:03:34Z

Added Xite and Zalando logo to Powered by page

commit dd769457c697c7d2e918eeeab7092be2023ebae5
Author: Manjula K 
Date:   2017-09-19T23:09:43Z

Adding style to Streams page

commit cffed48a1c738d2b7ebe3091ab845ea3fe84dbb3
Author: Manjula K 
Date:   2017-09-20T01:03:03Z

removing extra indentation in style

commit 2ba5e5e6ff8ffb0b91b9a0d7f96b42e1e759c96e
Author: Manjula K 
Date:   2017-09-20T22:12:05Z

Add new style height for line company




---

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

[Apache Jenkins Server]

See 


Changes:

[me] KAFKA-5657: Connect REST API should include the connector type when

--
[...truncated 2.54 MB...]
org.apache.kafka.streams.integration.GlobalKTableIntegrationTest > 
shouldKStreamGlobalKTableLeftJoin STARTED

org.apache.kafka.streams.integration.GlobalKTableIntegrationTest > 
shouldKStreamGlobalKTableLeftJoin PASSED

org.apache.kafka.streams.integration.GlobalKTableIntegrationTest > 
shouldKStreamGlobalKTableJoin STARTED

org.apache.kafka.streams.integration.GlobalKTableIntegrationTest > 
shouldKStreamGlobalKTableJoin PASSED

org.apache.kafka.streams.integration.FanoutIntegrationTest > 
shouldFanoutTheInput STARTED

org.apache.kafka.streams.integration.FanoutIntegrationTest > 
shouldFanoutTheInput PASSED

org.apache.kafka.streams.integration.EosIntegrationTest > 
shouldBeAbleToRunWithEosEnabled STARTED

org.apache.kafka.streams.integration.EosIntegrationTest > 
shouldBeAbleToRunWithEosEnabled PASSED

org.apache.kafka.streams.integration.EosIntegrationTest > 
shouldBeAbleToCommitToMultiplePartitions STARTED

org.apache.kafka.streams.integration.EosIntegrationTest > 
shouldBeAbleToCommitToMultiplePartitions PASSED

org.apache.kafka.streams.integration.EosIntegrationTest > 
shouldNotViolateEosIfOneTaskFails STARTED

org.apache.kafka.streams.integration.EosIntegrationTest > 
shouldNotViolateEosIfOneTaskFails PASSED

org.apache.kafka.streams.integration.EosIntegrationTest > 
shouldBeAbleToPerformMultipleTransactions STARTED

org.apache.kafka.streams.integration.EosIntegrationTest > 
shouldBeAbleToPerformMultipleTransactions PASSED

org.apache.kafka.streams.integration.EosIntegrationTest > 
shouldBeAbleToCommitMultiplePartitionOffsets STARTED

org.apache.kafka.streams.integration.EosIntegrationTest > 
shouldBeAbleToCommitMultiplePartitionOffsets PASSED

org.apache.kafka.streams.integration.EosIntegrationTest > 
shouldBeAbleToRunWithTwoSubtopologies STARTED

org.apache.kafka.streams.integration.EosIntegrationTest > 
shouldBeAbleToRunWithTwoSubtopologies PASSED

org.apache.kafka.streams.integration.EosIntegrationTest > 
shouldNotViolateEosIfOneTaskGetsFencedUsingIsolatedAppInstances STARTED

org.apache.kafka.streams.integration.EosIntegrationTest > 
shouldNotViolateEosIfOneTaskGetsFencedUsingIsolatedAppInstances PASSED

org.apache.kafka.streams.integration.EosIntegrationTest > 
shouldNotViolateEosIfOneTaskFailsWithState STARTED

org.apache.kafka.streams.integration.EosIntegrationTest > 
shouldNotViolateEosIfOneTaskFailsWithState PASSED

org.apache.kafka.streams.integration.EosIntegrationTest > 
shouldBeAbleToRunWithTwoSubtopologiesAndMultiplePartitions STARTED

org.apache.kafka.streams.integration.EosIntegrationTest > 
shouldBeAbleToRunWithTwoSubtopologiesAndMultiplePartitions PASSED

org.apache.kafka.streams.integration.EosIntegrationTest > 
shouldBeAbleToRestartAfterClose STARTED

org.apache.kafka.streams.integration.EosIntegrationTest > 
shouldBeAbleToRestartAfterClose PASSED

org.apache.kafka.streams.integration.KStreamRepartitionJoinTest > 
shouldCorrectlyRepartitionOnJoinOperationsWithZeroSizedCache STARTED

org.apache.kafka.streams.integration.KStreamRepartitionJoinTest > 
shouldCorrectlyRepartitionOnJoinOperationsWithZeroSizedCache PASSED

org.apache.kafka.streams.integration.KStreamRepartitionJoinTest > 
shouldCorrectlyRepartitionOnJoinOperationsWithNonZeroSizedCache STARTED

org.apache.kafka.streams.integration.KStreamRepartitionJoinTest > 
shouldCorrectlyRepartitionOnJoinOperationsWithNonZeroSizedCache PASSED

org.apache.kafka.streams.integration.KStreamKTableJoinIntegrationTest > 
shouldCountClicksPerRegionWithZeroByteCache STARTED

org.apache.kafka.streams.integration.KStreamKTableJoinIntegrationTest > 
shouldCountClicksPerRegionWithZeroByteCache PASSED

org.apache.kafka.streams.integration.KStreamKTableJoinIntegrationTest > 
shouldCountClicksPerRegionWithNonZeroByteCache STARTED

org.apache.kafka.streams.integration.KStreamKTableJoinIntegrationTest > 
shouldCountClicksPerRegionWithNonZeroByteCache PASSED

org.apache.kafka.streams.integration.InternalTopicIntegrationTest > 
shouldCompactTopicsForStateChangelogs STARTED

org.apache.kafka.streams.integration.InternalTopicIntegrationTest > 
shouldCompactTopicsForStateChangelogs PASSED

org.apache.kafka.streams.integration.InternalTopicIntegrationTest > 
shouldUseCompactAndDeleteForWindowStoreChangelogs STARTED

org.apache.kafka.streams.integration.InternalTopicIntegrationTest > 
shouldUseCompactAndDeleteForWindowStoreChangelogs PASSED

org.apache.kafka.streams.integration.KStreamAggregationIntegrationTest > 
shouldReduceSessionWindows STARTED

org.apache.kafka.streams.integration.KStreamAggregationIntegrationTest > 
shouldReduceSessionWindows PASSED

org.apache.kafka.streams.integration.KStreamAggregationIntegrationTest > 
shouldReduce STARTED

[GitHub] kafka pull request #3922: Kafka 5854: Handle authentication failures in Kafk...

[rajinisivaram]

Github user rajinisivaram closed the pull request at:

https://github.com/apache/kafka/pull/3922


---

Re: 1.0.0 KIPs Update

[Ismael Juma]

Hi James,

Isn't PR 3799 purely a code refactoring (i.e. no change in behaviour)? If
so, it would probably land in trunk only after today. If it's new
functionality, then it depends on size, risk and importance. If you think
it's important and should target 1.0.0, feel free to make your case in the
JIRA or PR.

Thanks,
Ismael

On Wed, Sep 20, 2017 at 10:59 PM, James Cheng  wrote:

> Hi. I'm a little unclear on what types of things are subject to the
> "Feature Freeze" today (Sept 20th).
>
> For changes such as https://github.com/apache/kafka/pull/3799 <
> https://github.com/apache/kafka/pull/3799> and https://issues.apache.org/
> jira/browse/KAFKA-3480 
> that don't require KIPs, is today the freeze date? If I have PR created but
> not yet reviewed, does that mean it is eligible to get into 1.0.0?
>
> And if I have a PR that comes AFTER today, does that mean it is NOT
> eligible for 1.0.0?
>
> Thanks!
>
> -James
>
> > On Sep 11, 2017, at 12:14 PM, Guozhang Wang  wrote:
> >
> > Sure! Please feel free to update the wiki.
> >
> >
> > Guozhang
> >
> > On Mon, Sep 11, 2017 at 9:28 AM, Rajini Sivaram  >
> > wrote:
> >
> >> Hi Guozhang,
> >>
> >> Can KIP-188 be added to the list, please? The vote has passed and PR
> should
> >> be ready soon.
> >>
> >> Thank you,
> >>
> >> Rajini
> >>
> >> On Thu, Sep 7, 2017 at 10:28 PM, Guozhang Wang 
> wrote:
> >>
> >>> Actually my bad, there is already a voting thread and you asked people
> to
> >>> recast a vote on a small change.
> >>>
> >>> On Thu, Sep 7, 2017 at 2:27 PM, Guozhang Wang 
> >> wrote:
> >>>
>  Hi Tom,
> 
>  It seems KIP-183 is still in the discussion phase, and voting has not
> >>> been
>  started?
> 
> 
>  Guozhang
> 
> 
>  On Thu, Sep 7, 2017 at 1:13 AM, Tom Bentley 
> >>> wrote:
> 
> > Would it be possible to add KIP-183 to the list too, please?
> >
> > Thanks,
> >
> > Tom
> >
> > On 6 September 2017 at 22:04, Guozhang Wang 
> >> wrote:
> >
> >> Hi Vahid,
> >>
> >> Yes I have just added it while sending this email :)
> >>
> >>
> >> Guozhang
> >>
> >> On Wed, Sep 6, 2017 at 1:54 PM, Vahid S Hashemian <
> >> vahidhashem...@us.ibm.com
> >>> wrote:
> >>
> >>> Hi Guozhang,
> >>>
> >>> Thanks for the heads-up.
> >>>
> >>> Can KIP-163 be added to the list?
> >>> The proposal for this KIP is accepted, and the PR is ready for
> >>> review.
> >>>
> >>> Thanks.
> >>> --Vahid
> >>>
> >>>
> >>>
> >>> From:   Guozhang Wang 
> >>> To: "dev@kafka.apache.org" 
> >>> Date:   09/06/2017 01:45 PM
> >>> Subject:1.0.0 KIPs Update
> >>>
> >>>
> >>>
> >>> Hello folks,
> >>>
> >>> This is a heads up on 1.0.0 progress:
> >>>
> >>> https://urldefense.proofpoint.com/v2/url?u=https-3A__cwiki.a
> >>> pache.org_confluence_pages_viewpage.action-3FpageId-3D717649
> >>> 13=DwIBaQ=jf_iaSHvJObTbx-siA1ZOg=Q_itwloTQj3_
> >>> xUKl7Nzswo6KE4Nj-kjJc7uSVcviKUc=bLvgeykOujjty9joOuWXD4wZab
> >>> o1CV0pULY4eqBxqzk=90UN7ejzCQmdPOyRR_
> >> 2z304xLUSBCtOYi0KqhAo4EyU=
> >>>
> >>>
> >>> We have one week left towards the KIP deadline, which is Sept.
> >> 13th.
> >> There
> >>> are still a lot of KIPs that under discussion / voting process.
> >> For
> > the
> >>> KIP
> >>> proposer, please keep in mind that the voting has to be done
> >> before
> > the
> >>> deadline in order to be added into the coming release.
> >>>
> >>>
> >>> Thanks,
> >>> -- Guozhang
> >>>
> >>>
> >>>
> >>>
> >>>
> >>
> >>
> >> --
> >> -- Guozhang
> >>
> >
> 
> 
> 
>  --
>  -- Guozhang
> 
> >>>
> >>>
> >>>
> >>> --
> >>> -- Guozhang
> >>>
> >>
> >
> >
> >
> > --
> > -- Guozhang
>
>

[GitHub] kafka pull request #3927: KAFKA-5862: Remove ZK dependency from Streams rese...

[bbejeck]

GitHub user bbejeck opened a pull request:

https://github.com/apache/kafka/pull/3927

KAFKA-5862: Remove ZK dependency from Streams reset tool



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/bbejeck/kafka 
KAFKA-5862_remove_zk_dependency_from_streams_reset_tool

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/3927.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #3927


commit f6c8f2e1c91c8b4829a5a30187959adecc08b31a
Author: Bill Bejeck 
Date:   2017-09-20T22:08:59Z

KAFKA-5862: Remove ZK dependency from Streams reset tool




---

[jira] [Created] (KAFKA-5948) EosIntegrationTest fails with TopicAlreadyMarkedForDeletionException

[Matthias J. Sax (JIRA)]

Matthias J. Sax created KAFKA-5948:
--

 Summary: EosIntegrationTest fails with 
TopicAlreadyMarkedForDeletionException
 Key: KAFKA-5948
 URL: https://issues.apache.org/jira/browse/KAFKA-5948
 Project: Kafka
  Issue Type: Bug
  Components: streams, unit tests
Affects Versions: 0.11.0.1
Reporter: Matthias J. Sax
Assignee: Damian Guy


Seem to be a test setup race condition:

{noformat}
kafka.common.TopicAlreadyMarkedForDeletionException: topic 
singlePartitionThroughTopic is already marked for deletion
at kafka.admin.AdminUtils$.deleteTopic(AdminUtils.scala:340)
at kafka.admin.AdminUtils.deleteTopic(AdminUtils.scala)
at 
org.apache.kafka.streams.integration.utils.KafkaEmbedded.deleteTopic(KafkaEmbedded.java:200)
at 
org.apache.kafka.streams.integration.utils.EmbeddedKafkaCluster.deleteTopicsAndWait(EmbeddedKafkaCluster.java:268)
at 
org.apache.kafka.streams.integration.utils.EmbeddedKafkaCluster.deleteTopicsAndWait(EmbeddedKafkaCluster.java:256)
at 
org.apache.kafka.streams.integration.EosIntegrationTest.createTopics(EosIntegrationTest.java:102)
{noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: 1.0.0 KIPs Update

[James Cheng]

Hi. I'm a little unclear on what types of things are subject to the "Feature 
Freeze" today (Sept 20th). 

For changes such as https://github.com/apache/kafka/pull/3799 
 and 
https://issues.apache.org/jira/browse/KAFKA-3480 
 that don't require KIPs, is 
today the freeze date? If I have PR created but not yet reviewed, does that 
mean it is eligible to get into 1.0.0?

And if I have a PR that comes AFTER today, does that mean it is NOT eligible 
for 1.0.0?

Thanks!

-James

> On Sep 11, 2017, at 12:14 PM, Guozhang Wang  wrote:
> 
> Sure! Please feel free to update the wiki.
> 
> 
> Guozhang
> 
> On Mon, Sep 11, 2017 at 9:28 AM, Rajini Sivaram 
> wrote:
> 
>> Hi Guozhang,
>> 
>> Can KIP-188 be added to the list, please? The vote has passed and PR should
>> be ready soon.
>> 
>> Thank you,
>> 
>> Rajini
>> 
>> On Thu, Sep 7, 2017 at 10:28 PM, Guozhang Wang  wrote:
>> 
>>> Actually my bad, there is already a voting thread and you asked people to
>>> recast a vote on a small change.
>>> 
>>> On Thu, Sep 7, 2017 at 2:27 PM, Guozhang Wang 
>> wrote:
>>> 
 Hi Tom,
 
 It seems KIP-183 is still in the discussion phase, and voting has not
>>> been
 started?
 
 
 Guozhang
 
 
 On Thu, Sep 7, 2017 at 1:13 AM, Tom Bentley 
>>> wrote:
 
> Would it be possible to add KIP-183 to the list too, please?
> 
> Thanks,
> 
> Tom
> 
> On 6 September 2017 at 22:04, Guozhang Wang 
>> wrote:
> 
>> Hi Vahid,
>> 
>> Yes I have just added it while sending this email :)
>> 
>> 
>> Guozhang
>> 
>> On Wed, Sep 6, 2017 at 1:54 PM, Vahid S Hashemian <
>> vahidhashem...@us.ibm.com
>>> wrote:
>> 
>>> Hi Guozhang,
>>> 
>>> Thanks for the heads-up.
>>> 
>>> Can KIP-163 be added to the list?
>>> The proposal for this KIP is accepted, and the PR is ready for
>>> review.
>>> 
>>> Thanks.
>>> --Vahid
>>> 
>>> 
>>> 
>>> From:   Guozhang Wang 
>>> To: "dev@kafka.apache.org" 
>>> Date:   09/06/2017 01:45 PM
>>> Subject:1.0.0 KIPs Update
>>> 
>>> 
>>> 
>>> Hello folks,
>>> 
>>> This is a heads up on 1.0.0 progress:
>>> 
>>> https://urldefense.proofpoint.com/v2/url?u=https-3A__cwiki.a
>>> pache.org_confluence_pages_viewpage.action-3FpageId-3D717649
>>> 13=DwIBaQ=jf_iaSHvJObTbx-siA1ZOg=Q_itwloTQj3_
>>> xUKl7Nzswo6KE4Nj-kjJc7uSVcviKUc=bLvgeykOujjty9joOuWXD4wZab
>>> o1CV0pULY4eqBxqzk=90UN7ejzCQmdPOyRR_
>> 2z304xLUSBCtOYi0KqhAo4EyU=
>>> 
>>> 
>>> We have one week left towards the KIP deadline, which is Sept.
>> 13th.
>> There
>>> are still a lot of KIPs that under discussion / voting process.
>> For
> the
>>> KIP
>>> proposer, please keep in mind that the voting has to be done
>> before
> the
>>> deadline in order to be added into the coming release.
>>> 
>>> 
>>> Thanks,
>>> -- Guozhang
>>> 
>>> 
>>> 
>>> 
>>> 
>> 
>> 
>> --
>> -- Guozhang
>> 
> 
 
 
 
 --
 -- Guozhang
 
>>> 
>>> 
>>> 
>>> --
>>> -- Guozhang
>>> 
>> 
> 
> 
> 
> -- 
> -- Guozhang

[jira] [Created] (KAFKA-5947) Handle authentication failures from transactional producer and KafkaAdminClient

[Rajini Sivaram (JIRA)]

Rajini Sivaram created KAFKA-5947:
-

 Summary: Handle authentication failures from transactional 
producer and KafkaAdminClient
 Key: KAFKA-5947
 URL: https://issues.apache.org/jira/browse/KAFKA-5947
 Project: Kafka
  Issue Type: Improvement
  Components: clients
Reporter: Rajini Sivaram
Assignee: Rajini Sivaram
 Fix For: 1.0.0


Follow on from KAFKA-5854 to handle authentication failures better for 
transactional producer API and KafkaAdminClient



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] kafka pull request #3832: KAFKA-5854: Handle SASL authentication failures as...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/kafka/pull/3832


---

[GitHub] kafka pull request #3926: KAFKA-5934 Cross build for Scala 2.12

[schrepfler]

GitHub user schrepfler opened a pull request:

https://github.com/apache/kafka/pull/3926

KAFKA-5934 Cross build for Scala 2.12

Tried to do some simple refactorings to publish Kafka 0.8.x for Scala 2.12 
as it's still used quite a lot in the industry. Let me know if more needs to be 
done, I don't use gradle day to day plus there probably was a change in gradle 
4 which required a change to  build.gradle and I bumped the scala modules from 
1.0.2 to 1.0.6.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/William-Hill-Online/kafka 0.8.2

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/3926.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #3926


commit 43add2ab048dbd706d17960f0cebb737da926669
Author: Srdan Srepfler 
Date:   2017-09-19T23:42:33Z

KAFKA-5934 Cross build for Scala 2.12




---

[GitHub] kafka pull request #3923: MINOR: Upgrade to Gradle 4.2

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/kafka/pull/3923


---

[GitHub] kafka pull request #3925: KAFKA-5911 Avoid creation of extra Map for futures...

[tedyu]

GitHub user tedyu opened a pull request:

https://github.com/apache/kafka/pull/3925

KAFKA-5911 Avoid creation of extra Map for futures in KafkaAdminClient

This reduces creation of garbage while keeping thread safety untouched.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/tedyu/kafka trunk

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/3925.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #3925


commit b53379ed9a327b2c195dffc4c5d537fb0a0ace13
Author: tedyu 
Date:   2017-09-20T21:09:21Z

KAFKA-5911 Avoid creation of extra Map for futures in KafkaAdminClient




---

[GitHub] kafka pull request #3812: KAFKA-5657 Connect REST API should include the con...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/kafka/pull/3812


---

[jira] [Resolved] (KAFKA-5657) Connect REST API should include the connector type when describing a connector

[Ewen Cheslack-Postava (JIRA)]

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

Ewen Cheslack-Postava resolved KAFKA-5657.
--
Resolution: Fixed

Issue resolved by pull request 3812
[https://github.com/apache/kafka/pull/3812]

> Connect REST API should include the connector type when describing a connector
> --
>
> Key: KAFKA-5657
> URL: https://issues.apache.org/jira/browse/KAFKA-5657
> Project: Kafka
>  Issue Type: Improvement
>  Components: KafkaConnect
>Affects Versions: 0.11.0.0
>Reporter: Randall Hauch
>  Labels: needs-kip, newbie
> Fix For: 1.0.0
>
> Attachments: 5657.v1.txt
>
>
> Kafka Connect's REST API's {{connectors/}} and {{connectors/\{name\}}} 
> endpoints should include whether the connector is a source or a sink.
> See KAFKA-4343 and KIP-151 for the related modification of the 
> {{connector-plugins}} endpoint.
> Also see KAFKA-4279 for converter-related endpoints.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[Apache Jenkins Server]

See 


Changes:

[jason] KAFKA-5358; Consumer perf tool should count rebalance time (KIP-177)

--
[...truncated 2.55 MB...]

org.apache.kafka.streams.integration.KStreamsFineGrainedAutoResetIntegrationTest
 > shouldThrowStreamsExceptionNoResetSpecified PASSED

org.apache.kafka.streams.integration.RegexSourceIntegrationTest > 
testShouldReadFromRegexAndNamedTopics STARTED

org.apache.kafka.streams.integration.RegexSourceIntegrationTest > 
testShouldReadFromRegexAndNamedTopics PASSED

org.apache.kafka.streams.integration.RegexSourceIntegrationTest > 
testRegexMatchesTopicsAWhenCreated STARTED

org.apache.kafka.streams.integration.RegexSourceIntegrationTest > 
testRegexMatchesTopicsAWhenCreated PASSED

org.apache.kafka.streams.integration.RegexSourceIntegrationTest > 
testMultipleConsumersCanReadFromPartitionedTopic STARTED

org.apache.kafka.streams.integration.RegexSourceIntegrationTest > 
testMultipleConsumersCanReadFromPartitionedTopic PASSED

org.apache.kafka.streams.integration.RegexSourceIntegrationTest > 
testRegexMatchesTopicsAWhenDeleted STARTED

org.apache.kafka.streams.integration.RegexSourceIntegrationTest > 
testRegexMatchesTopicsAWhenDeleted PASSED

org.apache.kafka.streams.integration.RegexSourceIntegrationTest > 
testNoMessagesSentExceptionFromOverlappingPatterns STARTED

org.apache.kafka.streams.integration.RegexSourceIntegrationTest > 
testNoMessagesSentExceptionFromOverlappingPatterns PASSED

org.apache.kafka.streams.integration.RegexSourceIntegrationTest > 
shouldAddStateStoreToRegexDefinedSource STARTED

org.apache.kafka.streams.integration.RegexSourceIntegrationTest > 
shouldAddStateStoreToRegexDefinedSource PASSED

org.apache.kafka.streams.integration.KStreamRepartitionJoinTest > 
shouldCorrectlyRepartitionOnJoinOperationsWithZeroSizedCache STARTED

org.apache.kafka.streams.integration.KStreamRepartitionJoinTest > 
shouldCorrectlyRepartitionOnJoinOperationsWithZeroSizedCache PASSED

org.apache.kafka.streams.integration.KStreamRepartitionJoinTest > 
shouldCorrectlyRepartitionOnJoinOperationsWithNonZeroSizedCache STARTED

org.apache.kafka.streams.integration.KStreamRepartitionJoinTest > 
shouldCorrectlyRepartitionOnJoinOperationsWithNonZeroSizedCache PASSED

org.apache.kafka.streams.integration.InternalTopicIntegrationTest > 
shouldCompactTopicsForStateChangelogs STARTED

org.apache.kafka.streams.integration.InternalTopicIntegrationTest > 
shouldCompactTopicsForStateChangelogs PASSED

org.apache.kafka.streams.integration.InternalTopicIntegrationTest > 
shouldUseCompactAndDeleteForWindowStoreChangelogs STARTED

org.apache.kafka.streams.integration.InternalTopicIntegrationTest > 
shouldUseCompactAndDeleteForWindowStoreChangelogs PASSED

org.apache.kafka.streams.integration.KStreamAggregationIntegrationTest > 
shouldReduceSessionWindows STARTED

org.apache.kafka.streams.integration.KStreamAggregationIntegrationTest > 
shouldReduceSessionWindows PASSED

org.apache.kafka.streams.integration.KStreamAggregationIntegrationTest > 
shouldReduce STARTED

org.apache.kafka.streams.integration.KStreamAggregationIntegrationTest > 
shouldReduce PASSED

org.apache.kafka.streams.integration.KStreamAggregationIntegrationTest > 
shouldAggregate STARTED

org.apache.kafka.streams.integration.KStreamAggregationIntegrationTest > 
shouldAggregate PASSED

org.apache.kafka.streams.integration.KStreamAggregationIntegrationTest > 
shouldCount STARTED

org.apache.kafka.streams.integration.KStreamAggregationIntegrationTest > 
shouldCount PASSED

org.apache.kafka.streams.integration.KStreamAggregationIntegrationTest > 
shouldGroupByKey STARTED

org.apache.kafka.streams.integration.KStreamAggregationIntegrationTest > 
shouldGroupByKey PASSED

org.apache.kafka.streams.integration.KStreamAggregationIntegrationTest > 
shouldCountWithInternalStore STARTED

org.apache.kafka.streams.integration.KStreamAggregationIntegrationTest > 
shouldCountWithInternalStore PASSED

org.apache.kafka.streams.integration.KStreamAggregationIntegrationTest > 
shouldReduceWindowed STARTED

org.apache.kafka.streams.integration.KStreamAggregationIntegrationTest > 
shouldReduceWindowed PASSED

org.apache.kafka.streams.integration.KStreamAggregationIntegrationTest > 
shouldCountSessionWindows STARTED

org.apache.kafka.streams.integration.KStreamAggregationIntegrationTest > 
shouldCountSessionWindows PASSED

org.apache.kafka.streams.integration.KStreamAggregationIntegrationTest > 
shouldAggregateWindowed STARTED

org.apache.kafka.streams.integration.KStreamAggregationIntegrationTest > 
shouldAggregateWindowed PASSED

org.apache.kafka.streams.integration.GlobalKTableIntegrationTest > 
shouldKStreamGlobalKTableLeftJoin STARTED

org.apache.kafka.streams.integration.GlobalKTableIntegrationTest > 
shouldKStreamGlobalKTableLeftJoin PASSED

org.apache.kafka.streams.integration.GlobalKTableIntegrationTest > 
shouldKStreamGlobalKTableJoin 

[jira] [Created] (KAFKA-5946) Give connector method parameter better name

[Ted Yu (JIRA)]

Ted Yu created KAFKA-5946:
-

 Summary: Give connector method parameter better name
 Key: KAFKA-5946
 URL: https://issues.apache.org/jira/browse/KAFKA-5946
 Project: Kafka
  Issue Type: Improvement
Reporter: Ted Yu


During the development of KAFKA-5657, there were several iterations where 
method call didn't match what the connector parameter actually represents.

[~ewencp] had used connType as equivalent to connClass because Type wasn't used 
to differentiate source vs sink.

[~ewencp] proposed the following:
It would help to convert all the uses of connType to connClass first, then 
standardize on class == java class, type == source/sink, name == user-specified 
name.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (KAFKA-5945) Improve handling of authentication failures when credentials are removed

[Rajini Sivaram (JIRA)]

Rajini Sivaram created KAFKA-5945:
-

 Summary: Improve handling of authentication failures when 
credentials are removed
 Key: KAFKA-5945
 URL: https://issues.apache.org/jira/browse/KAFKA-5945
 Project: Kafka
  Issue Type: Improvement
  Components: clients
Affects Versions: 1.0.0
Reporter: Rajini Sivaram
Assignee: Rajini Sivaram


KAFKA-5854 improves the handling of authentication failures. The scope of 
KAFKA-5854  was limited to a specific scenario - provide better feedback to 
applications when security is misconfigured. The PR improves diagnostics for 
this scenario by throwing an AuthenticationException and also avoids retries. 
To enable this, the first request initiated by any public API was updated to 
throw authentication exceptions.

This JIRA is for a more extensive handling of authentication exceptions which 
also includes proper handling of credential updates at any time. If a 
credential is removed, then we could see authentication exception from any 
request and we want to propagate this properly. This needs quite extensive 
testing and is less likely to be hit by users, so it will be done later under 
this JIRA.

The gaps that need covering are:
1. Ensure authentication failures are processed in the Network client for any 
request
2. Ensure metadata refresh failures are handled properly at any time
3. Heartbeat threads and other background threads should handle authentication 
failures. Threads should not terminate on failure, but should avoid retries 
until application performs a new operation.




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (KAFKA-5944) Add unit tests for handling of authentication failures in clients

[Rajini Sivaram (JIRA)]

Rajini Sivaram created KAFKA-5944:
-

 Summary: Add unit tests for handling of authentication failures in 
clients
 Key: KAFKA-5944
 URL: https://issues.apache.org/jira/browse/KAFKA-5944
 Project: Kafka
  Issue Type: Test
  Components: clients
Reporter: Rajini Sivaram
 Fix For: 1.0.0


KAFKA-5854 improves authentication failures in clients and has added 
integration tests and some basic client-side tests that create actual 
connections to a mock server. It will be good to add a set of tests for 
producers, consumers etc. that use MockClient to add more extensive tests for 
various scenarios.

cc [~hachikuji] [~vahid]



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Jenkins build is back to normal : kafka-0.11.0-jdk7 #310

[Apache Jenkins Server]

See 

[GitHub] kafka pull request #3924: KAFKA-5547: Return TOPIC_AUTHORIZATION_FAILED erro...

[omkreddy]

GitHub user omkreddy opened a pull request:

https://github.com/apache/kafka/pull/3924

KAFKA-5547: Return TOPIC_AUTHORIZATION_FAILED error if no describe access 
for topics



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/omkreddy/kafka KAFKA-5547-TOPIC-AUTHRO

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/3924.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #3924


commit ea7d4e795aba6059b61dc518f38ed11d81b38c09
Author: Manikumar Reddy 
Date:   2017-09-15T16:22:57Z

KAFKA-5547: Return TOPIC_AUTHORIZATION_FAILED error if no describe access 
for topics




---

[GitHub] kafka pull request #3188: KAFKA-5358: Consumer perf tool should count rebala...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/kafka/pull/3188


---

[jira] [Resolved] (KAFKA-5358) Consumer perf tool should count rebalance time separately

[Jason Gustafson (JIRA)]

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

Jason Gustafson resolved KAFKA-5358.

   Resolution: Fixed
Fix Version/s: 1.0.0

Issue resolved by pull request 3188
[https://github.com/apache/kafka/pull/3188]

> Consumer perf tool should count rebalance time separately
> -
>
> Key: KAFKA-5358
> URL: https://issues.apache.org/jira/browse/KAFKA-5358
> Project: Kafka
>  Issue Type: Improvement
>Reporter: Jason Gustafson
>Assignee: huxihx
> Fix For: 1.0.0
>
>
> It would be helpful to measure rebalance time separately in the performance 
> tool so that throughput between different versions can be compared more 
> easily in spite of improvements such as 
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-134%3A+Delay+initial+consumer+group+rebalance.
>  At the moment, running the perf tool on 0.11.0 or trunk for a short amount 
> of time will present a severely skewed picture since the overall time will be 
> dominated by the join group delay.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] kafka pull request #3914: Adding See how Kafka Streams is being used section...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/kafka/pull/3914


---

[GitHub] kafka pull request #3923: MINOR: Upgrade to Gradle 4.2

[ijuma]

GitHub user ijuma opened a pull request:

https://github.com/apache/kafka/pull/3923

MINOR: Upgrade to Gradle 4.2

It includes the usual performance improvements, but
the nicest improvement for me is that the findBugs
plugin no longer outputs almost 1000 lines in
Jenkins builds:


https://docs.gradle.org/4.2/release-notes.html#findbugs-plugin-does-not-render-analysis-progress-anymore

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/ijuma/kafka gradle-4.2

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/3923.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #3923


commit 79517c5dabcabe4aaf7b9d7c495d54a032db4f56
Author: Ismael Juma 
Date:   2017-09-20T15:49:00Z

MINOR: Upgrade to Gradle 4.2

It includes the usual performance improvements, but
the nicest improvement for me is that the findBugs
plugin no longer outputs almost 1000 lines in
Jenkins builds:


https://docs.gradle.org/4.2/release-notes.html#findbugs-plugin-does-not-render-analysis-progress-anymore




---

[GitHub] kafka pull request #3922: Kafka 5854: Handle authentication failures in Kafk...

[rajinisivaram]

GitHub user rajinisivaram opened a pull request:

https://github.com/apache/kafka/pull/3922

Kafka 5854: Handle authentication failures in KafkaAdminClient

This is currently on top of the commits from #3832. 

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/rajinisivaram/kafka KAFKA-5854-adminclient

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/3922.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #3922


commit f5878201303f4bb43a5b20f7abdef6f5a9af8fc1
Author: Vahid Hashemian 
Date:   2017-09-15T17:50:41Z

KAFKA-5854: Handle SASL authentication failures as non-retriable exceptions 
in clients

This PR implements the client-side of KIP-152, by modifying 
`KafkaConsumer`, `KafkaProducer`, and `ConsumerGroupCommand` to throw a 
non-retriable exception when user authentication fails.

This PR is co-authored with @rajinisivaram.

commit a16a794f5ae06572d1434943f2765fa0f942bfa2
Author: Vahid Hashemian 
Date:   2017-09-18T20:57:33Z

Addressed feedback on the initial commit.

Thanks to @rajinisivaram for the review and sharing some of the code to 
speed things up.

commit 5388b916fd94889ad0c8e7068bb61946e20ccd19
Author: Vahid Hashemian 
Date:   2017-09-19T19:00:47Z

Addressed additional feedback received

commit a6e67a7e89e1437cdf8d44b73e28ecb2cd959c1f
Author: Vahid Hashemian 
Date:   2017-09-20T01:36:47Z

Minor changes based on the feedback received

commit d19874a06a98264f021d4af4a70326865657b8b3
Author: Vahid Hashemian 
Date:   2017-09-20T01:43:53Z

Merge branch 'trunk' into KAFKA-5854

commit a89fe929776b39e4c27d8c8aee7c4630e115a398
Author: Rajini Sivaram 
Date:   2017-09-20T15:27:23Z

KAFKA-5854: Handle authentication exceptions in KafkaAdminClient




---

[jira] [Created] (KAFKA-5943) Reduce dependency on mock in connector tests

[Ted Yu (JIRA)]

Ted Yu created KAFKA-5943:
-

 Summary: Reduce dependency on mock in connector tests
 Key: KAFKA-5943
 URL: https://issues.apache.org/jira/browse/KAFKA-5943
 Project: Kafka
  Issue Type: Improvement
Reporter: Ted Yu


Currently connector tests make heavy use of mock (easymock, power mock).

This often hides the real logic behind operations and makes finding bugs 
difficult.

We should reduce the use of mocks so that developers can debug connector code 
using unit tests.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] kafka pull request #3921: MINOR: add upgrade note for KIP-173 topic configs

[dguy]

GitHub user dguy opened a pull request:

https://github.com/apache/kafka/pull/3921

MINOR: add upgrade note for KIP-173 topic configs



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/dguy/kafka minor-kip-173-docs

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/3921.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #3921


commit 1d34eb692a2ab20cc72a53ee69d6b3ce9bbf63c2
Author: Damian Guy 
Date:   2017-09-20T12:55:47Z

add note for topic configs




---

[jira] [Created] (KAFKA-5942) Handle authentication failures in streams

[Rajini Sivaram (JIRA)]

Rajini Sivaram created KAFKA-5942:
-

 Summary: Handle authentication failures in streams
 Key: KAFKA-5942
 URL: https://issues.apache.org/jira/browse/KAFKA-5942
 Project: Kafka
  Issue Type: Improvement
  Components: streams
Reporter: Rajini Sivaram


KIP-152 added support for clients to detect authentication failures. Prior to 
this, clients handled authentication failures as retriable I/O exceptions, 
making it hard for users to diagnose security misconfiguration. We should 
verify that streams handle authentication failures and report them.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (KAFKA-5941) Handle authentication failures in connect

[Rajini Sivaram (JIRA)]

Rajini Sivaram created KAFKA-5941:
-

 Summary: Handle authentication failures in connect
 Key: KAFKA-5941
 URL: https://issues.apache.org/jira/browse/KAFKA-5941
 Project: Kafka
  Issue Type: Improvement
  Components: KafkaConnect
Reporter: Rajini Sivaram


KIP-152 added support for clients to detect authentication failures. Prior to 
this, clients handled authentication failures as retriable I/O exceptions, 
making it hard for users to diagnose security misconfiguration. We should 
verify that connectors handle authentication failures and report them.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: Limit Jenkins jobs on H0 to H13

[Ismael Juma]

Hi Ted,

Thanks for following up with INFRA on the issues we've been seeing. I asked
a clarifying comment in that ticket (for some reason it only allowed me to
add an internal comment).

Ismael

On Wed, Sep 20, 2017 at 2:31 AM, Ted Yu  wrote:

> Hi,
> See Gavin's comment:
>
> https://issues.apache.org/jira/browse/INFRA-15084?page=
> com.atlassian.jira.plugin.system.issuetabpanels:comment-
> tabpanel=16172575#comment-16172575
>
> Can someone with admin permission modify the Jenkins job(s) ?
>
> Thanks
>

[GitHub] kafka pull request #3905: MINOR: change task initialization logging levels

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/kafka/pull/3905


---

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

[Apache Jenkins Server]

See 

[jira] [Resolved] (KAFKA-5931) Deprecate KTable#to and KTable#through

[Damian Guy (JIRA)]

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

Damian Guy resolved KAFKA-5931.
---
Resolution: Fixed

Issue resolved by pull request 3903
[https://github.com/apache/kafka/pull/3903]

> Deprecate KTable#to and KTable#through
> --
>
> Key: KAFKA-5931
> URL: https://issues.apache.org/jira/browse/KAFKA-5931
> Project: Kafka
>  Issue Type: Sub-task
>  Components: streams
>Reporter: Damian Guy
>Assignee: Damian Guy
> Fix For: 1.0.0
>
>
> {{KTable#to}} and {{KTable#through}} should be deprecated in favour of using 
> {{KTable#toStream}}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] kafka pull request #3903: KAFKA-5931: deprecate KTable#through and KTable#to

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/kafka/pull/3903


---

[GitHub] kafka pull request #3920: KAFKA5940: Throw exception if the JSON file is inv...

[scholzj]

GitHub user scholzj opened a pull request:

https://github.com/apache/kafka/pull/3920

KAFKA5940: Throw exception if the JSON file is invalid

Throw an exception when the JSON file with topics/partitions and offsets is 
incorrect (= when Json.parseFull(...) returns None).

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/scholzj/kafka KAFKA-5940

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/3920.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #3920


commit 870167e1d33710e129506621578e019634510bc9
Author: Jakub Scholz 
Date:   2017-09-20T11:00:45Z

Throw exception if the JSON file is invalid




---

[jira] [Created] (KAFKA-5940) kafka-delete-records.sh doesn't give any feedback when the JSON offset configuration file is invalid

[Jakub Scholz (JIRA)]

Jakub Scholz created KAFKA-5940:
---

 Summary: kafka-delete-records.sh doesn't give any feedback when 
the JSON offset configuration file is invalid
 Key: KAFKA-5940
 URL: https://issues.apache.org/jira/browse/KAFKA-5940
 Project: Kafka
  Issue Type: Improvement
  Components: tools
Reporter: Jakub Scholz
Assignee: Jakub Scholz


When deleting records using {{bin/kafka-delete-records.sh}}, the user has to 
pass a JSON file with the list of topics/partitions and the offset to which the 
records should be deleted. However, currently when such file is invalid the 
utility doesn't print any visible error:

{code}
$ bin/kafka-delete-records.sh --bootstrap-server localhost:9092 
--offset-json-file offset.json
Executing records delete operation
Records delete operation completed:
$
{code}

Instead, I would suggest that it throws an exception to make it clear that the 
problem is the invalid JSON file:
{code}
$ bin/kafka-delete-records.sh --bootstrap-server localhost:9092 
--offset-json-file offset.json
Exception in thread "main" kafka.common.AdminCommandFailedException: Offset 
json file doesn't contain valid JSON data.
at 
kafka.admin.DeleteRecordsCommand$.parseOffsetJsonStringWithoutDedup(DeleteRecordsCommand.scala:54)
at 
kafka.admin.DeleteRecordsCommand$.execute(DeleteRecordsCommand.scala:62)
at kafka.admin.DeleteRecordsCommand$.main(DeleteRecordsCommand.scala:37)
at kafka.admin.DeleteRecordsCommand.main(DeleteRecordsCommand.scala)
$
{code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Jenkins build is back to normal : kafka-trunk-jdk7 #2786

[Apache Jenkins Server]

See 

[GitHub] kafka-site pull request #81: MINOR: Fix typo in the gradle command for code ...

[scholzj]

GitHub user scholzj opened a pull request:

https://github.com/apache/kafka-site/pull/81

MINOR: Fix typo in the gradle command for code style check

Fix typo in the gradle command for code style check: chec**k**styleMain 
instead of chec**h**styleMain

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/scholzj/kafka-site coding-guide-typo

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka-site/pull/81.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #81


commit 644a677161800cbc384e196bda40188c26f7351e
Author: Jakub Scholz 
Date:   2017-09-20T10:01:42Z

Fix typo in the gradle command for code style check




---

[GitHub] kafka pull request #3846: MINOR: update release script for streams quickstar...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/kafka/pull/3846


---

[jira] [Created] (KAFKA-5939) Add a dryrun option to release.py

[Damian Guy (JIRA)]

Damian Guy created KAFKA-5939:
-

 Summary: Add a dryrun option to release.py
 Key: KAFKA-5939
 URL: https://issues.apache.org/jira/browse/KAFKA-5939
 Project: Kafka
  Issue Type: Bug
  Components: tools
Reporter: Damian Guy


It would be great to add a `dryrun` feature to `release.py` so that it can be 
used to test changes to the scripts etc. At the moment you need to make sure 
all JIRAs are closed for the release, have no uncommited changes etc, which is 
a bit of a hassle when you just want to test a change you've made to the 
script. There may be other things that need to be skipped, too



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] kafka pull request #3758: KAFKA-3131: enable error level for SSLException lo...

[omkreddy]

Github user omkreddy closed the pull request at:

https://github.com/apache/kafka/pull/3758


---

[GitHub] kafka pull request #3919: [MINOR] Where possible, introduce EnumMap.

[KoenDG]

GitHub user KoenDG opened a pull request:

https://github.com/apache/kafka/pull/3919

[MINOR] Where possible, introduce EnumMap.

Very simple PR, introduce EnumMap in 2 places of the code.

EnumMap: https://docs.oracle.com/javase/7/docs/api/java/util/EnumMap.html

EnumMap is meant to be used when the key of a Map is an Enum.

From the documentation: 

> Enum maps are represented internally as arrays. This representation is 
extremely compact and efficient.

Should use less memory per instance and also be faster in lookup.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/KoenDG/kafka enummap

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/3919.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #3919


commit 6af0ead332c40a531f0974e5ea7c2f97582d18d4
Author: KoenDG 
Date:   2017-09-20T07:33:54Z

Where possible, introduce EnumMap.




---

[jira] [Created] (KAFKA-5938) Oracle jdbc-source-connector with kafka-connect distributed mode will result in http 500 error

[Wolfgang Clemens (JIRA)]

Wolfgang Clemens created KAFKA-5938:
---

 Summary: Oracle jdbc-source-connector with kafka-connect 
distributed mode will result in http 500 error
 Key: KAFKA-5938
 URL: https://issues.apache.org/jira/browse/KAFKA-5938
 Project: Kafka
  Issue Type: Bug
  Components: KafkaConnect
Affects Versions: 0.11.0.0
Reporter: Wolfgang Clemens


When I try to add an oracle jdbc source connector in kafka-connect distributed 
mode via curl it will end up in a http 500 error.
To reproduce, feel free to clone my repo for that error: 
https://github.com/TranceMaster86/kafka-connect-oracle-error
In the readme I described how to reproduce the error.

It will hang up kafka-connect completely. All other connectors seems to stop 
working after I want to create an oracle jdbc source connector with a '@' in 
the connection string. I think this will be the main problem here. The oracle 
connection string looks like 'jdbc:oracle:thin:@hostname:port/service' or 
'jdbc:oracle:thin:@hostname:port:SID'.

See also: https://github.com/confluentinc/cp-docker-images/issues/338



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] kafka pull request #3811: KAFKA-5839: Upgrade Guide doc changes for KIP-130

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/kafka/pull/3811


---

[GitHub] kafka pull request #3918: KAFKA-5920: Handle SSL handshake failures as authe...

[rajinisivaram]

GitHub user rajinisivaram opened a pull request:

https://github.com/apache/kafka/pull/3918

KAFKA-5920: Handle SSL handshake failures as authentication exceptions



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/rajinisivaram/kafka 
KAFKA-5920-SSL-handshake-failure

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/3918.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #3918


commit baada6c9c7ddf85ec00bd5bf23b464ed79571283
Author: Rajini Sivaram 
Date:   2017-09-18T22:06:48Z

KAFKA-5920: Handle SSL handshake failures as authentication exceptions




---

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

[Apache Jenkins Server]

See 


Changes:

[wangguoz] MINOR: various random minor fixes and improve KafkaConsumer JavaDocs

--
[...truncated 4.95 MB...]

org.apache.kafka.streams.StreamsConfigTest > 
shouldResetToDefaultIfConsumerAutoCommitIsOverridden PASSED

org.apache.kafka.streams.StreamsConfigTest > 
shouldThrowExceptionIfNotAtLestOnceOrExactlyOnce STARTED

org.apache.kafka.streams.StreamsConfigTest > 
shouldThrowExceptionIfNotAtLestOnceOrExactlyOnce PASSED

org.apache.kafka.streams.StreamsConfigTest > 
shouldAllowSettingConsumerIsolationLevelIfEosDisabled STARTED

org.apache.kafka.streams.StreamsConfigTest > 
shouldAllowSettingConsumerIsolationLevelIfEosDisabled PASSED

org.apache.kafka.streams.StreamsConfigTest > 
shouldSupportPrefixedProducerConfigs STARTED

org.apache.kafka.streams.StreamsConfigTest > 
shouldSupportPrefixedProducerConfigs PASSED

org.apache.kafka.streams.StreamsConfigTest > 
shouldSupportPrefixedPropertiesThatAreNotPartOfRestoreConsumerConfig STARTED

org.apache.kafka.streams.StreamsConfigTest > 
shouldSupportPrefixedPropertiesThatAreNotPartOfRestoreConsumerConfig PASSED

org.apache.kafka.streams.StreamsConfigTest > 
shouldOverrideStreamsDefaultProducerConfigs STARTED

org.apache.kafka.streams.StreamsConfigTest > 
shouldOverrideStreamsDefaultProducerConfigs PASSED

org.apache.kafka.streams.StreamsConfigTest > 
shouldSupportPrefixedPropertiesThatAreNotPartOfProducerConfig STARTED

org.apache.kafka.streams.StreamsConfigTest > 
shouldSupportPrefixedPropertiesThatAreNotPartOfProducerConfig PASSED

org.apache.kafka.streams.StreamsConfigTest > 
shouldBeBackwardsCompatibleWithDeprecatedConfigs STARTED

org.apache.kafka.streams.StreamsConfigTest > 
shouldBeBackwardsCompatibleWithDeprecatedConfigs PASSED

org.apache.kafka.streams.StreamsConfigTest > 
shouldBeSupportNonPrefixedConsumerConfigs STARTED

org.apache.kafka.streams.StreamsConfigTest > 
shouldBeSupportNonPrefixedConsumerConfigs PASSED

org.apache.kafka.streams.StreamsConfigTest > 
shouldOverrideStreamsDefaultConsumerConifgsOnRestoreConsumer STARTED

org.apache.kafka.streams.StreamsConfigTest > 
shouldOverrideStreamsDefaultConsumerConifgsOnRestoreConsumer PASSED

org.apache.kafka.streams.StreamsConfigTest > shouldAcceptExactlyOnce STARTED

org.apache.kafka.streams.StreamsConfigTest > shouldAcceptExactlyOnce PASSED

org.apache.kafka.streams.StreamsConfigTest > 
shouldSetInternalLeaveGroupOnCloseConfigToFalseInConsumer STARTED

org.apache.kafka.streams.StreamsConfigTest > 
shouldSetInternalLeaveGroupOnCloseConfigToFalseInConsumer PASSED

org.apache.kafka.streams.StreamsConfigTest > 
shouldSupportPrefixedPropertiesThatAreNotPartOfConsumerConfig STARTED

org.apache.kafka.streams.StreamsConfigTest > 
shouldSupportPrefixedPropertiesThatAreNotPartOfConsumerConfig PASSED

org.apache.kafka.streams.StreamsConfigTest > 
shouldResetToDefaultIfRestoreConsumerAutoCommitIsOverridden STARTED

org.apache.kafka.streams.StreamsConfigTest > 
shouldResetToDefaultIfRestoreConsumerAutoCommitIsOverridden PASSED

org.apache.kafka.streams.StreamsConfigTest > 
shouldSpecifyCorrectValueSerdeClassOnError STARTED

org.apache.kafka.streams.StreamsConfigTest > 
shouldSpecifyCorrectValueSerdeClassOnError PASSED

org.apache.kafka.streams.StreamsConfigTest > 
shouldSpecifyCorrectValueSerdeClassOnErrorUsingDeprecatedConfigs STARTED

org.apache.kafka.streams.StreamsConfigTest > 
shouldSpecifyCorrectValueSerdeClassOnErrorUsingDeprecatedConfigs PASSED

org.apache.kafka.streams.StreamsConfigTest > 
shouldResetToDefaultIfConsumerIsolationLevelIsOverriddenIfEosEnabled STARTED

org.apache.kafka.streams.StreamsConfigTest > 
shouldResetToDefaultIfConsumerIsolationLevelIsOverriddenIfEosEnabled PASSED

org.apache.kafka.streams.StreamsConfigTest > 
shouldNotOverrideUserConfigCommitIntervalMsIfExactlyOnceEnabled STARTED

org.apache.kafka.streams.StreamsConfigTest > 
shouldNotOverrideUserConfigCommitIntervalMsIfExactlyOnceEnabled PASSED

org.apache.kafka.streams.StreamsConfigTest > 
shouldSupportMultipleBootstrapServers STARTED

org.apache.kafka.streams.StreamsConfigTest > 
shouldSupportMultipleBootstrapServers PASSED

org.apache.kafka.streams.StreamsConfigTest > 
shouldThrowStreamsExceptionIfKeySerdeConfigFails STARTED

org.apache.kafka.streams.StreamsConfigTest > 
shouldThrowStreamsExceptionIfKeySerdeConfigFails PASSED

org.apache.kafka.streams.StreamsConfigTest > 
shouldSupportNonPrefixedProducerConfigs STARTED

org.apache.kafka.streams.StreamsConfigTest > 
shouldSupportNonPrefixedProducerConfigs PASSED

org.apache.kafka.streams.StreamsConfigTest > testGetRestoreConsumerConfigs 
STARTED

org.apache.kafka.streams.StreamsConfigTest > testGetRestoreConsumerConfigs 
PASSED

org.apache.kafka.streams.StreamsConfigTest > 
shouldThrowExceptionIfBootstrapServersIsNotSet STARTED

org.apache.kafka.streams.StreamsConfigTest > 
shouldThrowExceptionIfBootstrapServersIsNotSet PASSED