[teiid-issues] [JBoss JIRA] (TEIID-4217) Add support for Name In Source to MongoDB translator

[Steven Hawkins (Jira)]

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

Steven Hawkins reassigned TEIID-4217:
-------------------------------------

    Fix Version/s: Open To Community
         Assignee:     (was: Ramesh Reddy)


Moving to a community issue.  Looking forward we'll discourage the hand creation of source metadata, so the name in source can be a mostly internal detail and only needed in instances where the source name is not a valid teiid name.

> Add support for Name In Source to MongoDB translator
> ----------------------------------------------------
>
>                 Key: TEIID-4217
>                 URL: https://issues.jboss.org/browse/TEIID-4217
>             Project: Teiid
>          Issue Type: Enhancement
>          Components: Misc. Connectors
>    Affects Versions: 8.12.x
>            Reporter: Andrej Smigala
>            Priority: Minor
>             Fix For: Open To Community
>
>
> MongoDB translator currently ignore NAMEINSOURCE option on the table, unlike e.g. the JDBC translators. 
> So for instance querying a vdb like this:
> {code:xml}
> <vdb name="mongo" version="1">
>     <model name="mongo">
>         <source name="local" translator-name="mongodb" connection-jndi-name="java:/mongoDS"/>
>         <metadata type="DDL"><![CDATA[
>             CREATE FOREIGN TABLE MyOrders (
>                 OrderID integer PRIMARY KEY,
>                 CustomerId integer,
>                 OrderDate date,
>                 Status integer
>             ) OPTIONS(UPDATABLE 'TRUE', NAMEINSOURCE 'CustomOrders');
>             ]]>
>         </metadata>
>     </model>
> </vdb>
> {code}
> will create a collection called 'MyOrders' in the database, rather than 'CustomOrders'



--
This message was sent by Atlassian Jira
(v7.12.1#712002)