[
https://issues.jboss.org/browse/TEIID-1615?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-1615:
---------------------------------------
updated the xml resolving logic so that you can issue document queries that have
"context(x, y) in (select elem from doc.path)". Without that change you would
be forced to use "context(x, y) in (select col from mappingclass)"
This new resolving logic does have some catches though, as we expect the mapping class
partial name to appear in each relevant document path as doc.[elem...].<mc
name>.<elem or attribute name>. If the document path does not match that form,
then we cannot create a proper table/column representation.
Add features to support relate planning
---------------------------------------
Key: TEIID-1615
URL:
https://issues.jboss.org/browse/TEIID-1615
Project: Teiid
Issue Type: Feature Request
Components: Query Engine
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 7.4.1
MetaMatrix had an xml relate planner feature that can be reproduced with standard xml
processing with additional features.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira