[teiid-designer-issues] [JBoss JIRA] (TEIIDDES-1207) Merge the relational and function metamodels
[
https://issues.jboss.org/browse/TEIIDDES-1207?page=com.atlassian.jira.plu...
]
Steven Hawkins commented on TEIIDDES-1207:
------------------------------------------
I'm not implying that the indexing logic needs to change. Having extension properties
in a separate index is not an issue. The runtime logic already associates all extension
metadata to their underlying records via a uuid lookup.
The indexing logic would only change if you update the metamodel, which would imply that
we're not using extension properties - at least for the basic function metadata.
Merge the relational and function metamodels
--------------------------------------------
Key: TEIIDDES-1207
URL: https://issues.jboss.org/browse/TEIIDDES-1207
Project: Teiid Designer
Issue Type: Quality Risk
Components: Modeling
Affects Versions: 8.0
Reporter: Steven Hawkins
Having the function and relational models is no longer necessary. We can add the needed
function metadata (including TEIIDDES-152 vararg support, null-on-null, etc.) through
either extension properties or a metamodel change. This is in the vain of PostgreSQL
which uses the create function syntax to add what would be procedures in other dbmses.
Virtual functions (procedures marked as functions in a view layer) could also still
specify transformation sql if pushdown is not required - rather than forcing the use of a
java class.
We could deprecate the old function model support of the Teiid side then.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira