[teiid-issues] [JBoss JIRA] (TEIID-2706) Cache hint for resultset cache in user query doesn't work

Fri Oct 18 16:40:01 EDT 2013

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

Steven Hawkins commented on TEIID-2706:
---------------------------------------

I don't see enough information here or in the case to say what may be going on.  From the unit tests the user query cache hint is working as expected.

Can you provide more on the exact queries being issued?

> Cache hint for resultset cache in user query doesn't work
> ---------------------------------------------------------
>
>                 Key: TEIID-2706
>                 URL: https://issues.jboss.org/browse/TEIID-2706
>             Project: Teiid
>          Issue Type: Bug
>          Components: Query Engine
>    Affects Versions: 7.7.7
>            Reporter: Debbie Steigner
>            Assignee: Steven Hawkins
>
> I enabled TRACE logging and Command Logging to see if the Resultset Cache was being used on my queries.  If I use the ResultSetCacheMode=true on connection string you can see Teiid using the cache instead of pulling from source again:
> This is displayed the first time the query is run, it's loading the Cache:
> 2013-10-18 07:17:52,951 TRACE [org.teiid.PROCESSOR] Adding to global/distributed cache Cache Entry<tR+M2n5wIwzI=bqt2 at teiid-security> params:null sql:select * from SmallA
> This displays the subsequent times the same query is run and you will not see source queries:
> 2013-10-18 07:19:21,115 TRACE [org.teiid.PROCESSOR] Cache hit for Cache Entry<tR+M2n5wIwzI=bqt2 at teiid-security> params:null sql:select * from SmallA
> But if I remove the connection string and just try using the Cache Hint  /*+ cache*/ you see nothing in the logs in regards to the Cache loading or being used on the second query, you still see Teiid pulling the results from the source.

--
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