[teiid-issues] [JBoss JIRA] (TEIID-2251) All multi-source models share the same metadata
Steven Hawkins (JIRA)
issues at jboss.org
Mon Jul 2 17:46:00 EDT 2018
[ https://issues.jboss.org/browse/TEIID-2251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steven Hawkins resolved TEIID-2251.
-----------------------------------
Resolution: Deferred
Without a major overhaul of the import logic especially when sources are added/removed at runtime, there isn't a great way to do this. If manipulating the import naming is not sufficient (such as errors caused by native type) another workaround is to use a vdb per source and then a multi-source vdb over the source vdbs.
> All multi-source models share the same metadata
> -----------------------------------------------
>
> Key: TEIID-2251
> URL: https://issues.jboss.org/browse/TEIID-2251
> Project: Teiid
> Issue Type: Sub-task
> Components: Query Engine, Server
> Affects Versions: 8.1, 8.2
> Environment: Win XP pro, JBoss AS 7.1.1, JDBC drivers: system-i (jt400 7.8) , MySQL (connector/j 6.5.1)
> Reporter: Dave Stannard
> Assignee: Steven Hawkins
>
> Sharing the same metadata can cause issues, for heterogeneous sources or when attempting to use multi-source for multiple schemas, as described below:
> Teiid issues queries with the catalog and schema of the the primary source. This gives invalid results for all the other sources.
> If the non-primary source connection(s) have authority to access the primary's catalog/schema then duplicated rows are returned to the client.
> If it does *not* have authority then an error results.
> Note: In MySQL this effect can be mitigated by setting useCatalogName=false. This seems to be because the JDBC4DatabaseMetaData.getTables() method does not return a schema; so suppressing the catalog is enough.
> For the System-I whose equivalent getTables() method returns a catalog and schema, I couldn't find a workaround.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
More information about the teiid-issues
mailing list