Technically, we can pass the schema name in the SQL statement, however that doesn't seem to work either.. which is funny because SELECT * FROM <schema>.<table> is valid SQL.

Below steps to reproduce the issue:

• Create the proprietary database extension:
  https://access.redhat.com/documentation/en-us/red_hat_fuse/7.2/html-single/connecting_fuse_online_to_applications_and_services/index#connecting-to-proprietary-databases_db
• Import the extension jar into Fuse online
• Create a database connection and configured the correct url , user, password and schema.
• Validate the connection
• Create a new integration, pick my database connection as start and choose Period select. Enter SELECT * FROM TEST

The error occurs. The meta pod log shows the error, see below:

Caused by: io.syndesis.common.util.SyndesisServerException: Table 'TEST' does not exist in schema 'TABLEAPI' 
at io.syndesis.connector.sql.SqlConnectorMetaDataExtension.meta(SqlConnectorMetaDataExtension.java:60) ~[connector-sql-1.7.13.fuse-740001-redhat-00002.jar!/:1.7.13.fuse-740001-redhat-00002] 
at io.syndesis.connector.support.verifier.api.ComponentMetadataRetrieval.fetchMetaData(ComponentMetadataRetrieval.java:58) ~[connector-support-verifier-1.7.13.fuse-740001-redhat-00002.jar!/:1.7.13.fuse-740001-redhat-00002] 
at io.syndesis.connector.support.verifier.api.ComponentMetadataRetrieval.fetch(ComponentMetadataRetrieval.java:48) ~[connector-support-verifier-1.7.13.fuse-740001-redhat-00002.jar!/:1.7.13.fuse-740001-redhat-00002] 
at io.syndesis.connector.meta.v1.ConnectorEndpoint.actions(ConnectorEndpoint.java:80) ~[classes!/:1.7.13.fuse-740001-redhat-00002] 
... 88 common frames omitted

We have tried to work around the issue:

• Tried a query on a table instead of a view
• Tried a different SCHEMA / table in the same DB.
• Tried quotes (" ") around schema and viewname (sometimes the _ underscores are a problem)
• Tried with and without schema in the connection
• Tried deleting everything and recreate extension and connection again.