dalex dalex created TEIID-5133: ---------------------------------- Summary: XmlTable path language is not always identical to XPathValue expressions Key: TEIID-5133 URL: https://issues.jboss.org/browse/TEIID-5133 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 9.3.4 Environment: eiid-9.3.4 on WildFly Full 10.0.0.Final (WildFly Core 2.0.10.Final) Reporter: dalex dalex Assignee: Steven Hawkins The same Path value, used in XPathValue and XmlTable->Path brings different results. That is for the following query: {code:sql} Select * From (select '<root> <item> <id>id1</id> <val>val1</val> </item> </root>' as resp) w, XMLTABLE( '/root' passing XMLPARSE(document w.resp) columns valOption2 string PATH 'item[id = "id1"]/val' --,valOption1 string PATH 'item[id/text() = "id1"]/val' ) x;; {code} returned value for "valOption2" will be changed from "val1" to "null" that is incorrect and unexpected behavior. Using "node/text()" in Path expressions may result in side effects. -- This message was sent by Atlassian JIRA (v7.5.0#75005)