[teiid-issues] [JBoss JIRA] (TEIID-2079) Coordinate closing continuous executions across windows and data sources

[Steven Hawkins (Jira)]

     [ https://issues.jboss.org/browse/TEIID-2079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steven Hawkins resolved TEIID-2079.
-----------------------------------
    Resolution: Out of Date


> Coordinate closing continuous executions across windows and data sources
> ------------------------------------------------------------------------
>
>                 Key: TEIID-2079
>                 URL: https://issues.jboss.org/browse/TEIID-2079
>             Project: Teiid
>          Issue Type: Feature Request
>          Components: Query Engine
>            Reporter: Mark Addleman
>            Assignee: Steven Hawkins
>            Priority: Major
>
> From discussion https://community.jboss.org/thread/201379?tstart=0
> In a continuous execution involving more than one data source, it is possible that one or more data sources will reach end of data with no possibility of more results.  The translator API should allow for signalling this to the query engine.  Further for the query engine ought to extend non-continuous  end of result set processing semantics to the continuous execution case as much as possible.
> Below is a stab at what the continuous execution end of result set semantics might be.
> There are two cases:  correlated results across data sources and non-correlated results.
> In the correlated case (such as an inner join), when one data source indicates end of results, the execution ends for all correlated data sources.
> In the uncorrelated case (such as a union), any data source that signals end of results is not dropped from the plan on the next window and its resources are cleaned up.
> In both cases when all data source executions end, the client should be notified through a callback mechanism.



--
This message was sent by Atlassian Jira
(v7.12.1#712002)