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

See Changes: [cshapi] MINOR: add MacOS requirement to Streams docs -- [...truncated 4.68 MB...] org.apache.kafka.streams.test.OutputVerifierTest >

Re: [VOTE] KIP-349 Priorities for Source Topics

On 2019/01/28 02:26:31, n...@afshartous.com wrote: > Hi Sönke, > > Thanks for taking the time to review. I’ve put KIP-349 into hibernation. > > Thanks also to everyone who participated in the discussion. > > Best regards, > -- > Nick > > > On Jan 25, 2019, at 5:51 AM, Sönke Liebau

Re: [DISCUSSION] KIP-418: A method-chaining way to branch KStream

Ivan, I think it's a great idea to improve this API, but I find the onTopOff() mechanism a little confusing since it contrasts the fluency of other KStream method calls. Ideally I'd like to just call a method on the stream so it still reads top to bottom if the branch cases are defined fluently.

Re: [DISCUSS] KIP-401 TransformerSupplier/ProcessorSupplier enhancements

I'd like to resurrect this discussion with a cursory, proof-of-concept implementation of the KIP which combines many of our ideas: https://github.com/apache/kafka/pull/6496. I tried to keep the diff as small as possible for now, just using it to convey the main ideas. But I'll separately address

[jira] [Created] (KAFKA-8152) Offline partition state not propagated by controller

Jason Gustafson created KAFKA-8152: -- Summary: Offline partition state not propagated by controller Key: KAFKA-8152 URL: https://issues.apache.org/jira/browse/KAFKA-8152 Project: Kafka Issue

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

See Changes: [github] MINOR: fix message protocol help text for ElectPreferredLeadersResult -- [...truncated 2.34 MB...] kafka.cluster.BrokerEndPointTest >

Re: [DISCUSSION] KIP-418: A method-chaining way to branch KStream

Hi Bill, Thank you for your reply! This is how I usually do it: void handleFirstCase(KStream ks){ ks.filter().mapValues(...) } void handleSecondCase(KStream ks){ ks.selectKey(...).groupByKey()... } .. new KafkaStreamsBrancher() .addBranch(predicate1,

Re: [DISCUSS] KIP-236 Interruptible Partition Reassignment

Thanks for the KIP, making reassignment more flexible is definitely welcome. As others have mentioned, I think we need to do it via the Kafka protocol and not via ZK. The latter introduces an implicit API that other tools will depend on causing migration challenges. This has already happened with

Re: [Vote] KIP-421: Support resolving externalized secrets in AbstractConfig

I'm not sure if this is ready for a vote yet. In particular, I don't understand how it will work in the broker. Having external secrets in the broker is something that a lot of people have been asking for -- it seems like a big omission to not talk about it at all in this KIP. I also don't

Re: [DISCUSS] KIP-236 Interruptible Partition Reassignment

On Thu, Mar 21, 2019, at 20:51, George Li wrote: > Hi Colin, > > I agree with your proposal of having administrative APIs through RPC > instead of ZooKeeper. But seems like it will incur significant changes > to both submitting reassignments and this KIP's cancelling pending > reassignments. 

[jira] [Created] (KAFKA-8151) Broker hangs and lockups after Zookeeper outages

Joe Ammann created KAFKA-8151: - Summary: Broker hangs and lockups after Zookeeper outages Key: KAFKA-8151 URL: https://issues.apache.org/jira/browse/KAFKA-8151 Project: Kafka Issue Type: Bug