Dirty Read - Space Schema

Added by Gilad David Maayan, last edited by Aleia Hutcherson on May 25, 2008  (view change)
  GigaSpaces 5.X

Documentation Home
Quick Start Guide
Release Notes

Previous release
  Search Here
Searching GigaSpaces Platform 5.X Documentation

                                               
Summary: Defining whether objects under a transaction should be visible to read operations.

Overview

The JavaSpaces specification defines the visibility of entries for read operations as follows: a read operation performed under a null transaction can only access Entries that are not write-locked by non-null transactions. In other words, Entries that were written or taken by active transactions (transactions that have not been committed or rolled back) are not visible to the user performing a read operation.
Sometimes it is desirable for non-transactional read operations to have full visibility of the entries in the space. The dirty read property, once set, enables the read/readIfExist under null transaction and with the JavaSpace.NO_WAIT timeout parameter, to have this complete visibility.
In order to set the dirty read property, set the <dirty_read> tag to true in the space schema configuration file.

<space-config>
   <!--full visibility of the entries under transaction read/readIfExists-->
    <dirty_read>false</dirty_read>
</space-config>

Wiki Content Tree

Your Feedback Needed!

We need your help to improve this wiki site. If you have any suggestions or corrections, write to us at techw@gigaspaces.com. Please provide a link to the wiki page you are referring to.

Labels

 
(None)