ult to the next bolt is never done, the "combine" is called but no
tuples get out of the persistentAggregate.
Like I said at the beginning if I build the first topology (without
the join) the aggregation is done as expected.
Is someone have an idear ?
I probably can extract a simple test case if necessary.
Any help whould be appreciated,
Michel Hummel
n();
==
As you can see in the output (below), the aggregated tuples as well
as the joined tuples are printed (11) (J) :
DEBUG(1): [the cow jumped over the moon]
DEBUG(11): [over, 1]
DEBUG(2): [the, 2]
DEBUG(2): [cow, 1]
DEBUG(2): [jumped, 1]
DEBUG(2): [over, 1]
DEBUG(
ologies coupled with kafka.
Don't hesitate to contact me directly if you wan't more informations.
Michel Hummel
2017-03-02 22:56 GMT+01:00 Alexandre Vermeerbergen :
> Hello,
>
> I was wondering if there's some recommended mailing-list/site for posting a
> job opportuni
After some digging I finaly found a workaround (a pullrequest is
pending to fix the issue in storm).
Using a simple trick in the start method of the worker-hook (rewind of
the byteBuffer to allow the deserialization on stop)it can work as
expected, here is a simple example if someone encounter the
Hi look at the pull request https://github.com/apache/storm/issues/2591 .
The issue seems To be in all the current versions. You Will also find a
workaround in the comments of the pullrequest.
Le mer. 28 mars 2018 à 23:57, Mitchell Rathbun (BLOOMBERG/ 731 LEX) <
mrathb...@bloomberg.net> a écrit :
Le ven. 30 mars 2018 à 17:01, Jude Huang Zhipeng a
écrit :
> Hi Storm Community,
>
> Is there anybody has the experience integrate Prometheus with Storm? Is
> this a drawback to use twitter heron instead of Storm? Thanks in advance!
>
> Regards,
> Jude
>
>
I think that the issue also exists in cluster mode. did you test it ?
Le lun. 9 avr. 2018 à 21:50, Mitchell Rathbun (BLOOMBERG/ 731 LEX) <
mrathb...@bloomberg.net> a écrit :
> Just so I understand this correctly, the WorkerHook is created and then
> serialized. It is then deserialized two separat
that's the purpose of my pull request. the workerhook will now be statefull
compatible
Le lun. 9 avr. 2018 à 23:53, Mitchell Rathbun (BLOOMBERG/ 731 LEX) <
mrathb...@bloomberg.net> a écrit :
> Yeah you are right. So given that the WorkerHook is deserialized twice, I
> am wondering what the reason
