[teiid-issues] [JBoss JIRA] Commented: (TEIID-444) Expose the cache to connectors.

[John Doyle (JIRA)]

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

John Doyle commented on TEIID-444:
----------------------------------

The XML connector has a requirement that it stream the XML documents it is parsing because large docs can blow out memory.  In order to satisfy the streaming and caching requirements, I am chunking the xml into nodes under a node representing the response as it passes into the parser.  So a document is represented in the cache by a FQN (the ID) and it's children (the content).

I assume in the API you're describing the Object returned from getFromCache is the actual cached object, and not a Node of any sort, right?  I would prefer to have the hierarchical structure of the cache exposed in the API, it simplifies access in ways that would otherwise have to be accomplished through more state in the connector.  In this case, the connector would have to map a document key to multiple cache items.

This is an implementation question, not an API question, but how will connector caches show to a user for administration purposes?  Will they be able to map them to a binding instance?

~jd


> Expose the cache to connectors.
> -------------------------------
>
>                 Key: TEIID-444
>                 URL: https://jira.jboss.org/jira/browse/TEIID-444
>             Project: Teiid
>          Issue Type: Feature Request
>          Components: Connector API
>    Affects Versions: 6.0.0
>            Reporter: John Doyle
>            Assignee: Ramesh Reddy
>             Fix For: 6.1.0
>
>
> The XML-Relational connectors have historically had their own cache.  I'm modifying the connectors to use JBoss cache and it would benefit users if this connector and other connectors with need of a cache could use the teiid cache to ease cache configuration and monitoring.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira