[ https://issues.jboss.org/browse/TEIID-2914?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-2914: ------------------------------------ Its easy to remove, but is it the better option. I was thinking, that in this case, the resource adapter is like a jdbc driver, you ask it what's its capabilities are. The configuration of the resource adapter is there, then why not add what it supports too. The translator will check for the capability from the Cache (i.e., cache wrapper) and then performs the appropriate type of query. I really think, the function of querying (e.g. by key, lucene or DSL) should be moved into the cache wrapper, so the translator doesn't need to control how its performed. And with the addition of DSL support and the dependencies on google protobuf's, if we don't segment this more, there will be no separation between the translator and resource adapter. -- 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