Package com.bigdata.rdf.internal

This package provides an internal representation of RDF Values.

See: Description

Interface Summary

Interface	Description
DTEFlags	Data type enum bit flags.
IDatatypeURIResolver	Specialized interface for resolving (and creating if necessary) datatype URIs.
IExtension<V extends BigdataValue>	IExtensions are responsible for round-tripping between an RDF Value and an LiteralExtensionIV for a particular datatype.
IExtensionFactory	IExtensionFactories are responsible for enumerating what extensions are supported for a particular database configuration.
IExtensionIV
IInlineUnicode	Interface for IVs which have inline Unicode components in their representation.
IInlineURIFactory	This factory will create URIExtensionIVs using InlineURIHandler delegates.
ILexiconConfiguration<V extends BigdataValue>	Configuration determines which RDF Values are inlined into the statement indices rather than being assigned term identifiers by the lexicon.
InlineLiteralIV<V extends BigdataLiteral,T>	Common root interface for AbstractLiteralIV and LiteralExtensionIV, the two inline literal IV class roots.
INonInlineExtensionCodes	An interface declaring the one byte extension code for non-inline IV s.
IPrefixedURIHandler	Utility for inline URI Handlers that have a namespace and a prefix
ISuffixedURIHandler	Utility for inline URI Handlers that have a namespace and a suffix
IV<V extends BigdataValue,T>	Interface for the internal representation of an RDF Value (the representation which is encoded within the statement indices).
IVCache<V extends BigdataValue,T>	Interface for managing the BigdataValue cached on an IV.

Class Summary

