[
https://issues.jboss.org/browse/TEIID-2914?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-2914:
---------------------------------------
Now, if this logic is pushed into the translator, it brings a lot of
dependencies. And on the other had, if put into the connector, I was thinking the
cacheContainerWrapper as the means to expose this info, as the connection has access to
this object.
How does it bring in less dependencies in the resource adapter? That is we still have to
package both the translator and the resource adapter. Are you thinking about making
separate resource adapter instances such that one could be omitted from the kits?
The user/translator doesn't need to know what's the best
option in order to issue a query.
The translator is not the user. Also there are for example numerous jdbc capabilities
that can be controlled via translator properties.
Infinispan Connector didn't have the advanced searching option
exposed
----------------------------------------------------------------------
Key: TEIID-2914
URL:
https://issues.jboss.org/browse/TEIID-2914
Project: Teiid
Issue Type: Bug
Components: Misc. Connectors
Affects Versions: 8.7, 8.7.1
Reporter: Van Halbert
Assignee: Steven Hawkins
The advanced searching option (i.e, lucene searching) that is defined in the .rar was not
being picked up in the connector.
Also, it was incorrectly defined on the translator, because the translator cannot
override how the cache is configured.
--
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