[
https://issues.apache.org/jira/browse/ISIS-573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Haywood updated ISIS-573:
-----------------------------
Summary: [WON'T FIX] To improve performance, set up caching of query
results against any entities that are immutable (ie ref data, ie have
ImmutableFacet on them). (was: To improve performance, set up caching of query
results against any entities that are immutable (ie ref data, ie have
ImmutableFacet on them).)
> [WON'T FIX] To improve performance, set up caching of query results against
> any entities that are immutable (ie ref data, ie have ImmutableFacet on them).
> ----------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: ISIS-573
> URL: https://issues.apache.org/jira/browse/ISIS-573
> Project: Isis
> Issue Type: New Feature
> Components: Core, Core: Objectstore: JDO
> Affects Versions: objectstore-jdo-1.1.0, core-1.2.0
> Reporter: Dan Haywood
> Priority: Major
> Fix For: 3.0.0
>
>
> In DN, this is done using:
> query.addExtension("datanucleus.query.results.cached", "true");
> query.addExtension("datanucleus.query.resultCache.validateObjects", "false");
> So, need to figure out how to set up these properties on queries by
> repositories of immutable facets. But this could probably be done
> transparently.
> NB: for these cache results to hang around and not get garbage collected,
> would also need to set the global config parm:
> datanucleus.cache.queryResult.type=strong
> ... its default value is weak.
> Further info at:
> http://www.datanucleus.org/products/datanucleus/jdo/query_cache.html#datastoreCompilation
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
