[
https://issues.jboss.org/browse/TEIID-1801?page=com.atlassian.jira.plugin...
]
Mark Addleman commented on TEIID-1801:
--------------------------------------
Regarding the time window & re-runing: I don't particularly care if these options
are exposed to the client via a method or a query hint as long as the data is available to
the translator via the execution context. My gut feel is that a query hint is
conceptually better.
Regarding the result set caching: This issue seems dominated by internal Teiid
considerations. My only input is that the result sets are potentially large so keeping
the clause open may not a good solution. I'm perfectly comfortable with requiring a
hint to indicate that a cache should be used.
Async Event Processing: Reset and Re-run plan
----------------------------------------------
Key: TEIID-1801
URL:
https://issues.jboss.org/browse/TEIID-1801
Project: Teiid
Issue Type: Feature Request
Components: JDBC Driver, Query Engine
Reporter: Mark Addleman
Assignee: Steven Hawkins
Fix For: 8.0
In order to processing a stream of events aggregated within a specified time window, the
engine should provide some way of specifying the time period (analogous to a window),
reset and re-rerun the plan for every time period. There should also be an engine to
translator callback indicating that the plan has been reset as opposed to closed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira