[teiid-issues] [JBoss JIRA] (TEIID-2083) Provide a Admin method to read the metadata of a VDB

[Steven Hawkins (JIRA)]

     [ https://issues.jboss.org/browse/TEIID-2083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steven Hawkins reopened TEIID-2083:
-----------------------------------



various issues were resolved with TEIID-2103, but non-runtime type handling is still an issue.  for now when a non-runtime type (marked as Basic in the metadata) is used we use the runtime type as the type name and add a custom UDT property with the datatype name, length, precision, and scale.

At the very least the parser needs support for that, which would get us to all known designer built-in types.  However any enterprise types would still be an issue.  Right now datatypes are not schema scoped entries and do not have export sql, so there's no export of the enterprise type information.
                
> 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