Using Kafka as Primary Datastore without compaction

Hi There, I am currently reading the Kafka Definitive guide book as we wanted to Architect an application using Kafka as the primary data store. In the Log Compaction section you have mentioned the dirty records are compacted with leaving just the latest records in the topic. Actually the

Re: [DISCUSS]KIP-216: IQ should throw different exceptions for different errors

Sorry to hear! Get well soon! It's not a big deal if the KIP stalls a little bit. Feel free to pick it up again when you find time. >>> Is `StreamThreadNotRunningException` really an retryable error? >> >> When KafkaStream state is REBALANCING, I think it is a retryable error. >> >>

Re: [VOTE] KIP-313: Add KStream.flatTransform and KStream.flatTransformValues

+1 (binding) -Matthias On 6/22/18 10:25 AM, Bill Bejeck wrote: > Thanks for the KIP, +1. > > -Bill > > On Fri, Jun 22, 2018 at 1:08 PM Ted Yu wrote: > >> +1 >> >> On Fri, Jun 22, 2018 at 2:50 AM, Bruno Cadonna wrote: >> >>> Hi list, >>> >>> I would like to voting on this KIP. >>> >>> I

Re: [DISCUSS] KIP-319: Replace segments with segmentSize in WindowBytesStoreSupplier

Thanks for the KIP. Overall, I think it makes sense to clean up the API. Couple of comments: > Sadly there's no way to "deprecate" this > exposure I disagree. We can just mark the variable as deprecated and I advocate to do this. When the deprecation period passed, we can make it private (or

Re: [Discuss] KIP-321: Add method to get TopicNameExtractor in TopologyDescription

Thanks for the KIP! I am don't have any further comments. For Guozhang's comment: if we mention anything about `toString()`, we should make explicit that `toString()` output is still not public contract and users should not rely on the output. Furhtermore, for the actual uses output, I would

[jira] [Created] (KAFKA-7093) Kafka warn messages after upgrade from 0.11.0.1 to 1.1.0

Suleyman created KAFKA-7093: --- Summary: Kafka warn messages after upgrade from 0.11.0.1 to 1.1.0 Key: KAFKA-7093 URL: https://issues.apache.org/jira/browse/KAFKA-7093 Project: Kafka Issue Type: New

Re: [DISCUSS] KIP-291: Have separate queues for control requests and data requests

Hi Lucas,              One more question, any thoughts on making this configurable and also allowing subset of data requests to be prioritized. For example ,we notice in our cluster when we take out a broker and bring new one it will try to become follower and have lot of fetch requests to

[jira] [Created] (KAFKA-7092) Multiple topics (including __consumer_offsets) have not been cleaned for a few months

Noam Berman created KAFKA-7092: -- Summary: Multiple topics (including __consumer_offsets) have not been cleaned for a few months Key: KAFKA-7092 URL: https://issues.apache.org/jira/browse/KAFKA-7092