[teiid-issues] [JBoss JIRA] (TEIID-2103) Replace System VDB with DDL based metadata

Mon Jul 16 21:17:06 EDT 2012

    [ https://issues.jboss.org/browse/TEIID-2103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12706258#comment-12706258 ] 

Steven Hawkins commented on TEIID-2103:
---------------------------------------

Updated the parsing logic so that procedure parameters and result set columns can have option metadata - the docs need updated.  Also updated parser/metadata validation checks for procedures (param names, usage of rs columns, and return parameters) and views.  Allowing routines to have both a result set (which can be preceded by the TABLE keyword) and a return parameter that can be fully define in the parameter list as an out RESULT.  For example:

CREATE FOREIGN PROCEDURE PROC (OUT PARAM1 STRING RESULT, PARAM2 STRING) RETURNS TABLE (COL1 INTEGER, COL2 INTEGER) RETURNS STRING

Also changed the procedure parsing logic to not require the plan to be stored as CREATE UPDATE PROCEDURE ... - this could also be used in Designer to remove the unneeded prolog.

> Replace System VDB with DDL based metadata
> ------------------------------------------
>
>                 Key: TEIID-2103
>                 URL: https://issues.jboss.org/browse/TEIID-2103
>             Project: Teiid
>          Issue Type: Enhancement
>          Components: Embedded, Server
>    Affects Versions: 8.0
>            Reporter: Ramesh Reddy
>            Assignee: Steven Hawkins
>             Fix For: 8.1
>
>
> Currently System VDB is based on Designer based VDB which requires the vdb indexing logic to be present to load into system. Now that DDL based metadata facility is available, should consider removing the Designer based VDB over the DDL based. This has couple different advantages
> 1) Removes the dependency indexing logic to load
> 2) Embedded Teiid can also have System functionality (currently it does not)
> 3) Modifications to System metadata will be much easier
> 4) Teiid would be master copy that defines this, right now Designer has its own copy, Teiid has its own, keeping them in sync is proven to be hard based on recent JIRA
> as a initial step the "getSchema" method could be utilized to convert the current System.vdb into DDL form.

--
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