[
https://issues.jboss.org/browse/TEIID-2210?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-2210:
---------------------------------------
You could say the same thing for database tables. It's a question of the likelihood
of a cache name change vs. configuring a translator per cache (which seems like a lot of
work). I would vote for the current view that the ObjectConnection roughly represents a
CacheContainer.
You could workaround this by introducing a cache name indirection mechanism (similar to
the file translator), just have a special type of ObjectConnection that represents a
singleton cache and would therefore effectively ignore the name for lookup purposes, or
add back just a single cache name as a configuration property. At this point I would vote
for keeping additional configuration off of the translator.
Create Object Translator to support Infinispan and other Map oriented
data sources
----------------------------------------------------------------------------------
Key: TEIID-2210
URL:
https://issues.jboss.org/browse/TEIID-2210
Project: Teiid
Issue Type: Feature Request
Components: Misc. Connectors
Reporter: Van Halbert
Assignee: Van Halbert
Create the Object-translator that can support map oriented data sources (i.e.,
Infinispan, Coherence, etc.). The OBJECTABLE function can be used to tabularize the
object once retrieved from the translator.
--
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