aggregation is a common use case for us and never
thought to look to Guava for it.
Thanks!
On Fri, Dec 22, 2017 at 1:50 PM, Manish Sharma <mailto:maa...@gmail.com>> wrote:
We added a guava cache in the bolt's execute method to aggregate tuples and
wait for the tick signal
We added a guava cache in the bolt's execute method to aggregate
tuples and wait for the tick signal.
You can control the tick frequency with TOPOLOGY_TICK_TUPLE_FREQ_SECS
in the main topology.
This is a Spark use case IMO.
cheers, /Manish
On Wed, Dec 20, 2017 at 9:09 PM, Jinhua Luo wrote
We solved this offset sync issue by making our topology idempotent, (we
could do that with our use case)
our storm topology consumes documents from kafka and commits to
elasticsearch & inserting records to cassandra..
our topology can re-consume from beginning of the queue, and the docids and
prima
I am curious about your use case, Why are you running LocalCluster in
production?
You are missing out on distributed, high availability features when running
in cluster mode.
On Fri, Dec 8, 2017 at 2:37 PM, Mitchell Rathbun (BLOOMBERG/ 731 LEX) <
mrathb...@bloomberg.net> wrote:
> When running St
> .setProp(ConsumerConfig.VALUE_DESERIALIZER_CLASS_CONFIG,
> EmailObjectDeserializer.class)
>
> or
>
> .setProp(ConsumerConfig.VALUE_DESERIALIZER_CLASS_CONFIG, "com.example.
> EmailObjectDeserializer")
>
> that is, you need to use the fully qualified class name of the
>
Hello,
I am trying to use a custom ValueDeserializer when consuming from kafka, I
tried the following
--snip--
KafkaSpoutConfig kafkaSpoutConfig = KafkaSpoutConfig
.builder(property.getKafka_consumer_bootstrap_servers(), topics)
.setFirstPollOffsetStrategy(KafkaSpoutConfig.FirstPollOffsetStrategy