[
https://issues.jboss.org/browse/TEIID-5541?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-5541:
---------------------------------------
At least it breaks previous behavior.
Yes, that is another related case that needs addressed - we can use projection without
streaming, but we can't do streaming processing without projection. This case
wouldn't have been triggered before except in the case of a column path having
multiple context items, which unfortunately there wasn't a test for.
There's a new commit to correct this.
Incorrect parsing of xml with XmlTable
--------------------------------------
Key: TEIID-5541
URL:
https://issues.jboss.org/browse/TEIID-5541
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 11.1
Environment: teiid-11.1.0 (from 01.09.2018) on WildFly Full 11.0.0.Final (WildFly
Core 3.0.8.Final)
Reporter: dalex dalex
Assignee: Steven Hawkins
Priority: Blocker
Fix For: 11.0.3, 11.1.2, 12.0, 11.2.1
Running the query:
{code:sql}
Begin
Declare xml xcontent = '<root
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<report>
<data>
<year xsi:type="decimal">2018</year>
</data>
</report>
<waitSeconds xsi:type="decimal">13</waitSeconds>
</root>' ;
Select *
From
XmlTable(
XmlNamespaces ('http://www.w3.org/2001/XMLSchema-instance' as xsi),
'/root/report/data'
PASSING xcontent
Columns
"year" integer,
waitSeconds xml Path 'root()/root/waitSeconds',
waitSecondsStr string Path 'root()/root/waitSeconds'
)a ;
End ;;
{code}
and having a look at the structure we can see that the value 13 should be returned, while
the value is not picked from xml for result.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)