Class	Description
AbstractEncodeDecodeKeysTestCase
AbstractEncodeDecodeMixedIVsTest	Test of encode/decode and especially comparator semantics for mixed IVs.
BSBMExtensionFactory	Adds inlining for the http://www4.wiwiss.fu-berlin.de/bizer/bsbm/v01/vocabulary/USD datatype, which is treated as xsd:float.
ColorsEnumExtension<V extends BigdataValue>	Example of how to do a custom enum and map that enum over a byte using a native inline XSDByteIV.
CompressedTimestampExtensionFactory	Extension factory that adds a compressed timestamp literal datatype, namely .
DefaultExtensionFactory	Default IExtensionFactory.
EpochExtension<V extends BigdataValue>	This implementation of IExtension implements inlining for literals that represent time in milliseconds since the epoch.
HashCollisionUtility	Utility class to parse some RDF resource(s) and count hash collisions using a variety of hash codes.
InlineFixedWidthIntegerURIHandler	Utility IV to generate IVs for URIs in the form of http://example.org/value/0000513 where the localName is in integer printed with fixed width padding.
InlineHexUUIDURIHandler	Inline URI Handler to handle URI's in the form of a Hex UUID such as:
InlineIntegerURIHandlerMap	Utility to provide a map of multiple inline URI handlers for a single namespace.
InlineIPv4URIHandler	Inline URI handler for IPv4 host addresses.
InlineLocalNameIntegerURIHandler	Abstract class that defines the integer packing needed to allow for support of multiple inline integer URI handlers with the same namepace.
InlineNamespaceMultiURIHandler	A container URIHandler that handles multiple inline URI possibilities for a given namespace.
InlinePrefixedFixedWidthIntegerURIHandler	Utility IV to generate IVs for URIs in the form of http://example.org/value/STRPREFIX1234234513 where the localName of the URI is a string prefix followed by an integer value with fixed width.
InlinePrefixedIntegerURIHandler	Utility IV to generate IVs for URIs in the form of http://example.org/value/STRPREFIX1234234513 where the localName of the URI is a string prefix followed by an integer value.
InlinePrefixedSuffixedFixedWidthIntegerURIHandler	Utility IV to generate IVs for URIs in the form of http://example.org/value/STRPREFIX1234234513STRSUFFIX where the localName of the URI is a string prefix followed by a fixed width integer value followed by a string suffix.
InlinePrefixedSuffixedHexUUIDURIHandler	Inline URI Handler to handle URI's in the form of a Hex UUID with a prefix and suffix such as:
InlinePrefixedSuffixedIntegerURIHandler	Utility IV to generate IVs for URIs in the form of http://example.org/value/STRPREFIX1234234513STRSUFFIX where the localName of the URI is a string prefix followed by an integer value followed by a string suffix.
InlinePrefixedSuffixedUUIDURIHandler	Inline URI Handler to handle URI's in the form of a UUID with a prefix and a suffix such as:
InlineSignedIntegerURIHandler	Simple InlineURIHandler that packs the localName portion of the URI into an appropriately sized signed integer.
InlineSuffixedFixedWidthIntegerURIHandler	Utility IV to generate IVs for URIs in the form of http://example.org/value/1234234513STRSUFFIX where the localName of the URI is a string suffix followed by an integer value with fixed width.
InlineSuffixedHexUUIDURIHandler	Inline URI Handler to handle URI's in the form of a Hex UUID with a suffix such as:
InlineSuffixedIntegerURIHandler	Utility IV to generate IVs for URIs in the form of http://example.org/value/STRPREFIX1234234513 where the localName of the URI is a string prefix followed by an integer value.
InlineSuffixedUUIDURIHandler	Inline URI Handler to handle URI's in the form of a UUID with a suffix such as:
InlineUnsignedIntegerURIHandler	Simple InlineURIHandler that packs the localName portion of the URI into an appropriately sized signed integer.
InlineURIFactory	Default implementation of IInlineURIFactory that comes pre-loaded with two handlers: IPv4 (InlineIPv4URIHandler) UUID (InlineUUIDURIHandler You MAY declare additional handlers.
InlineURIHandler	Handler is mapped to a namespace prefix.
InlineUUIDURIHandler	Inline URI handler for UUIDs.
IPv4Address	Class models an IPv4 address.
IVUnicode	Utility class supporting IVs having inline Unicode data.
IVUnicode.IVUnicodeComparator	Class imposes the natural ordering of the encoded Unicode representation for an IV having inline Unicode data on Java Strings.
IVUtility	Helper class for IVs.
LexiconConfiguration<V extends BigdataValue>	An object which describes which kinds of RDF Values are inlined into the statement indices and how other RDF Values are coded into the lexicon.
MultipurposeIDHandler	Inline URI handler for IDs of multiple types.
NoExtensionFactory	A class which does not support any extensions.
NoInlineURIFactory	Do-nothing inline URI factory used in the case where there is no vocabulary defined.
ParserSpeedTest	Utility to measure the raw speed of the RDF parser.
SampleExtensionFactory	Simple IExtensionFactory implementation that creates two IExtensions - the EpochExtension and the ColorsEnumExtension.
TermIVComparator	Places BigdataValues into an ordering determined by their assigned IVs (internal values).
TestAll	Aggregates test suites into increasing dependency order.
TestBlobIV	Unit tests for BlobIV.
TestDTE	Test suite for DTE
TestDTEFlags	Test suite for DTEFlags.
TestEncodeDecodeGeoSpatialLiteralIVs	Unit tests for GeoSpatialLiteralExtension.
TestEncodeDecodeIPv4AddrIV	Encode/decode unit tests for IPv4AddrIV.
TestEncodeDecodeKeys	Unit tests for encoding and decoding compound keys (such as are used by the statement indices) in which some of the key components are inline values having variable component lengths while others are term identifiers.
TestEncodeDecodeLiteralArrayIVs	Encode/decode unit tests for LiteralArrayIV.
TestEncodeDecodeMixedIVs	Test of encode/decode and especially comparator semantics for mixed IVs.
TestEncodeDecodePackedLongIVs	Unit tests for PackedLongIV and its associated CompressedTimestampExtension extension.
TestEncodeDecodeUnicodeIVs	Unit tests for IVs which inline Unicode data.
TestEncodeDecodeXSDDateIVs	Unit tests for XSDIntegerIV.
TestEncodeDecodeXSDDecimalIVs	Unit tests for XSDDecimalIV.
TestEncodeDecodeXSDIntegerIVs	Unit tests for XSDIntegerIV.
TestFullyInlineTypedLiteralIV	Test suite for FullyInlineTypedLiteralIV.
TestFullyInlineURIIV	Test suite for FullyInlineURIIV.
TestInlineLocalNameIntegerURIHandler
TestInlineURIHandlers	Test suite for URIExtensionIV.
TestIVUnicode	Test suite for IVUnicode.
TestLiteralDatatypeIV	Test suite for PartlyInlineTypedLiteralIV.
TestMultiInlineURIHandlersSingleNamespace	Test case for multiple InlineURIHandlers at a single namespace.
TestPackedLongIVs	Test suite for math operations on PackedLongIV and CompressedTimestampExtension.
TestTermIV	Test suite for TermId.
TestUnsignedIntegerIVs	Test suite for xsd:nonPositiveInteger, xsd:negativeInteger, xsd:nonNegativeInteger, and xsd:positiveInteger.
TestUnsignedIVs	Test suite for the xsd:unsigned IV which are internally represented by Java primitives (xsd:unsignedByte, xsd:unsignedShort, xsd:unsignedInt, and xsd:unsignedLong).
TestURIExtensionIV	Test suite for URIExtensionIV.
TestURIExtensionIV.MockVocabulary
TestVocabURIByteIV
TestVTE	Test suite for VTE.
TestXPathFunctions	Test suite for various xpath numeric functions.
TestZOrderRangeScanUtility	Test for utility functionalities required for zOrder index construction, such as ZOrderRangeScanUtil.
XPathMathFunctions	Support for the picky xpath math functions: abs, ceiling, floor, and round.
XSD	Collects various XSD URIs as constants.

Enum Summary

Enum	Description
ColorsEnumExtension.Color	Simple demonstration enum for some common colors.
DTE	Data Type Enumeration (DTE) is a class which declares the known intrinsic data types, provides for extensibility to new data types, and provides for data types which either can not be inlined or are not being inlined.
DTEExtension	An extension of the intrinsic types defined by DTE.
VTE	Value Type Enumeration (IVTE) is a class with methods for interpreting and setting the bit flags used to identify the type of an RDF Value (URI, Literal, Blank Node, SID, etc).

Exception Summary

Exception	Description
NoSuchVocabularyItem	An exception thrown when a request is made for a URI which was not declared in the Vocabulary.
NotMaterializedException	Exception thrown by IVCache.getValue() if the IV has not first been cached using IVCache.asValue(LexiconRelation).

Package com.bigdata.rdf.internal Description

This package provides an internal representation of RDF Values. The internal representation of an RDF Value is either a term identifier or an inline value. Term identifiers are assigned by consistent writes on the TERM2ID index and the ID2TERM index (which maps the term identifier back onto the RDF Value). Inline values directly code the RDF Value and are generally used for datatype literals having short values (xsd:boolean, xsd:char) or numeric values (xsd:short, xsd:int, xsd:float, xsd:long, xsd:double).

The unsigned byte[] keys for an RDF Value are formed by appending some bit flags which partition the key space into URIs, blank nodes, literals, and statement identifiers, a bit flag indicating whether the value is inline, followed by either pad bits and the term identifier or a code which identifies the data type of the inline value and minimum length decodable representation of the data type value formed using IKeyBuilder. This design clusters different kinds of RDF values within different regions of the ID2TERM index.

Inline values have a significant performance advantage since the RDF Value object can be recovered directly from the inline value without indirection through the ID2TERM index. This reduces the costs to materialize RDF Values, greatly speeds up aggregation style queries over numeric data, and reduces both the maintenance time and the size on the disk for the lexicon indices since inline values are not entered into the lexicon.

Inline values also make it possible to translate a LT/GT style filter against an inlined datatype into key-range queries against the OSP(C) index. Since the inline values for different numeric data types are located in different parts of the key space, the use of a cast in the query will require either than key-range queries are issued against all numeric data types (UNION of access paths) or that the query is evaluated without the use of key-range scans on OSP(C).

RDF Values which are inlined obey the equality and order semantics of their value space (think xsd:int). One consequence of this is that comparison of inlined datatype literals MUST occur in the value space. E.g., 005 and 5 represent the same point in the xsd:int value space. Clients should be aware of this distinction as statements which have lexical distinctions which are not distinct in the value space will be mapped onto the same statement internally.