Re: [VOTE] #2 KIP-248: Create New ConfigCommand That Uses The New AdminClient

Hi All, I'd like to ask the community to please vote for this as the KIP freeze is tomorrow. Thank you very much, Viktor On Mon, May 21, 2018 at 9:39 AM, Viktor Somogyi wrote: > Hi Colin, > > Sure, I'll add a note. > Thanks for your vote. > > Viktor > > On Sat, May 19, 2018 at 1:01 AM, Colin Mc

Re: [VOTE] #2 KIP-248: Create New ConfigCommand That Uses The New AdminClient

Hi Colin, Sure, I'll add a note. Thanks for your vote. Viktor On Sat, May 19, 2018 at 1:01 AM, Colin McCabe wrote: > Hi Viktor, > > Thanks, this looks good. > > The boolean should default to false if not set, to ensure that existing > clients continue to work as-is, right? Might be good to ad

[jira] [Created] (KAFKA-6924) Making state store queryable on replicas

Navinder Brar created KAFKA-6924: Summary: Making state store queryable on replicas Key: KAFKA-6924 URL: https://issues.apache.org/jira/browse/KAFKA-6924 Project: Kafka Issue Type: New Featur

Re: [VOTE] KIP-255: OAuth Authentication via SASL/OAUTHBEARER

Hi Committers. One more binding affirmative vote is required if KIP 255 is to have a chance of being included in the 2.0.0 release. Please vote today. Ron > On May 18, 2018, at 9:27 PM, Ron Dagostino wrote: > > Hi committers. KIP 255 still needs 1 more binding vote. Currently there are >

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

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

[jira] [Created] (KAFKA-6923) Deprecate ExtendedSerializer/Serializer and ExtendedDeserializer/Deserializer

Ismael Juma created KAFKA-6923: -- Summary: Deprecate ExtendedSerializer/Serializer and ExtendedDeserializer/Deserializer Key: KAFKA-6923 URL: https://issues.apache.org/jira/browse/KAFKA-6923 Project: Kafk

Re: [DISCUSS] KIP-285: Connect Rest Extension Plugin

Hi Jason, Thanks a lot for your feedback. The health interface does provide the same information that's already exposed in the Connect Rest endpoints. Where it would be useful is if we need to infer certain kind of health status based on the connect and task status. One good example would be Livel

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

See Changes: [wangguoz] MINOR: Fix type inference on joins and aggregates (#5019) -- [...truncated 3.13 MB...] org.apache.kafka.common.config.ConfigDefTest > testInvalidD

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

See

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

See Changes: [github] KAFKA-6729: Follow up; disable logging for source KTable. (#5038) -- [...truncated 424.70 KB...] kafka.utils.json.JsonValueTest > testDecodeString ST

Jenkins build is back to normal : kafka-trunk-jdk10 #118

See

Re: [VOTE] #2 KIP-248: Create New ConfigCommand That Uses The New AdminClient

+1 (non-binding) On Fri, May 18, 2018 at 5:16 PM, Viktor Somogyi wrote: > Updated KIP-248: > https://cwiki.apache.org/confluence/display/KAFKA/KIP-248+-+Create+New+ > ConfigCommand+That+Uses+The+New+AdminClient > > I'd like to ask project members, committers and contributors to vote > as this wo

Re: [DISCUSS] KIP-290: Support for wildcard suffixed ACLs

Awesome last minute effort Piyush. Really appreciate your time and input, Andy Sent from my iPhone > On 19 May 2018, at 03:43, Piyush Vijay wrote: > > Updated the KIP. > > 1. New enum field 'ResourceNameType' in Resource and ResourceFilter classes. > 2. modify getAcls() and rely on ResourceN