[teiid-issues] [JBoss JIRA] (TEIID-1992) Create Connector/Translator to support Infinispan as a data source

[Justin Hayes (JIRA)]

    [ https://issues.jboss.org/browse/TEIID-1992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12685458#comment-12685458 ] 

Justin Hayes commented on TEIID-1992:
-------------------------------------

The file I just attached is the module responsible for interfacing with ispn, primarily for using it as the queryable index layer. The index entries are represented as objects of type StringIndex, which includes a key and value representing the indexed field and value, respectively. There is also a docId which is the UUID of the document from which the index was extracted. It is these StringIndex objects that are stored in ispn and queried via the lucene directory implementation. Check out the InfinispanService.searchIndex) method to see how searching is done. The search returns a list of Strings, which are the UUIDs (docId field) and the invoker is expected to use those UUIDs to load the full documents from the data store. 

This doesn't expose any way to "know" about the metadata stored within the cache, so I'm not sure how useful it is for what you were already thinking of doing. In fact, it was made to be the opposite - to support any type of index. That's why the StringIndex class is so generic.
                
> Create Connector/Translator to support Infinispan as a data source
> ------------------------------------------------------------------
>
>                 Key: TEIID-1992
>                 URL: https://issues.jboss.org/browse/TEIID-1992
>             Project: Teiid
>          Issue Type: Feature Request
>          Components: Misc. Connectors
>            Reporter: Van Halbert
>            Assignee: Van Halbert
>         Attachments: ispn-integration.zip
>
>
> Create a Connector/Translator in order for Teiid to support Infinispan as a read-only data source on its initial release.  Read Only because if someone is building an object cache, the primary means for updating the cache would not be thru relational means.  However, if someone is wanting to add an object cache as a disparate data source for data integration for exposing the content, then this connector/translator will enable that. 
> A goal here is to build an object translator framework that can easily plug in other object cache sources.  Example, add support for Coherence.   There was a Coherence connector/translator already created in the sandbox, for which, it will provide direction for the object translator.  

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira