[
https://issues.jboss.org/browse/TEIID-5461?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-5461:
---------------------------------------
SQL Server has the same restriction as well. So we'll assume those in the Teiid
implementation. There are other hive/impala frame restrictions, such as requiring the
full between specification (handled by the translator) and eliminating additional frames
(such as current row to current row - which is not yet accounted for). SQL Server does
not allow range with n preceding/following, which we may do as well.
The initial commit for 11.2 is at
https://github.com/shawkins/teiid/commit/4ce82d4358709156d68948e0b22e2a69...
It is large for a back port, but does not introduce much in terms of complexity - and
should not be breaking in any way.
Add parsing and push down support for the frame clause
------------------------------------------------------
Key: TEIID-5461
URL:
https://issues.jboss.org/browse/TEIID-5461
Project: Teiid
Issue Type: Sub-task
Components: Connector API, Query Engine
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 11.2
To make it possible to introduce these changes into older branches, we should first
implement the parsing and push down logic - such that engine processing would initially
fail.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)