storm-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From tai khuu <khuutan...@gmail.com>
Subject partitionPersist, function and stateQuery execution order
Date Thu, 05 Feb 2015 06:52:37 GMT
Hi guys,

I have always thought that when you call partionPersist, each and
stateQuery in sequential order the will be execute in the same order as you
call it given that there is no shuffle, parallelism hint, but today i
stumble upon a weird situation when partionPersist is run after other
function, given that it was called first

for example

{
inputStream.partitionerPersist
inputStream.each
}
the state will be update after other function is executed

I really don't understand the correct order of Trident Stream operation,
someone please help me on this.

Thanks

Mime
View raw message