[JBoss JIRA] (TEIID-2345) source hints are not honoured for nested sqls
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2345?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-2345.
---------------------------------
> source hints are not honoured for nested sqls
> ---------------------------------------------
>
> Key: TEIID-2345
> URL: https://issues.jboss.org/browse/TEIID-2345
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 8.1
> Reporter: Vineela Gampa
> Assignee: Steven Hawkins
>
> Hi
> I want to use general hints below. I observed i was able to put my sourcehint as below which yields generalhint information to data_window procedure. As per this document https://docs.jboss.org/author/display/TEIID/Query+Plans if i use KEEP_ALIASES general hint is available for all nested queries but i was not able to get it working
> SELECT /*+ sh[KEEP ALIASES]:'foo' bar:'leading' */ \r\n" when i use something like this general hint is null in all the executions.
> If i use below general hint is available only to the first execution.
> "SELECT /*+ sh:'foo' bar:'leading' */ \r\n"
> + " chorus_results.* \r\n"
> + "FROM (\r\n"
> + " EXEC data_window('select pkey, counter from testing.bigtable WHERE pkey=? LIMIT 300', ?)\r\n"
> + ") AS chorus_data_window, ARRAYTABLE(chorus_data_window.tuple COLUMNS pkey long, counter long) AS chorus_results LIMIT 0, 20",
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months
[JBoss JIRA] (TEIID-2354) Inherent insert using WHERE partitioning is incomplete
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2354?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-2354.
---------------------------------
> Inherent insert using WHERE partitioning is incomplete
> ------------------------------------------------------
>
> Key: TEIID-2354
> URL: https://issues.jboss.org/browse/TEIID-2354
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 7.7
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.3
>
>
> Using a metadata structure such as:
> create foreign table b (custid integer, field1 varchar) options updatable true)
> create view c options (updatable true) as select * from b where custid = 1 union all select * from b where custid = 2;
> will fail to process INSERT into c (custid, field1) values (1, 'foo')
> because a null value will be inserted into be for the custid field. The logic is treating the WHERE partitioning as if it were projected literals from the SELECT cause inappropriately.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months