[jira] [Resolved] (KAFKA-7702) Prefixed ACLs don't work with single character prefix

2018-12-04 Thread Rajini Sivaram (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-7702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram resolved KAFKA-7702. --- Resolution: Fixed Reviewer: Jun Rao > Prefixed ACLs don't work with single character

Jenkins build is back to normal : kafka-2.1-jdk8 #69

2018-12-04 Thread Apache Jenkins Server
See

Re: [VOTE] KIP-345: Introduce static membership protocol to reduce consumer rebalances

2018-12-04 Thread Boyang Chen
Thanks Guozhang for confirming!Let‘s move followup back to the discussion thread. Would appreciate a +1 from you when you feel this is ready :) Get Outlook for iOS From: Guozhang Wang Sent: Tuesday, December 4, 2018 7:21:41 AM To: dev

Re: [VOTE] KIP-345: Introduce static membership protocol to reduce consumer rebalances

2018-12-04 Thread Patrick Williams
Pls take me off this VOTE list Best, Patrick Williams Sales Manager, UK & Ireland, Nordics & Israel StorageOS +44 (0)7549 676279 patrick.willi...@storageos.com 20 Midtown 20 Proctor Street Holborn London WC1V 6NX Twitter: @patch37 LinkedIn: linkedin.com/in/patrickwilliams4

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

2018-12-04 Thread Apache Jenkins Server
See Changes: [rajinisivaram] KAFKA-7702: Fix matching of prefixed ACLs to match single char prefix -- [...truncated 436.70 KB...] kafka.zk.ReassignPartitionsZNodeTest >

[jira] [Resolved] (KAFKA-7696) kafka-delegation-tokens.sh using a config file that contains security.protocol=SASL_PLAINTEXT throws OutOfMemoryError if it tries to connect to an SSL-enabled secured br

