This Bugzilla instance is deprecated, and most Eclipse projects now use GitHub or Eclipse GitLab. Please see the deprecation plan for details.
Bug 398193 - support a tuner option for configuration templates
Summary: support a tuner option for configuration templates
Status: RESOLVED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Eclipselink (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: James Sutherland CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-01-15 10:26 EST by James Sutherland CLA
Modified: 2022-06-09 10:05 EDT (History)
1 user (show)

See Also:


Attachments
adds SessionTuner and some other fixes (88.71 KB, patch)
2013-01-16 09:14 EST, James Sutherland CLA
no flags Details | Diff
some more fixes (27.24 KB, patch)
2013-02-26 11:18 EST, James Sutherland CLA
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description James Sutherland CLA 2013-01-15 10:26:35 EST
Allow a tuner option to allow the configuration of many persistence properties using a single configuration option.

This allows for simplified configuration by allowing different tuners to be built for different execution environments.  For example a user could create a DevelopmentTuner and a ProductionTuner that configures the persistent unit for the chosen environment.
Comment 1 James Sutherland CLA 2013-01-15 10:27:20 EST
Safe and Standard tuner options will be provided, as well as a SessionTuner interface to allow users and third parties to develop their own tuners.
Comment 2 James Sutherland CLA 2013-01-16 09:14:02 EST
Created attachment 225701 [details]
adds SessionTuner and some other fixes
Comment 3 James Sutherland CLA 2013-01-16 10:37:39 EST
Git main push - Bug#398193 - tuning configuration templates

https://bugs.eclipse.org/bugs/show_bug.cgi?id=398193

https://bugs.eclipse.org/bugs/show_bug.cgi?id=352500

Adds tuning templates and query results cache invalidation.

Changes:
- Added "eclipselink.tuning" persistence unit property to configure a SessionTuner configuration template (Safe, Standard, <custom-class>).
- Added "eclipselink.cache.query-results" persistence unit property to enable query results caching for all named queries.
- Added defaultQueryResultsCachePolicy on Project to default to all named queries.
- Added support for query results cache invalidation, any change to any class returned by the query causes the results to be invalidated.
- Added EMPTY CacheId constant.
- Added invalidateQueryCache(Class) API on IdentityMapAccessor
- Changed cache coordination merge to invalidate query cache.
- Changed UnitOfWork merge to invalidate query cache.
- Added invalidateOnChange property to QueryResultesCachePolicy (true by default).
- Changed TableCreator to check if a table exists before attempting to create it (added CHECK_EXISTENCE flag to disable this check).
- Added SafeModeTuner to provide a debugging tuned persistence unit.
- Added SessionTuner interface to allow configuration temaplates.
- Added StandardTuner for a default configuration.
- Added tests for query results invalidation to JPA AdvancedQueryTestSuite.
- Added clearQueryCache(Class) API to JpaCache.
Comment 4 James Sutherland CLA 2013-02-26 11:18:21 EST
Created attachment 227616 [details]
some more fixes
Comment 5 James Sutherland CLA 2013-03-04 08:44:48 EST
Git main push: Bug#398193 - tuning

https://bugs.eclipse.org/bugs/show_bug.cgi?id=398193

Some changes to facilitate tuning.

Changes:
- Added hook to pass session to batch writing mechanism.
- Some cleanup.
Comment 6 James Sutherland CLA 2013-05-01 10:44:44 EDT
support added in 2.5
Comment 7 Eclipse Webmaster CLA 2022-06-09 10:05:29 EDT
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink