Hi Lasantha,
I try the same set of queries without distributed processing.
Now this query work fine:
*- queryB:*'from streamFlow#window.timeBatch( 5 sec ) select max(bytes) as
maxBytes, min(bytes) as minBytes, avg(bytes) as avgBytes, sum(bytes) as
sumBytes, src group by src insert into infoBytes'*
but this query doesn't work:
*- queryA:* 'from flow=streamFlow[bytes>250]+,
monitor=streamMonitor[monitor=="cpu" and value>25.00] within 10000 select
flow[0].src as src, monitor.value as cpu insert into streamD'*
I try explain you how I am using Siddhi within the TridentTopology. I am
using the Trident State API.
I put siddhiManager inside a Trident State, and I use this Trident State
across my topology, for example:
------------------------------- STORM
----------------------------|----------------- Siddhi ---------------
--> TridentStream( FLOW ) --> Trident State with Siddhi | ->
SiddhiStream(streamFlow) [Thread 1]
|
--> TridentStream( MONITOR ) --> Trident State with Siddhi | ->
SiddhiStream(streamMonitor) [Thread 2]
I need the distributed processing to make a communication between Thread1
and Thread2 [queryA].
I can have multiple parallelism in the same Trident State to do it scalable.
What do you think?
Thanks,
Andres
-----
--
Andres Gomez
Developer at Eneo Tecnologia.
Website: http://redborder.net
LinkedIn: http://lnkd.in/sHnbJe
--
View this message in context:
http://wso2-oxygen-tank.10903.n7.nabble.com/siddhi-v2-2-0-SNAPSHOT-stop-calling-callbacks-after-few-seconds-tp103254p103966.html
Sent from the WSO2 Development mailing list archive at Nabble.com.
_______________________________________________
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
