Issue Details (XML | Word | Printable)

Key: NUCCORE-355
Type: New Feature New Feature
Status: Closed Closed
Resolution: Fixed
Priority: Minor Minor
Assignee: Andy Jefferson
Reporter: Eric Sultan
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
DataNucleus Core

Add the possibility to configure which class to pin in L2Cache by configuration

Created: 01/Aug/09 10:15 AM   Updated: 10/Dec/10 07:48 AM   Resolved: 21/Nov/10 03:50 PM
Component/s: Cache
Affects Version/s: None
Fix Version/s: 2.2.0.release


 Description  « Hide
Two ways :
- datanucleus.cache.level2.classNames (comma-separated) and/or datanucleus.cache.level2.packageNames (comma-separated)
- put an extension in metadata <extension vendor-name="datanucleus" key="pin-at-start" value="true"/>

Sort Order: Ascending order - Click to sort in descending order
Eric Sultan added a comment - 05/Aug/09 09:17 AM
Usage :
an extension have to be set on the class we want to auto pin at start :
<extension vendor-name="datanucleus" key="auto-pinning" value="yes"/>

values : no (default) - yes (on the current class) - subclass (on the current class and all subclasses)

Andy Jefferson added a comment - 21/Nov/10 03:50 PM
SVN trunk now supports class-level metadata extension "cache-pin" (true/false - default=false) as defining if objects of the class will be pinned in the L2 cache (assuming the L2 cache supports pinning)