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

See Changes: [wangguoz] KAFKA-5660 Don't throw TopologyBuilderException during runtime (#4645) -- [...truncated 3.51 MB...] kafka.zookeeper.ZooKeeperClientTest > testZNo

[jira] [Created] (KAFKA-6619) InstanceAlreadyExistsException while Tomcat starting up

xiezhi created KAFKA-6619: - Summary: InstanceAlreadyExistsException while Tomcat starting up Key: KAFKA-6619 URL: https://issues.apache.org/jira/browse/KAFKA-6619 Project: Kafka Issue Type: Bug A

[jira] [Created] (KAFKA-6618) Prevent two controllers from updating znodes concurrently

Dong Lin created KAFKA-6618: --- Summary: Prevent two controllers from updating znodes concurrently Key: KAFKA-6618 URL: https://issues.apache.org/jira/browse/KAFKA-6618 Project: Kafka Issue Type: Imp

[jira] [Resolved] (KAFKA-4974) System test failure in 0.8.2.2 upgrade tests

[ https://issues.apache.org/jira/browse/KAFKA-4974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-4974. Resolution: Fixed > System test failure in 0.8.2.2 upgrade tests > -

[jira] [Resolved] (KAFKA-5626) Producer should be able to negotiate ProduceRequest version with broker

[ https://issues.apache.org/jira/browse/KAFKA-5626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin resolved KAFKA-5626. - Resolution: Duplicate Fixed in https://issues.apache.org/jira/browse/KAFKA-5960 > Producer should be able

[jira] [Created] (KAFKA-6617) Improve controller performance by batching reassignment znode write operation

Dong Lin created KAFKA-6617: --- Summary: Improve controller performance by batching reassignment znode write operation Key: KAFKA-6617 URL: https://issues.apache.org/jira/browse/KAFKA-6617 Project: Kafka

[jira] [Resolved] (KAFKA-5999) Offset Fetch Request

[ https://issues.apache.org/jira/browse/KAFKA-5999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava resolved KAFKA-5999. -- Resolution: Invalid Assignee: Ewen Cheslack-Postava Closing as Invalid unt

Re: Exposing additional metadata in Kafka Connect schema parameters

I can only speak to my view on it, but I view logical types as truly generic. The point is that they can be handled as the underlying type safely, processed as such as needed, but if the logical type is properly preserved they can properly translate through as the more "complicated" type. To me, t

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

See

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

See Changes: [wangguoz] KAFKA-5660 Don't throw TopologyBuilderException during runtime (#4645) -- [...truncated 419.09 KB...] kafka.tools.ConsoleConsumerTest > shouldPar

Re: [DISCUSS] KIP-250 Add Support for Quorum-based Producer Acknowledgment

Hi, Colin, A couple of thoughts on your previous comments. 1. I am not sure if the controller is necessarily a bottleneck for leader election. In the common case, leader election is due to a single broker failure. So, the controller only needs to change the leaders for the number of partitions on

Re: [DISCUSSION] KIP-266: Add TimeoutException to KafkaConsumer#position()

I agree that adding the overloads is most flexible. But going for that direction we'd do that for all the blocking call that I've listed above, with this timeout value covering the end-to-end waiting time. Guozhang On Tue, Mar 6, 2018 at 10:02 AM, Ted Yu wrote: > bq. The most flexible option i

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

See

Re: [ANNOUNCE] Apache Kafka 1.0.1 Released

Congrats, everyone! Thanks for driving the release, Ewen! -James > On Mar 6, 2018, at 1:22 PM, Guozhang Wang wrote: > > Ewen, thanks for driving the release!! > > > Guozhang > > On Tue, Mar 6, 2018 at 1:14 PM, Ewen Cheslack-Postava wrote: > >> The Apache Kafka community is pleased to annou

Re: [DISCUSS] KIP-211: Revise Expiration Semantics of Consumer Group Offsets

Hi Jason, Thanks a lot for your clarification and feedback. Your statements below all seem reasonable to me. I have updated the KIP according to the conversation so far. It contains significant changes compared to the initial version, so it might be worth glancing over the whole thing one more t

[jira] [Created] (KAFKA-6616) kafka-merge-pr.py should use GitHub's REST API to merge

Ismael Juma created KAFKA-6616: -- Summary: kafka-merge-pr.py should use GitHub's REST API to merge Key: KAFKA-6616 URL: https://issues.apache.org/jira/browse/KAFKA-6616 Project: Kafka Issue Type:

Re: [DISCUSS] KIP-253: Support in-order message delivery with partition expansion

Hi, Mattias, Regarding your comment "If it would be time-delay based, it might be problematic for Kafka Streams: if we get the information that the new input partitions are available for producing, we need to enable the new changelog partitions for producing, too. If those would not be available y

[jira] [Resolved] (KAFKA-6615) Add scripts for DumpLogSegments

[ https://issues.apache.org/jira/browse/KAFKA-6615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-6615. Resolution: Fixed Fix Version/s: 1.2.0 > Add scripts for DumpLogSegments > --

Re: [ANNOUNCE] Apache Kafka 1.0.1 Released

On 6 March 2018 at 21:17, Ewen Cheslack-Postava wrote: > The Apache Kafka community is pleased to announce the release for Apache Kafka > 1.0.1. > > This is a bugfix release for the 1.0 branch that was first released with > 1.0.0 about 4 months ago. We've fixed 49 issues since that release. Most

Re: [VOTE] KIP-186: Increase offsets retention default to 7 days

+1 Thanks, Bill On Tue, Mar 6, 2018 at 2:27 PM, Matthias J. Sax wrote: > +1 (binding) > > On 3/6/18 10:43 AM, Vahid S Hashemian wrote: > > +1 (non-binding) > > > > Thanks Ewen. > > > > --Vahid > > > > > > > > From: Ewen Cheslack-Postava > > To: dev@kafka.apache.org > > Date: 03/05/2018

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

See Changes: [github] MINOR: Do not start processor for bounce-at-start (#4639) -- [...truncated 414.42 KB...] kafka.coordinator.transaction.TransactionCoordinatorTest >

Re: [ANNOUNCE] Apache Kafka 1.0.1 Released

Ewen, thanks for driving the release!! Guozhang On Tue, Mar 6, 2018 at 1:14 PM, Ewen Cheslack-Postava wrote: > The Apache Kafka community is pleased to announce the release for Apache > Kafka > 1.0.1. > > This is a bugfix release for the 1.0 branch that was first released with > 1.0.0 about 4

[ANNOUNCE] Apache Kafka 1.0.1 Released

The Apache Kafka community is pleased to announce the release for Apache Kafka 1.0.1. This is a bugfix release for the 1.0 branch that was first released with 1.0.0 about 4 months ago. We've fixed 49 issues since that release. Most of these are non-critical, but in aggregate these fixes will hav

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

See Changes: [github] MINOR: Do not start processor for bounce-at-start (#4639) -- [...truncated 416.53 KB...] kafka.tools.ConsoleConsumerTest > shouldParseValidNewConsum

Re: [VOTE] KIP-186: Increase offsets retention default to 7 days

+1 (binding) On 3/6/18 10:43 AM, Vahid S Hashemian wrote: > +1 (non-binding) > > Thanks Ewen. > > --Vahid > > > > From: Ewen Cheslack-Postava > To: dev@kafka.apache.org > Date: 03/05/2018 11:35 AM > Subject:[VOTE] KIP-186: Increase offsets retention default to 7 > days > >

Re: [VOTE] KIP-186: Increase offsets retention default to 7 days

+1 (non-binding) Thanks Ewen. --Vahid From: Ewen Cheslack-Postava To: dev@kafka.apache.org Date: 03/05/2018 11:35 AM Subject:[VOTE] KIP-186: Increase offsets retention default to 7 days I'd like to kick off voting for KIP-186: https://urldefense.proofpoint.com/v2/url?u=htt

Re: [DISCUSS] KIP-253: Support in-order message delivery with partition expansion

Hi everyone, Thanks for all the comments! It appears that everyone prefers linear hashing because it reduces the amount of state that needs to be moved between consumers (for stream processing). The KIP has been updated to use linear hashing. Regarding the migration endeavor: it seems that migrat

Re: [DISCUSSION] KIP-266: Add TimeoutException to KafkaConsumer#position()

bq. The most flexible option is to add overloads to the consumer This option is flexible. Looking at the tail of SPARK-18057, Spark dev voiced the same choice. +1 for adding overload with timeout parameter. Cheers On Mon, Mar 5, 2018 at 2:42 PM, Jason Gustafson wrote: > @Guozhang I probably

[jira] [Created] (KAFKA-6615) Add scripts for DumpLogSegments

Jason Gustafson created KAFKA-6615: -- Summary: Add scripts for DumpLogSegments Key: KAFKA-6615 URL: https://issues.apache.org/jira/browse/KAFKA-6615 Project: Kafka Issue Type: Improvement

[jira] [Created] (KAFKA-6614) kafka-streams to configure internal topics message.timestamp.type=CreateTime

Dmitry Vsekhvalnov created KAFKA-6614: - Summary: kafka-streams to configure internal topics message.timestamp.type=CreateTime Key: KAFKA-6614 URL: https://issues.apache.org/jira/browse/KAFKA-6614

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

See Changes: [jason] KAFKA-3806: Increase offsets retention default to 7 days (KIP-186) -- [...truncated 3.51 MB...] kafka.zookeeper.ZooKeeperClientTest > testPipelinedGet

Exposing additional metadata in Kafka Connect schema parameters

Hi, A user of the Debezium CDC Kafka Connect connectors has asked whether we could provide information about the original source type of captured table columns. Usually the type info we provide by using the Kafka Connect types and some custom semantic types is good enough. But there are some case

[VOTE] 1.1.0 RC1

Hello Kafka users, developers and client-developers, This is the second candidate for release of Apache Kafka 1.1.0. This is minor version release of Apache Kakfa. It Includes 29 new KIPs. Please see the release plan for more details: https://cwiki.apache.org/confluence/pages/viewpage.action?pag

Re: [DISCUSS] KIP-257 - Configurable Quota Management

Hi Rajini, I've read through your KIP and it looks good, I only have two things to clarify. 1. How do we detect removed partitions in updatePartitionMetadata? I'm presuming that the list here is the currently existing map of partitions, so if something is removed it can be calculated as the diff o