[teiid-issues] [JBoss JIRA] (TEIID-5455) Result Set Cache Hit Ratio % doesn't calculate for Odata/Odata4 queries

[Steven Hawkins (JIRA)]

     [ https://issues.jboss.org/browse/TEIID-5455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steven Hawkins resolved TEIID-5455.
-----------------------------------
    Fix Version/s: 11.1
       Resolution: Done


Added code to allow the resultset cache property to elevate caching beyond session specific.

> Result Set Cache Hit Ratio % doesn't calculate for Odata/Odata4 queries
> -----------------------------------------------------------------------
>
>                 Key: TEIID-5455
>                 URL: https://issues.jboss.org/browse/TEIID-5455
>             Project: Teiid
>          Issue Type: Enhancement
>          Components: OData
>    Affects Versions: 8.12.14.6_4
>            Reporter: Debbie Steigner
>            Assignee: Steven Hawkins
>             Fix For: 11.1
>
>
> The Result Set Cache Hit Ratio percentage metric appears to only use JDBC and ODBC connections in the calculation.  Connected via JDBC with resultSetCacheMode=true Connection property and ran the same query a few times and it shows values in the Management Console for Hit Ratio %, Total Entries and Request Count.  The same result when using vdb property "<property name="connection.resultSetCacheMode" value="true"/>" and ODBC connection.  But after adding the init-param connection property[1] to the web.xml of the teiid-olingo-odata4.war and restarting the server.  Then running the same odata4 query a few times only values show for Total Entries and Request Count, the Hit Ratio is still at 0.0.  Is this intended behavior?  Or should Odata and Odata4 queries be included in the Ratio?
> [1]
> <init-param>
>    <param-name>connection.resultSetCacheMode</param-name>
>             <param-value>true</param-value>       
>        </init-param> 



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)