Checkout
 

jukka in jackrabbit

Remove the Travis notification webhook

This hasn't been working since early 2016. If someone is interested

in resurrecting this functionality, INFRA-11080 looks like a good

starting point.

OAK-1995: Improved SegmentNodeStore documentation

Document the magic constants used in MapRecord

OAK-1995: Improved SegmentNodeStore documentation

Add some TODOs for areas that could do with extra documentation

OAK-1995: Improved SegmentNodeStore documentation

Add a warning about the complex internals of MemoryNodeBuilder

Adjust trunk version back to 2.9-SNAPSHOT as discussed in http://markmail.org/message/ab5wdurinfx3etv3
  1. … 8 more files in changeset.
OAK-2003: Avoid <p/> in javadoc

Turn off strict javadoc checks in Java 8 to avoid more malformedness problems

Also add a link to JCR 2.0 javadocs

OAK-2003: Avoid <p/> in javadoc

perl -i -pe 's[<p/>][<p>]g' `find . -name '*.java'`

1.0.4: Merged revisions 1614384 and 1614385 (OAK-2002)
OAK-2002: TarMK: FileStore constructor loads all entries in the journal.log

Exclude accidentally committed parts.

OAK-2002: TarMK: FileStore constructor loads all entries in the journal.log

Load the journal.log as strings and only instantiate the last RecordIds.

OAK-1965: Support for constraints like: foo = 'X' OR bar = 'Y'

Push down per-selector multi-property OR constraints and use then in PropertyIndexPlan

OAK-1965: Support for constraints like: foo = 'X' OR bar = 'Y'

Refactor PropertyIndex to make it easier to extend.

Make the property index query plans more informative by including

the name of the index being used and the encoded values being looked up.

OAK-1965: Support for constraints like: foo = 'X' OR bar = 'Y'

Decouple OrderedPropertyIndex from PropertyIndex to allow independent evolution

OAK-1965: Support for constraints like: foo = 'X' OR bar = 'Y'

Make the per-selector constraints available to index implementations

OAK-1965: Support for constraints like: foo = 'X' OR bar = 'Y'

Use method dispatch instead of a switch statement for evaluating operators

OAK-1965: Support for constraints like: foo = 'X' OR bar = 'Y'

The IN operator is handled as a separate constraint type

OAK-1965: Support for constraints like: foo = 'X' OR bar = 'Y'

Extend OrImpl and AndImpl to support more than two component constraints,

and use that mechanism for improved simplification.

Replace the getInMap() feature with more specific code in OrImpl, as that's

the only place where the functionality is needed.

  1. … 6 more files in changeset.
OAK-1965: Support for constraints like: foo = 'X' OR bar = 'Y'

Improved simplification of IN constraints.

OAK-1965: Support for constraints like: foo = 'X' OR bar = 'Y'

Simplify the LiteralImpl string representation for STRING and LONG

values types that can be correctly parsed without a cast().

Add better equals() and hashCode() methods to LiteralImpl and

BindVariableValueImpl to make detecting duplicates easier/faster.

OAK-1939: Code coverage profile

Prevent Eclipse from complaining about the jacoco plugin

1.0.2: Merged revision 1607152 (OAK-1934)
1.0.2: Merged revision 1608783 (OAK-1932)
OAK-1932: TarMK compaction can create mixed segments

Avoid triggering revision cleanup at each new tar file.

Instead it gets triggered after compaction.

1.0.2: Merged revisions 1607077, 1607185, 1607196, 1607526, 1607664 and 1608560 (OAK-1927, OAK-1932)
OAK-1932: TarMK compaction can create mixed segments

Adjust the oak-run compact option to correctly trigger the cleanup after compaction

OAK-1945: Unclear NodeStore.merge() contract

Clarify the javadocs

OAK-1932: TarMK compaction can create mixed segments

Use a separate writer in the compaction code

OAK-1927: TarMK compaction delays journal updates

Better not to track backlog since the compaction

already automatically rebases recent changes and

flush is invoked once every five seconds.

Also expose more details in the thread name

OAK-1927: TarMK compaction delays journal updates

Refactor the existing flush thread functionality to a new BackgroundThread class

Add a new TarMK compaction background thread

OAK-1934: Optimize MutableTree.orderBefore for the common case

Only scan the actual child node list when the target node is not found in

the child order list or when appending to the end of the list. Ohterwise

use the already existing child order property.