[teiid-issues] [JBoss JIRA] (TEIID-2292) Add "SOURCE_NAME" column automatically for Multi-Source models
[
https://issues.jboss.org/browse/TEIID-2292?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-2292:
---------------------------------------
Having the source name configurable overlaps with TEIID-2254 and is somewhat of a separate
issue.
The rationale for having an actual source_name column in the metadata is:
1. For Designer (which a fix on our side won't currently address) you can then you use
the source_name column in transformations, rather than only at runtime.
2. For dynamic vdbs downstream consumption of the metadata will have the source_name
column exposed - otherwise it is not since it is not known to the system tables.
3. For dynamic or designer vdbs eligible procedures (those that have no out/inout/return)
will be automatically multi-source enabled, which was the primary concern of
https://community.jboss.org/message/773694#773694
Add "SOURCE_NAME" column automatically for Multi-Source
models
--------------------------------------------------------------
Key: TEIID-2292
URL: https://issues.jboss.org/browse/TEIID-2292
Project: Teiid
Issue Type: Feature Request
Components: Query Engine
Affects Versions: 8.2
Reporter: Ramesh Reddy
Assignee: Steven Hawkins
Currently Teiid adds SOURCE_NAME pseudo column when the model defines as multi-source to
all the tables. This is not reflected in the metadata. However based on the community
requests it looks like providing a way to automatically adding this to the tables and
procedures is useful in dynamic vdb scenarios.
This can be added when a property like
<property name="multi-source-column" value="{name-of-column}"/>
--
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