com.bigdata.btree.isolation

Class TestConflictResolution

java.lang.Object

junit.framework.Assert

junit.framework.TestCase

junit.framework.TestCase2

com.bigdata.btree.isolation.TestConflictResolution

All Implemented Interfaces:

junit.framework.Test

public class TestConflictResolution
extends TestCase2

Tests of write-write conflict resolution.

Write-write conflicts either result in successful reconcilation via state-based conflict resolution or an abort of the transaction that is validating. The tests in this suite verify that write-write conflicts can be detected and provide versions of those tests where the conflict can and can not be validated and verify the end state in each case.

State-based validation requires transparency at the object level, including the ability to deserialize versions into objects, to compare objects for consistency, to merge data into the most recent version where possible and according to data type specific rules, and to destructively merge objects when the conflict arises on identity rather than state.

An example of an identity based conflict is when two objects are created that represent URIs in an RDF graph. Since the lexicon for an RDF graph generally requires uniqueness those objects must be merged into a single object since they have the same identity. For an RDFS store validation on the lexicon or statements ALWAYS succeeds since they are always consistent.

Version:

$Id$

Author:

Bryan Thompson

Nested Class Summary

Nested Classes

Modifier and Type	Class and Description
static class	TestConflictResolution.SingleValueConflictResolver Helper class used to resolve a predicted conflict to a known value.

Nested classes/interfaces inherited from class junit.framework.TestCase2

TestCase2.MyProperties, TestCase2.RandomType

Field Summary

Fields inherited from class junit.framework.TestCase2

_randomType, log

Constructor Summary

Constructors

Constructor and Description
TestConflictResolution()
TestConflictResolution(String name)

Method Summary

Methods

Modifier and Type	Method and Description
Properties	getProperties() Reads in the configuration properties for the test from a variety of resources and returns a properties hierarchy.
void	test_writeWriteConflict_conflictIsResolved() Test correct detection and resolution of a write-write conflict.
void	test_writeWriteConflict_correctDetection() Test correct detection of a write-write conflict.

Methods inherited from class junit.framework.TestCase2

assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEqualsWithinUlps, assertSameArray, assertSameArray, assertSameBigDecimal, assertSameBigDecimal, assertSameBigInteger, assertSameBigInteger, assertSameIterator, assertSameIterator, assertSameIteratorAnyOrder, assertSameIteratorAnyOrder, assertSameValue, assertSameValue, assertZeroUlps, assertZeroUlps, fail, getInnerCause, getNormalInt, getProjectBuildPath, getRandomObject, getRandomObject, getRandomOrder, getRandomString, getTestInputStream, getTestResource, getTestResource, getUlps, getUlps, isDEBUG, isDEBUG, isINFO, isINFO, isInnerCause, logProperties

Methods inherited from class junit.framework.TestCase

assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertFalse, assertFalse, assertNotNull, assertNotNull, assertNotSame, assertNotSame, assertNull, assertNull, assertSame, assertSame, assertTrue, assertTrue, countTestCases, createResult, fail, fail, failNotEquals, failNotSame, failSame, format, getName, run, run, runBare, runTest, setName, setUp, tearDown, toString

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, wait, wait, wait

Constructor Detail

TestConflictResolution

public TestConflictResolution()

TestConflictResolution

public TestConflictResolution(String name)

Parameters:

name -

Method Detail

getProperties

public Properties getProperties()

Description copied from class: TestCase2

Reads in the configuration properties for the test from a variety of resources and returns a properties hierarchy. If a property name is not bound at the top-level of the returned Properties object, then the lower levels of the hierarchy are recursively searched.

The hierarchy is constructed from the following properties files in the following order. The first property file in this list corresponds to the top of the property hierarchy. The last property file in this list corresponds to the bottom of the property hierarchy. The property resources are:

1. The System properties specified using the -D argument on the command line.
2. ${user.home}/build.properties. ${user.home} is the value of the Java system environment variable named "user.home" and corresponds to the user home directory. A warning is logged if this properties file does not exist. Note: The JUnit UI can wind up with a different value for this property than when you execute tests without the UI. It is an error if the properties file exists but can not be read.
3. {class}.properties, where {class} is the class name reported by Java reflection, is loaded iff it is found.
4. {class} is repeatedly truncated by dropping the last package name component to generate a package name. If a properties file named "test.properties" exists in that package then those properties are loaded.

Overrides:

getProperties in class TestCase2

Returns:

A Properties object that supplies bindings for property names according to the described hierarchy among property resources. The returned Properties is NOT cached. TODO This does not handle the recursive truncation of the class name to search for "test.properties" yet.

test_writeWriteConflict_correctDetection

public void test_writeWriteConflict_correctDetection()

Test correct detection of a write-write conflict. An index is registered and the journal is committed. Two transactions (tx1, tx2) are then started. Both transactions write a value under the same key. tx1 prepares and commits. tx2 attempts to prepare, and the test verifies that a ValidationError is reported.

test_writeWriteConflict_conflictIsResolved

public void test_writeWriteConflict_conflictIsResolved()

Test correct detection and resolution of a write-write conflict. An index is registered with an IConflictResolver and the journal is committed. Two transactions (tx1, tx2) are then started. Both transactions write a value under the same key. tx1 prepares and commits. tx2 attempts to prepare, and the test verifies that the conflict resolver is invoked, that it may resolve the conflict causing validation to succeed and that the value determined by conflict resolution is made persistent when tx2 commits.