[STREAMPIPES-142] Handle non-primitive and primitive event data returned from Siddhi

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.67.0
• Component/s: Pipeline Elements
• Assignee: Patrick Wiener
• Reporter: Patrick Wiener
• Created: 25/May/20 17:38
• Updated: 26/Nov/22 12:54
• Resolved: 26/May/20 07:52

Description

Depending on the Siddhi query, events received from Siddhi either contain a non-primitive data structure, e.g. for the trend detection [1] it is a LinkedList,

Returned Siddhi event looks like this: 

Event{timestamp=1590427035172, data=[[24661], [10], [c], [1590427035166]], isExpired=false}

 or

contain a primitive data structure, e.g. for the numerical filter (siddhi) [2] as an Integer.

Returned Siddhi event looks like this:

Event{timestamp=1590427127153, data=[24753, 36, b, 1590427127149], isExpired=false}

 

Now, in the wrapper when trying to convert to a StreamPipes event in the 

toSpEvent(...)

method this fails due to casting error.

 

[1][Trend detection|https://github.com/apache/incubator-streampipes-extensions/blob/dev/streampipes-processors-filters-siddhi/src/main/java/org/apache/streampipes/processors/siddhi/trend/Trend.java]

[2][Numerical Filter (Siddhi)|https://github.com/apache/incubator-streampipes-extensions/blob/dev/streampipes-processors-filters-siddhi/src/main/java/org/apache/streampipes/processors/siddhi/filter/NumericalFilter.java]

 

Issue Links

• Blocked: STREAMPIPES-143 Numerical Filter in Siddhi not working