atom feed8 messages in[esper-dev] [jira] Updated: (ESPER-21...
FromSent OnAttachments
Thomas Bernhardt (JIRA)Mar 28, 2008 10:00 am 
Thomas Bernhardt (JIRA)Apr 22, 2008 9:10 am 
Thomas Bernhardt (JIRA)Oct 20, 2008 11:44 am 
Thomas Bernhardt (JIRA)Jan 2, 2009 9:20 am 
Thomas Bernhardt (JIRA)Jan 2, 2009 9:22 am 
Thomas Bernhardt (JIRA)Sep 17, 2009 4:31 am 
Thomas Bernhardt (JIRA)Sep 17, 2009 4:31 am 
Thomas Bernhardt (JIRA)Sep 17, 2009 4:31 am 
Subject:[esper-dev] [jira] Updated: (ESPER-217) Allow expressions as view parameters
From:Thomas Bernhardt (JIRA) (
Date:Oct 20, 2008 11:44:20 am


Thomas Bernhardt updated ESPER-217:

Fix Version/s: (was: 2.3) 3.0

Allow expressions as view parameters


Key: ESPER-217 URL: Project: Esper Issue Type: New Feature Components: Core Affects Versions: 2.0 Reporter: Thomas Bernhardt Fix For: 3.0

Is it possible to easily drive an ext_timed window where the timestamp property is the result of an XPath property? XPath properties can return STRING, NUMBER, or BOOLEAN - NUMBER translates to Double but the window requires a long-typed milliseconds value. What I found is that even after I converted to milliseconds, the window specification accepts only a property name, not an expression, so I can't give it cast(timestamp, long). It won't truncate the Double. So I had to do insert into TempEvent select property1, property2, cast(timestamp, long) as timestamp from EventType select property1, property2, timestamp from, 10 sec) which works but requires me to generate an intermediate map event for each event that comes through the system. This is doable, and perhaps encouraged if I have many rules driven by XPath properties, but it feels like it should be avoidable, either by allowing an expression as the first argument to ext_timed, by some truncation logic, or by allowing XPath expressions to be cast to longs on their way out, etc.