[
https://issues.jboss.org/browse/TEIID-5455?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-5455:
---------------------------------------
To support odata pagination the odata layer already adds its own cache hint which
currently supersedes the result set cache mode as it makes the query results specific to a
given skipToken. This would be a new feature to allow query results to be cached at a
higher level via the connection property.
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: Bug
Affects Versions: 8.12.14.6_4
Reporter: Debbie Steigner
Assignee: Steven Hawkins
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)