[ https://issues.jboss.org/browse/TEIID-2914?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-2914: ------------------------------------ Also, part of the thinking is to make the cacheWrapper like a jdbc driver. In a database, it performs the query the best it can, and I would assume the cache query execution would do the same. The user/translator doesn't need to know what's the best option in order to issue a query. If they need to know that, they could look at how the cache is configured. Additionally, ask the wrapper for the metadata. I know you don't want to push the language objects into connector. Then an option could be , in the translator, could use a visitor to obtain what's needed to pass as the query. Similar to what other translators do when they construct data source specific query. -- 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