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

[ https://issues.jboss.org/browse/TEIID-2292?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2292. ----------------------------------- Fix Version/s: 8.3 Resolution: Done Added the model property multisource.addColumn to control if a multi-source column is added to the actual metadata. 2/3 follow directly from this. The designer side of 1 was not addressed, however the refactoring allows for the use of the multi-source pseudo-column in view/procedure definitions even without actually adding the column. This is because the metadata wrapper logic was moved into the initial metadata construction on CompositeVDB. There is a possible issue here in that if you then turn multi-source off, the definitions may then become invalid. However I don't see this a large issue since - it could be worked around by having a multi-source model with 1 source and/or allowing the addColumn property to work with non-multisource models - and this is inline with how the multisourcemetadatawrapper used to function in that it was always applied. For the design time metadata it basically returned itself meaning that the columns were available for definition resolution and it ensured that columns matching the multi-source column name didn't have two different meanings. -- 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