2018-12-04 Thread Attila Sasvari (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-7696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Attila Sasvari resolved KAFKA-7696. --- Resolution: Duplicate > kafka-delegation-tokens.sh using a config file that contains >

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

2018-12-04 Thread Apache Jenkins Server
See Changes: [github] KAFKA-7702: Fix matching of prefixed ACLs to match single char prefix -- [...truncated 2.24 MB...] org.apache.kafka.streams.test.OutputVerifierTest

Re: [Discuss] KIP-389: Enforce group.max.size to cap member metadata growth

2018-12-04 Thread Patrick Williams
Please take me off this Discuss list Best, Patrick Williams Sales Manager, UK & Ireland, Nordics & Israel StorageOS +44 (0)7549 676279 patrick.willi...@storageos.com 20 Midtown 20 Proctor Street Holborn London WC1V 6NX Twitter: @patch37 LinkedIn: linkedin.com/in/patrickwilliams4

Re: [jira] [Created] (KAFKA-7699) Improve wall-clock time punctuations

2018-12-04 Thread Patrick Williams
Please take me off this JIRA list Best, Patrick Williams Sales Manager, UK & Ireland, Nordics & Israel StorageOS +44 (0)7549 676279 patrick.willi...@storageos.com 20 Midtown 20 Proctor Street Holborn London WC1V 6NX Twitter: @patch37 LinkedIn: linkedin.com/in/patrickwilliams4

[jira] [Resolved] (KAFKA-7687) Print batch level information in DumpLogSegments when deep iterating

2018-12-04 Thread Jason Gustafson (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-7687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-7687. Resolution: Fixed Fix Version/s: 2.2.0 > Print batch level information in

Re: KAFKA-6144(or other ticket to resolve)

2018-12-04 Thread Matthias J. Sax
Thanks Nikolay, of course we would like to get this ticket resolved! Just a heads up: it's a complex beast and we need to lay out a sound design. Thus, I expect a long KIP discussion. If this does (hopefully) not scare you, feel free to pick it up. Also note, related

Re: KAFKA-6144(or other ticket to resolve)

2018-12-04 Thread Nikolay Izhikov
Hello, Matthias. > it's a complex beast and we need to lay out a sound design. Thats, what I looking for :) > If this does (hopefully) not scare you, feel free to pick it up. Yes, I want to pick it up. After, KAFKA-7420 which is almost done and KAFKA-6970 I start working on this ticket. >

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

2018-12-04 Thread ChienHsing Wu
Hi, Any comments/updates? I am not sure the next steps if no one has any further comments. Thanks, CH -Original Message- From: ChienHsing Wu Sent: Tuesday, November 20, 2018 2:46 PM To: dev@kafka.apache.org Subject: RE: [EXTERNAL] - Re: [DISCUSS] KIP-387: Fair Message Consumption

Re: [VOTE] KIP-345: Introduce static membership protocol to reduce consumer rebalances

2018-12-04 Thread Mike Freyberger
+1 (non binding) On 12/4/18, 9:43 AM, "Patrick Williams" wrote: Pls take me off this VOTE list Best, Patrick Williams Sales Manager, UK & Ireland, Nordics & Israel StorageOS +44 (0)7549 676279 patrick.willi...@storageos.com 20 Midtown

Re: KIP-213 - Scalable/Usable Foreign-Key KTable joins - Rebooted.

2018-12-04 Thread Adam Bellemare
Hi John Thanks for your feedback and assistance. I think your summary is accurate from my perspective. Additionally, I would like to add that there is a risk of inconsistent final states without performing the resolution. This is a major concern for me as most of the data I have dealt with is

Re: [DISCUSS] KIP-382: MirrorMaker 2.0

2018-12-04 Thread Sönke Liebau
Hi Ryanne, thanks for your response! It seems like you have already done a lot of investigation into the existing code and the solution design and all of what you write makes sense to me. Would it potentially be worth adding this to the KIP, now that you had to write it up because of me anyway?

Re: [DISCUSS] KIP-398: Support reading trust store from classpath

2018-12-04 Thread Sönke Liebau
Hi Neo, thanks for the KIP, the proposal sounds useful! Also I agree on both assumptions that you made: - users whose current truststore location starts with classpath: should be very few and extremely far between (and arguably made questionable choices when naming their files/directories), I

Re: KIP-213 - Scalable/Usable Foreign-Key KTable joins - Rebooted.

2018-12-04 Thread Adam Bellemare
Hi Guozhang and Matthias I know both of you are quite busy, but we've gotten this KIP to a point where we need more guidance on the API (perhaps a bit of a tie-breaker, if you will). If you have anyone else you may think should look at this, please tag them accordingly. The scenario is as such:

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

2018-12-04 Thread Apache Jenkins Server
See

Re: [Discuss] KIP-389: Enforce group.max.size to cap member metadata growth

2018-12-04 Thread Boyang Chen
Hey Stanislav, I read the latest KIP and saw that we already changed the default value to -1. Do we still need to take care of the consumer group shrinking when doing the upgrade? However this is an interesting topic that worth discussing. Although rolling upgrade is fine,

Re: [VOTE] KIP-354 Time-based log compaction policy

2018-12-04 Thread Colin McCabe
Hi Xiongqi, Thinking about this a little bit more, it seems like we don't have any guarantees just by looking at the timestamp of the first message in a log segment. Similarly, we don't have any guarantees just by looking at the maxTimestamp of the previous log segment. Old data could appear

Kafka Summit NYC and London in 2019

2018-12-04 Thread Jun Rao
Hi, Everyone, We have two upcoming Kafka Summits, one in NYC and another in London. The deadline for summiting proposals is Dec 20 for both events. Please consider submitting a proposal if you are interested. The Links to submit abstracts are Kafka Summit NYC -

Re: [VOTE] KIP-354 Time-based log compaction policy

2018-12-04 Thread xiongqi wu
Colin, Thanks for comments. Out of ordered message timestamp is a very good point. We can combine max.compaction.lag.ms with log.message.timestamp.difference.max.ms to achieve what we want in an environment that message timestamp can be shifted a lot. There are similar discussions regarding

Re: [VOTE] KIP-354 Time-based log compaction policy

2018-12-04 Thread xiongqi (wesley) wu
Colin, Thanks for comments. Out of ordered message timestamp is a very good point. We can combine max.compaction.lag.ms with log.message.timestamp.difference.max.ms to achieve what we want in an environment that message timestamp can be shifted a lot. There are similar discussions regarding

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

2018-12-04 Thread Apache Jenkins Server
See Changes: [wangguoz] MINOR: Improve GlobalKTable docs (#5996) -- [...truncated 2.24 MB...] org.apache.kafka.streams.test.OutputVerifierTest >

Re: [DISCUSS] KIP-382: MirrorMaker 2.0

2018-12-04 Thread Ryanne Dolan
Sönke, I think so long as we can keep the differences at a very high level (i.e. the "control plane"), there is little downside to MM2 and Connect coexisting. I do expect them to converge to some extent, with features from MM2 being pulled into Connect whenever this is possible without breaking

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

2018-12-04 Thread Apache Jenkins Server
See