-
1. Re: Multi-source awareness in translator
shawkins Jan 6, 2012 11:47 AM (in response to wannasurf)1 of 1 people found this helpfulTim,
The importProperties are actually the model properties, so you can use org.teiid.metadata.MetadataFactory.getImportProperties().getProperty("supports-multi-source-bindings"). Is this related to TEIID-1880?
Steve
-
2. Re: Multi-source awareness in translator
wannasurf Jan 6, 2012 12:10 PM (in response to shawkins)No, this is not directly related to TEIID-1880. Our JBoss/Teiid application requires additional metadata to supplement what the application can discover about the tables in our dynamic VDB from the system tables, and this metadata includes information about the tables and columns we define during the getMetadata function. The application metadata, as well as the dynmaic VDB tables and columns, is constructed during the processing of the getMetadata function within our custom translators. For multi-source, the source_name column that Teiid internally adds to each of our tables must also be described by our application metadata at getMetadata time. However, if we are configured to run single-source, Teiid obviously will not add this column and therefore our translator getMetadata function also should not create application metadata for this column..
-
3. Re: Multi-source awareness in translator
rareddy Jan 6, 2012 1:41 PM (in response to wannasurf)Tim,
It is your application that is defining whether the given model is multi-source or not by defining the above property in the -vdb.xml under "model" fragment that Steve mentioned, so the by using above technique you can figure out the model defined this property or not to decide it is multi-source or not.
Ramesh..