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

[Ramesh Reddy (JIRA)]

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

Ramesh Reddy resolved TEIID-2083.
---------------------------------

    Resolution: Done


Took the easier option to parse the UDT option.

Adding the parser code to recognize the UDT option on the column. If this option is found then the datatype will be replaced with supported user defined designer's index type. Also the length, and precision and scale captured on the column.

Should consider the support of enterprise types when the data type framework is re-worked.
                
> 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