[teiid-issues] [JBoss JIRA] (TEIID-2914) Infinispan Connector didn't have the advanced searching option exposed
Van Halbert (JIRA)
issues at jboss.org
Thu Apr 3 09:03:13 EDT 2014
[ https://issues.jboss.org/browse/TEIID-2914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12958917#comment-12958917 ]
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.
> 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
More information about the teiid-issues
mailing list