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

See Changes: [wangguoz] MINOR: Stabilization fixes broker down test trunk (#6043) -- [...truncated 4.49 MB...] org.apache.kafka.connect.data.SchemaProjectorTest >

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

See

[jira] [Resolved] (KAFKA-6090) Upgrade the Scala recommendation to 2.12

[ https://issues.apache.org/jira/browse/KAFKA-6090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-6090. Resolution: Duplicate > Upgrade the Scala recommendation to 2.12 >

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

See Changes: [wangguoz] MINOR: Fixes for broker down test stability 2.1 (#6042) -- [...truncated 460.49 KB...] kafka.api.GroupAuthorizerIntegrationTest >

[jira] [Created] (KAFKA-7761) CLONE - Add broker configuration to set minimum value for segment.bytes and segment.ms

Chinmay Patil created KAFKA-7761: Summary: CLONE - Add broker configuration to set minimum value for segment.bytes and segment.ms Key: KAFKA-7761 URL: https://issues.apache.org/jira/browse/KAFKA-7761

[jira] [Created] (KAFKA-7760) Add broker configuration to set minimum value for segment.bytes and segment.ms

Badai Aqrandista created KAFKA-7760: --- Summary: Add broker configuration to set minimum value for segment.bytes and segment.ms Key: KAFKA-7760 URL: https://issues.apache.org/jira/browse/KAFKA-7760

Re: [DISCUSS] KIP-404: Add Kafka Connect configuration parameter for disabling WADL output on OPTIONS request

Randall, not sure about precedence but seemed to me that changing the already submitted KIP would be a nice way to document that a public (even by accident) feature is getting closed. But again, I don't feel too strong about this, so I'm fine with a simple PR instead. Konstantine. On Wed, Dec

[jira] [Resolved] (KAFKA-7715) Connect should have a parameter to disable WADL output for OPTIONS method

[ https://issues.apache.org/jira/browse/KAFKA-7715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleksandr Diachenko resolved KAFKA-7715. Resolution: Won't Fix Related KIP(KIP-404) was discarded, reported a bug - 

Re: [DISCUSS] KIP-404: Add Kafka Connect configuration parameter for disabling WADL output on OPTIONS request

Thanks for the feedback. At this point, it seems like the issue should be addressed as a bug, and this KIP is not relevant anymore. I will mark this KIP as discarded, create a ticket and proceed with a PR. Regards, Alex. On Tue, Dec 18, 2018 at 2:36 PM Randall Hauch wrote: > Konstatine,

[jira] [Created] (KAFKA-7759) Disable WADL output on OPTIONS method in Connect REST

Oleksandr Diachenko created KAFKA-7759: -- Summary: Disable WADL output on OPTIONS method in Connect REST Key: KAFKA-7759 URL: https://issues.apache.org/jira/browse/KAFKA-7759 Project: Kafka

Re: [DISCUSS] KIP-382: MirrorMaker 2.0

Becket, thanks for taking a look. > 1. Only relying on the topic naming seems a little fragile. I think the limitations on topic names are imposed by Kafka itself (beyond those from Zookeeper and the file system), so it might be possible to add a reserved character for this purpose. This would

[jira] [Created] (KAFKA-7758) When Naming a Repartition Topic with Aggregations Reuse Repartition Graph Node for Multiple Operations

Bill Bejeck created KAFKA-7758: -- Summary: When Naming a Repartition Topic with Aggregations Reuse Repartition Graph Node for Multiple Operations Key: KAFKA-7758 URL: https://issues.apache.org/jira/browse/KAFKA-7758

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

Looking back the email thread I think one of the comments from Mayuresh was the question about needing KIP for this change or not as the KafkaConsumer does not guarantee the end user any order, and so no changes to the contracts to users. I entered KIP based on suggestions from the attached

[jira] [Created] (KAFKA-7757) Too many open files after java.io.IOException: Connection to n was disconnected before the response was read

Pedro Gontijo created KAFKA-7757: Summary: Too many open files after java.io.IOException: Connection to n was disconnected before the response was read Key: KAFKA-7757 URL:

[jira] [Resolved] (KAFKA-7683) Support ConfigDef.Type.MAP

[ https://issues.apache.org/jira/browse/KAFKA-7683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Czajka resolved KAFKA-7683. Resolution: Information Provided Alternate solution already exists, this is a non-issue. >

Re: transaction 2PC protocol

Hi, There is a design document for transaction support linked at the bottom of KIP-98 that you can read here https://docs.google.com/document/d/11Jqy_GjUGtdXJK94XGsEIK7CP1SnQGdp2eF0wSw9ra8 . That describes some of the recovery/retry mechanisms. The design relies on partition availability to

Re: transaction 2PC protocol

Hi, thanks for the answer, it was helpful. So, if there are several topic-partitions in a transaction, the reads are eventually consistent; it is possible some message from that transaction are not available yet, until some recovery/retry mechanism is completed for the fail topic-partitions?

Re: transaction 2PC protocol

Hi, This is very similar to traditional two-phase commit. There are essentially multiple logs being used - one per TopicPartition involved and the overall transaction log. At the point where COMMIT is being written to the TopicPartitions, it is assumed that it will be possible to write all of

RE: [VOTE] [REMINDER] KIP-383 Pluggable interface for SSL Factory

I did that and nobody came. https://lists.apache.org/list.html?dev@kafka.apache.org:lte=1M:kip-383 I don't understand why this feature is not more popular. It's the solution to one Jira and a work-around for a handful more Jiras. -Original Message- From: Damian Guy

Re: [VOTE] [REMINDER] KIP-383 Pluggable interface for SSL Factory

Hi Clement, You should start a separate thread for the vote, i.e., one with a subject of [VOTE] KIP-383 ... Looks like you haven't done this? On Tue, 18 Dec 2018 at 17:33, Harsha wrote: > Yes. +1 binding. > > Thanks, > Harsha > > On Mon, Dec 17, 2018, at 5:21 AM, Pellerin, Clement wrote: > >

Re: Vote for KIP-393 (Fix time windowed serde to deserialize changelog topic)

Sorry for the delay. Needed to read the KIP and code multiple times to wrap my head around it. Thanks for the KIP. +1 (binding) -Matthias On 12/13/18 1:19 PM, Damian Guy wrote: > +1 (binding) > > On Wed, 12 Dec 2018 at 13:27, Adam Bellemare > wrote: > >> +1 (non-binding) from me. Looks

[jira] [Created] (KAFKA-7756) Leader: -1 after topic delete

zhws created KAFKA-7756: --- Summary: Leader: -1 after topic delete Key: KAFKA-7756 URL: https://issues.apache.org/jira/browse/KAFKA-7756 Project: Kafka Issue Type: Bug Reporter: zhws