[teiid-issues] [JBoss JIRA] (TEIID-1598) translator scoped result set caching

[Mark Addleman (Commented) (JIRA)]

    [ https://issues.jboss.org/browse/TEIID-1598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12639495#comment-12639495 ] 

Mark Addleman commented on TEIID-1598:
--------------------------------------

Thinking about this issue and the streaming events:  I can easily imagine streaming queries that join with non-streamable result sets.  For example, suppose I want a stream of temperature readings by city but I have a set of weather stations that report temperature by station ID and, separately, I have a mapping table of station ID to city.

It is possible that the data source supplying the mapping table is slow, so I would want to cache those results for the life of the query stream (something like read consistency).  I suppose one solution would be to provide a materialized view of the mapping table.  Alternatively, the query (or translator) could indicate that the result set is cachable for the life of query and Teiid could automaticaly set up sort of a private materialized view.  

Again, I consider this capability low priority.
                
> translator scoped result set caching
> ------------------------------------
>
>                 Key: TEIID-1598
>                 URL: https://issues.jboss.org/browse/TEIID-1598
>             Project: Teiid
>          Issue Type: Feature Request
>            Reporter: Mark Addleman
>            Assignee: Steven Hawkins
>            Priority: Minor
>
> Something Steven mentioned in Teiid-1589 got me thinking:  It would be helpful for individual translators to request that Teiid cache results sets that match the query as presented to the execution factory (after the planner is done rewriting the query based on the translator's capabilities).
> I envision a new method on an Execution getCacheTtlMs() where zero or negative indicates that Teiid shouldn't cache the results.

--
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