[teiid-issues] [JBoss JIRA] (TEIID-2372) Providing functionality to set source table cardinality when metadata loaded

[Ramesh Reddy (JIRA)]

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

Ramesh Reddy resolved TEIID-2372.
---------------------------------

        Labels: CR1  (was: )
    Resolution: Done


Implemented the last suggestion.
{code}
ALTER FOREIGN TABLE {name) [(ADD|SET|DROP) {prop-name} {prop-value}] 
    [(,ALTER COLUMN {name} (ADD|SET|DROP) {prop-name} {prop-value})*]
{code}

The above also supports VIEWS and PROCEDURES. For example, if you want to add CARDINALITY to a table that you imported from a source database, you can do following.


{code:lang=XML}
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<vdb name="northwind" version="1">
    <model name="nw">
        <property name="importer.importKeys" value="true"/>
        <property name="importer.importProcedures" value="true"/>
         <source name="northwind-connector" translator-name="mysql" connection-jndi-name="java:/nw-ds"/>
         <metadata type = "NATIVE,DDL"><![CDATA[
              ALTER FOREIGN TABLE northwind.customers ADD CARDINALITY 10000,
                 ALTER COLUMN CompanyName ADD FOO 'BAR';
         ]]>
         </metadata>
    </model>
</vdb>
{code}

                
> Providing functionality to set source table cardinality when metadata loaded
> ----------------------------------------------------------------------------
>
>                 Key: TEIID-2372
>                 URL: https://issues.jboss.org/browse/TEIID-2372
>             Project: Teiid
>          Issue Type: Feature Request
>          Components: Query Engine
>    Affects Versions: 8.2
>            Reporter: Jack Ma
>            Assignee: Ramesh Reddy
>              Labels: CR1
>             Fix For: 8.3
>
>
> Want to have a easy way to set the source table cardinality when source model metadata loaded

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira