public interface ISolutionSet extends ICheckpointProtocol
ISolutionSetimplementations derived from
I am not sure that we will require this. We can probably use the
SolutionSetStream for named solution sets for quite a while
without supporting declaration of named solution sets with specific
join variables. However, if we do add support for this, then we need
to reconcile the
HTree version with the hash join code and
INamedSolutionSetRef and also add an
Stream backed solution sets so they can be
played out through a simple iterator model. The
relation specific, but it could be relayered to provide support for
BTree backed solution sets.
|Modifier and Type||Method and Description|
Replace the contents of the stream with the solutions read from the source.
Visit all entries in the index in the natural order of the index.
close, dumpPages, getCheckpoint, getDirtyListener, getIndexMetadata, getLastCommitTime, getMetadataAddr, getRecordVersion, getRootAddr, isOpen, reopen, setDirtyListener, setLastCommitTime, writeCheckpoint, writeCheckpoint2
getStore, rangeCount, removeAll
getReadLockCount, isReadOnly, readLock, writeLock
ISolutionSetStatsfor the saved solution set. This may be used for query planning and should not require the backing solutions to be materialized.
ICloseableIteratorreading the solutions from the stream.
void put(ICloseableIterator<IBindingSet> src)
src- The source.
Copyright © 2006–2019 SYSTAP, LLC DBA Blazegraph. All rights reserved.