[
https://issues.jboss.org/browse/TEIID-2083?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-2083:
---------------------------------------
Ramesh, there are a couple of things that we could do. What is stubbed in right now is a
UDT option clause option, where the name value pair is UDT=typename(length, precision,
scale) and the runtime type is used for the actual type declaration. That is consistent
with the current parser implementation.
If we add handling for that option, then we would be able to override the runtime type
with the given built-in/enterprise type. Assuming that the type is known - which it
should be in the case of built-in types.
The other route is to change the parser to allow for any identifier as the type name. As
you are indicating a new keyword may be needed in the latter case since there are
conflicts between the built-in type names and the runtime type name (the built-in type
integer != our 4 byte integer) since the built-in types are coming from xsd types.
The other part of this is that sense the enterprise types are not in any schema and we
lack a DDL form, there isn't a method for getting enterprise type definitions (which
are typically only used in xml scenarios though). We could add another method such as
getDatatypes or implicitly scope the datatypes to the SYS schema and add them as a
SchemaObjectType. Either way we'd still have to define the DDL for retrieving them.
Provide a Admin method to read the metadata of a VDB
----------------------------------------------------
Key: TEIID-2083
URL:
https://issues.jboss.org/browse/TEIID-2083
Project: Teiid
Issue Type: Feature Request
Components: AdminApi
Reporter: Ramesh Reddy
Assignee: Ramesh Reddy
Fix For: 8.1
Define a method on Admin API to expose the metadata of VDB. With the increased usage of
the Dynamic VDB and dynamic metadata exposed from the sources and creation of views using
DDL, currently there is no way to read the metadata of the VDB. Using JDBC, DatabaseMetata
can be used to read schema, however this would be limited in functionality as it will not
expose the extension metadata or transformation information in the cases of views.
There two possible ways we can expose
1) Expose the Metadata API, through Admin API. This seems good, however using CLI based
tools it is hard to expose binary contents.
2) Expose as DDL.
This method can be used with tooling, to design a importer that uses a runtime server to
read the metadata instead of building a custom importer for every source.
--
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