Jump to: navigation, search

EclipseLink/DesignDocs/356812

Design Specification: Database Change Event Cache Invalidation

ER 356812

Feedback

Document History

Date Author Version Description & Notes
2011-09-06 James 0.1 Draft

Project overview

Some databases support raising change events when tables are updated or changed. It is also possible in some databases to raise events from triggers, and some third party products support raising database change events.

When a share cache is used in EclipseLink it can become stale if other applications (or other nodes) update the database directly.

This project will provide an infrastructure for supporting database change events to invalidate the changed objects in the EclipseLink shared cache.

Oracle's Database Change event Notification will be supported for Oracle databases.


Concepts

Oracle DCN : The Oracle database Database Change event Notification feature available since Oracle 10.2.

Requirements

  • Support generic database change event listener.
  • Support Oracle DCN
  • Support cache invalidation of change objects.

Design Constraints

  • Must support database events with limited information, such as only the table ROWID.

Functionality

  • Add a DatabaseEventNotificationListener interface and to DatabaseSessionImpl (Database and Server sessions).
    • Give register/remove callbacks on login/logout.
  • Add OracleDCNListener to Oracle with Oracle JDBC dependencies.
    • Register with database on login, remove on logout. Register all tracked tables.
    • Oracle DCN only gives table name and ROWID, no primary key, so need to match ROWID with ID.
    • Adds ROWID and a cache index on ROWID to all tracked descriptors.
    • All objects read will be indexed by ROWID from cache index.
    • Add insert callback to select ROWID and index in cache.
    • On any update or delete get the transaction id and store in the unit of work properties.
    • On merge for updates include the transaction id in the CacheKey
    • When a DCN event is received find the CacheKey for the ROWID, and invalidate unless its transaction id matches the events transaction id.
  • Add a DatabaseCacheInvalidationPolicy to allow a descriptor to be configured to receive change events.
    • Add a persistence unit default property for cache invalidation type.
  • Only the primary table is supported. For secondary tables, or relationships usage of optimistic locking is required to ensure the primary table is always updated.

Testing

Add a JPA test model for DCN testing to the Oracle tests. Test:

  • multiple tables (with versioning)
  • inheritance
  • relationships (with versioning)
  • ensure objects invalidated in other session
  • test native SQL queries
  • test update-all queries

API

  • @Cache
    • invalidationType
  • CacheInvalidationType (TimeToLive, Database, Daily, None)

Native API

  • DatabaseSession
    • setDatabaseEventListener(DatabaseEventNotificationListener )
  • DatabaseEventNotificationListener (org.eclipse.persistence.platform.database.events)
  • OracleDCNListener (org.eclipse.persistence.platform.oracle.dcn)

Config files

  • persistence.xml - property
    • "eclipselink.cache.database-event-listener"="<class-name>"
    • "eclipselink.cache.invalidation.default"=CacheInvalidationType
  • orm.xml
<cache invalidation-type="Database"/>

Documentation

Should be documented under caching section, and Oracle section.

Open Issues

Issue # Owner Description / Notes
1 How to handle secondary tables and relationships?
2 How to integrate with third party cache support?

Decisions

Issue Description / Notes Decision

Future Considerations

  • Other databases and event mechanisms.
  • Show examples the uses triggers and Oracle AQ.