SailSource that does not respond to BackingSailSource.close() BackingSailSource.prepare() or
BackingSailSource.flush().SailSource.SailDataset is no longer is used, such as when a read operation is complete.SailDataset of the current state of this SailSource.SailSink will be visible
to subsequent SailSource.dataset(org.eclipse.rdf4j.IsolationLevel).SailSource, if applicable.SailSourceConnection to determine query join order.FederatedServiceResolver being used.ValueFactory that should be used in association with this.SailSink is committed, iff this was opened in an isolation level compatible with
IsolationLevels.SERIALIZABLE.SailSink is consistent with the isolation level it was created with.SailConflictException if SailSource.flush()ing
this branch would cause the backing SailSource to be inconsistent, if applicable.SailException on close.SailSource at a point in time that will remain consistent until SailDataset.close() is
called.SailConnection implementation that is based on an SailStore .SailConnection, using the given SailStore to manage the state.SailConnection, using the given SailStore to manage the state.SailSourceConnection to access SailSource.FederatedServiceResolver to use.SailSink that when when its SailSource.flush() is called, the changes are applied to
this source.SailStore wrapper that branches the backing SailSources to provide concurrent
IsolationLevels.SNAPSHOT_READ isolation and higher.SailStore, tracking changes in SailModelFactory instances.Copyright © 2015-2019 Eclipse Foundation. All Rights Reserved.