| Interface and Description |
|---|
| com.bigdata.rdf.spo.ISPOBuffer
by
IBuffer |
| com.bigdata.relation.rule.IStarJoin
This is not currently supported. It was implemented, but we did
not find improved performance for it.
|
| com.bigdata.bop.controller.SubqueryJoinAnnotations
With
SubqueryOp, which is the sole class which extends
this interface. |
| Class and Description |
|---|
| com.bigdata.rdf.inf.AbstractSPOBuffer
by
AbstractArrayBuffer, but this class is more tightly
coupled to the AbstractTripleStore. |
| com.bigdata.relation.accesspath.AccessPathFusedView
by
BOps using the UNION of JOINs. However, also note that
this is only used for TM and that the focus store is always local
for TM. |
| com.bigdata.journal.DiskOnlyStrategy
This has been replaced by
WORMStrategy. |
| com.bigdata.striterator.DistinctFilter |
| com.bigdata.rdf.spo.DistinctSPOIterator
By a simple distinct filter and a filter which strips off the
context position from an SPOC. Stack them together and it does
the same thing. (The fall back to the B+Tree might still be
interesting if we do not have a persistent hash map to fall back
on instead and we want streaming results. Otherwise use an
external merge sort.)
|
| com.bigdata.io.FileLockUtility |
| com.bigdata.cache.HardReferenceGlobalLRU
This implementation is not used.
|
| com.bigdata.util.HybridTimestampFactory
This class has not been fully debugged and SHOULD NOT be used.
|
| com.bigdata.net.InetAddressUtil
this was a red herring.
|
| com.bigdata.rdf.inf.JustificationIterator
replace with appropriate access path reading on the
justifications index for SPORelation (or treat as a secondary
relation).
|
| com.bigdata.concurrent.LockManager
This implementation manages locks in terms of threads. A thread
is required in order for a task to contend for its locks. This
places a strain on the thread scheduler.
|
| com.bigdata.util.concurrent.MappedTaskExecutor
by
LatchedExecutorService which has higher throughput and
plays more nicely with the Executor paradigm. |
| com.bigdata.util.httpd.NanoHTTPD
This is being replaced by the use of the Servlet API and embedded
use of jetty as a light weight servlet container.
|
| com.bigdata.bop.joinGraph.PartitionedJoinGroup
by
StaticAnalysis_CanJoin which is a port of this code to
the AST mode. |
| com.bigdata.relation.RelationFusedView
by
BOps using the UNION of JOINs. However, also note that
this is only used for TM and that the focus store is always local
for TM. |
| com.bigdata.jini.start.config.RoundRobinServiceConstraint
I think that we may get the right behavior naturally and it is
difficult to construct otherwise.
|
| com.bigdata.relation.rule.eval.RunRuleAndFlushBufferTaskFactory
This is now handled by
MutationTask.newMutationTasks(com.bigdata.relation.rule.IStep, IJoinNexus, java.util.Map) |
| com.bigdata.rdf.sparql.ast.SolutionSetStats
by
SolutionSetStatserator since the latter can compute
all of the same information can be used over streaming solution
sets. |
| com.bigdata.rdf.spo.SPOArrayIterator
by
ChunkedArrayIterator but this still has some very
purpose specific uses mainly dealing with
TruthMaintenance and with fully buffering precisely
because the DB impl is not using concurrency controls. |
| com.bigdata.rdf.inf.SPOAssertionBuffer
by
AbstractElementBuffer.InsertBuffer and AbstractSolutionBuffer.InsertSolutionBuffer and the
changes to how truth maintenance is handled (by rule rewrites). |
| com.bigdata.rdf.inf.SPORetractionBuffer
by
AbstractElementBuffer.DeleteBuffer and AbstractSolutionBuffer.DeleteSolutionBuffer and the
changes to how truth maintenance is handled (rule rewrites). |
| com.bigdata.rdf.spo.StatementWriter
by
SPORelation.insert(IChunkedOrderedIterator)? (Still
used by copyStatements) |
| com.bigdata.bop.controller.SubqueryOp
This operator is no longer in use. The last use case which we had
for this was in support of ASK subquery evaluation for (NOT)
EXISTS.
It is possible that another use case MIGHT be found to support parallel evaluation of named subqueries. However, that also might be handled by a thread pool if we move to interleaved query plan generation and query plan evaluation in support of the RTO. |
| com.bigdata.rdf.sparql.ast.ZeroLengthPathNode
Does not work - leads to cardinality problems.
|
| com.bigdata.bop.paths.ZeroLengthPathOp
Does not work. Leads to cardinality problems.
|
| Field and Description |
|---|
| com.bigdata.service.jini.master.TaskMaster.ConfigurationOptions.AGGREGATORS_TEMPLATE
This is a trial feature which is not fully implemented.
|
| com.bigdata.relation.AbstractResource.Options.CHUNK_CAPACITY
by
BOp annotations. |
| com.bigdata.relation.AbstractResource.Options.CHUNK_OF_CHUNKS_CAPACITY
by
BOp annotations. |
| com.bigdata.relation.AbstractResource.Options.CHUNK_TIMEOUT
by
BOp annotations. |
| com.bigdata.relation.AbstractResource.Options.DEFAULT_CHUNK_CAPACITY
by
BOp annotations. |
| com.bigdata.relation.AbstractResource.Options.DEFAULT_CHUNK_OF_CHUNKS_CAPACITY
by
BOp annotations. |
| com.bigdata.relation.AbstractResource.Options.DEFAULT_CHUNK_TIMEOUT
by
BOp annotations. |
| com.bigdata.relation.AbstractResource.Options.DEFAULT_FORCE_SERIAL_EXECUTION
by
BOp annotations. |
| com.bigdata.relation.AbstractResource.Options.DEFAULT_FULLY_BUFFERED_READ_THRESHOLD
by
BOp annotations. |
| com.bigdata.relation.AbstractResource.Options.DEFAULT_MAX_PARALLEL_SUBQUERIES
by
BOp annotations. |
com.bigdata.journal.Options.FILE_LOCK_ENABLED
FileLockUtility is going away since advisory locks
are not automatically removed if an application dies. |
| com.bigdata.relation.AbstractResource.Options.FORCE_SERIAL_EXECUTION
by
BOp annotations. |
| com.bigdata.relation.AbstractResource.Options.FULLY_BUFFERED_READ_THRESHOLD
by
BOp annotations. |
| com.bigdata.resources.OverflowManager.Options.HOT_SPLIT_THRESHOLD
Hot splits are not implemented and this option does not
do anything. It will be going away soon.
|
| com.bigdata.LRUNexus.Options.LIMITING_CAPACITY
At the moment, this option is only understood by the
BCHMGlobalLRU. The option may or may not survive
as that feature is alpha. |
| com.bigdata.jini.start.BigdataZooDefs.MASTER_ELECTION
by
BigdataZooDefs.QUORUM. The leader of a met quorum is
the first child of quorum/joined>. |
| com.bigdata.mdi.LocalPartitionMetadata.MAX_HISTORY_LENGTH |
| com.bigdata.relation.AbstractResource.Options.MAX_PARALLEL_SUBQUERIES
by
BOp annotations. |
| com.bigdata.resources.OverflowManager.Options.MAXIMUM_JOURNALS_PER_VIEW
merges are now performed in priority order while time
remains in a given asynchronous overflow cycle.
|
| com.bigdata.resources.OverflowManager.Options.MAXIMUM_MOVES
Moves are now decided on a case by case basis. An
alternative parameter might be introduced in the future
to restrict the rate at which a DS can shed shards by
moving them to other nodes.
|
| com.bigdata.resources.OverflowManager.Options.MAXIMUM_MOVES_PER_TARGET
Moves are now decided on a case by case basis. An
alternative parameter might be introduced in the future
to restrict the rate at which a DS can shed shards by
moving them to other nodes.
Note: This is also used to disable moves by some of the unit tests so we need a way to replace that functionality before this can be taken out. |
| com.bigdata.resources.OverflowManager.Options.MAXIMUM_OPTIONAL_MERGES_PER_OVERFLOW
merges are now performed in priority order while time
remains in a given asynchronous overflow cycle.
|
| com.bigdata.resources.OverflowManager.Options.MAXIMUM_SEGMENTS_PER_VIEW
merges are now performed in priority order while time
remains in a given asynchronous overflow cycle.
|
| com.bigdata.resources.OverflowManager.maximumJournalsPerView
merges are now performed in priority order while time remains
in a given asynchronous overflow cycle.
|
| com.bigdata.resources.OverflowManager.maximumMoves
Moves are now decided on a case by case basis. An alternative
parameter might be introduced in the future to restrict the
rate at which a DS can shed shards by moving them to other
nodes.
|
| com.bigdata.resources.OverflowManager.maximumMovesPerTarget
Moves are now decided on a case by case basis. An alternative
parameter might be introduced in the future to restrict the
rate at which a DS can shed shards by moving them to other
nodes.
Note: This is also used to disable moves by some of the unit tests so we need a way to replace that functionality before this can be taken out. |
| com.bigdata.resources.OverflowManager.maximumOptionalMergesPerOverflow
merges are now performed in priority order while time remains
in a given asynchronous overflow cycle.
|
| com.bigdata.resources.OverflowManager.maximumSegmentsPerView
merges are now performed in priority order while time remains
in a given asynchronous overflow cycle.
|
| com.bigdata.service.jini.master.TaskMaster.ConfigurationOptions.NAGGREGATORS
This is a trial feature which is not fully implemented.
|
| com.bigdata.resources.OverflowManager.Options.OVERFLOW_CANCELLED_WHEN_JOURNAL_FULL
Asynchronous overflow processing should run to completion
with a minimum goal of an incremental build for each
index partition having data on the previous journal.
|
| com.bigdata.resources.OverflowManager.Options.OVERFLOW_MAX_COUNT
This is no longer used, even for testing.
|
| com.bigdata.resources.OverflowManager.Options.OVERFLOW_TASKS_CONCURRENT |
| com.bigdata.resources.OverflowManager.Options.OVERFLOW_TIMEOUT
Asynchronous overflow processing should run to completion
with a minimum goal of an incremental build for each
index partition having data on the previous journal.
|
| com.bigdata.resources.OverflowManager.overflowTasksConcurrent |
| com.bigdata.service.jini.JiniClientConfig.Options.PROPERTIES
This is used by the
JiniClient, not the
JiniClientConfig. It's presents on this interface
is therefore confusing. It should be moved to the
JiniClient.Options. This symbolic constant can
show up in Configuration files, so we probably
need to leave in a reference here to redirect people to
the JiniClient.Options interface.
The historical presence of this property on the
|
| com.bigdata.BigdataStatics.threadLocalBuffers
This is ugly. Remove once the issue has been resolved.
|
| Method and Description |
|---|
| com.bigdata.htree.HTree.activeBucketPages() |
| com.bigdata.htree.HTree.activeDirectoryPages() |
| com.bigdata.rdf.spo.ISPOAssertionBuffer.add(SPO, Justification) |
| com.bigdata.rdf.store.IRawTripleStore.addStatements(IChunkedOrderedIterator |
| com.bigdata.relation.rule.IAccessPathExpander.backchain()
Never
true. The backchainer is only run for
normal predicates in triples mode at this time. If it is to
be layer, it should be layered as an annotation. See
https://sourceforge.net/apps/trac/bigdata/ticket/231. |
| com.bigdata.relation.rule.eval.IJoinNexus.bind(IRule, int, Object, IBindingSet)
by
#bind(IPredicate, Object, IBindingSet) |
| com.bigdata.jini.start.config.ServiceConfiguration.concat(T[], T[])
Use
ConfigMath#concat(T[],T[]) instead |
| com.bigdata.bop.engine.QueryEngine.declareQuery(IQueryDecl) |
| com.bigdata.bop.engine.IQueryPeer.declareQuery(IQueryDecl)
This method is unused and will probably disappear. The nodes
in a cluster reach back to the query controller using
IQueryClient.getQuery(UUID) to resolve the query on
its first reference. This is handled by the
FederatedQueryEngine within its run() loop where it
accepts IChunkMessages. |
| com.bigdata.bop.fed.FederatedQueryEngine.declareQuery(IQueryDecl) |
| com.bigdata.btree.NodeSerializer.encode(IAbstractNodeData)
This method is no longer used since I refactored the
IndexSegmentBuilder to optionally stuff the generated
nodes and leaves into the cache. It still works but it might
go away in the future. |
| com.bigdata.htree.NodeSerializer.encode(IAbstractNodeData)
This method is no longer used since I refactored the
IndexSegmentBuilder to optionally stuff the generated
nodes and leaves into the cache. It still works but it might
go away in the future. |
| com.bigdata.rdf.sail.BigdataSail.BigdataSailConnection.evaluate(QueryRoot, Dataset, BindingSet, boolean)
Consider removing this method from our public API. It is
no longer in any code path for the bigdata code base.
Embedded applications requiring high level evaluation
should use
BigdataSailRepositoryConnection. It
does not call through here, but goes directly to the
ASTEvalHelper. |
| com.bigdata.relation.rule.eval.IJoinNexus.forceSerialExecution()
by bop annotations.
|
| com.bigdata.bop.IPredicate.get(E, int)
by
IElement.get(int) which does exactly what this
method is trying to do. |
| com.bigdata.rdf.store.IRawTripleStore.getAccessPath(IKeyOrder by
SPORelation#getAccessPath(SPOKeyOrder, com.bigdata.relation.rule.IPredicate) |
| com.bigdata.rdf.spo.SPORelation.getAccessPath(IV, IV, IV) |
| com.bigdata.rdf.store.IRawTripleStore.getAccessPath(IV, IV, IV) |
| com.bigdata.rdf.sail.BigdataSailUpdate.getActiveDataset() |
| com.bigdata.util.ChecksumUtility.getCHK() |
| com.bigdata.relation.AbstractResource.getChunkCapacity()
by
BOp annotations. |
| com.bigdata.relation.rule.eval.IJoinNexus.getChunkCapacity()
by bop annotations.
|
| com.bigdata.relation.AbstractResource.getChunkOfChunksCapacity()
by
BOp annotations. |
| com.bigdata.relation.rule.eval.IJoinNexus.getChunkOfChunksCapacity()
by bop annotations.
|
| com.bigdata.relation.AbstractResource.getChunkTimeout()
by
BOp annotations. |
| com.bigdata.rdf.sail.sparql.ast.JavaCharStream.getColumn() |
| com.bigdata.btree.DefaultTupleSerializer.getDefaultKeyBuilderFactory() |
| com.bigdata.btree.DefaultTupleSerializer.getDefaultLeafKeysCoder() |
| com.bigdata.btree.DefaultTupleSerializer.getDefaultValuesCoder() |
| com.bigdata.relation.AbstractResource.getFullyBufferedReadThreshold()
by
BOp annotations. |
| com.bigdata.relation.rule.eval.IJoinNexus.getFullyBufferedReadThreshold()
by bop annotations.
|
| com.bigdata.gom.om.IObjectManager.getID()
Why do we need this? It should be hidden in how we generate
URIs, not part of the public API.
|
| com.bigdata.relation.IRelation.getIndexNames()
by
IRelation.getKeyOrders(). However, note that some odd ball
cases exist such as the free text index of the
LexiconRelation and the justifications index of the
SPORelation. These are currently enumerated by
IRelation.getIndexNames() but they are not enumerated by
IRelation.getKeyOrders() since they are not a simple
transform of the original relation. |
| com.bigdata.rdf.lexicon.LexiconRelation.getIV(Value)
Not even the unit tests should be doing this.
|
| com.bigdata.rdf.store.IRawTripleStore.getIV(Value)
This is only used by the unit tests. It is not efficient for
scale-out.
|
| com.bigdata.rdf.store.AbstractTripleStore.getIV(Value)
Not even the unit tests should be doing this.
|
| com.bigdata.rdf.spo.ISPOAssertionBuffer.getJustificationCount()
not used.
|
| com.bigdata.btree.proc.IKeyArrayIndexProcedure.getKey(int) |
| com.bigdata.btree.proc.IKeyArrayIndexProcedure.getKeyCount() |
| com.bigdata.rdf.sail.sparql.ast.JavaCharStream.getLine() |
| com.bigdata.relation.AbstractResource.getMaxParallelSubqueries()
by
BOp annotations. |
| com.bigdata.relation.rule.eval.IJoinNexus.getMaxParallelSubqueries()
by bop annotations.
|
| com.bigdata.gom.om.IObjectManager.getNames() |
| com.bigdata.htree.HTree.getPageInfo() |
| com.bigdata.service.ndx.PartitionedTupleIterator.getPartitionCount()
The #of partitions is a bit tricky since splits and joins can
introduce new partitions unless you are using a
read-consistent view.
|
| com.bigdata.rdf.sparql.ast.StaticAnalysis.getPruneFilters(JoinGroupNode)
This is now handled by
ASTBottomUpOptimizer. I think
that we will not need this method (it is only invoked from
the test suite at this point). |
| com.bigdata.bop.engine.IChunkMessage.getQueryController()
This forces us to serialize and send the proxy for the query
controller on a cluster. The message format is slimmer if we
instead rely on resolution of
IChunkMessage.getQueryControllerId()
against a service discovery cache.
We can not discover the query controller using river because it is not registered as a service. We can find the query peers on the data service nodes easily enough because they are all registered with river. However, the QueryEngine serving as the query controller is not currently registered with river and hence it can not be discovered using the UUID of the query controller alone. Probably the right thing to do is to register the query controller with river so it can be discovered. We could then modify getQueryPeer() (or add getQueryClient(UUID)) which would hit the discovery cache. |
| com.bigdata.ha.halog.HALogWriter.getReader()
Use
HALogWriter.getReader(long). That code can make an atomic
decision about whether the current HALog is being request or
a historical HALog. It is not possible for the caller to make
this decision from the outside. |
| com.bigdata.bop.IPredicate.getRelationCount() |
| com.bigdata.bop.IPredicate.getRelationName(int)
Unions of predicates must be handled explicitly as a union of
pipeline operators reading against the different predicate.
|
| com.bigdata.rdf.sparql.ast.StaticAnalysisBase.getRequiredNamedSubqueryRoot(String)
Caller's MUST BE CHANGED to look for both a
NamedSubqueryRoot and an ISolutionSetStats
and then handle these as appropriate. In one case, that means
static analysis of the NamedSubqueryRoot. In the
other, the relevant information are present in pre-computed
metadata on the ISolutionSetStats. |
| com.bigdata.btree.proc.AbstractKeyArrayIndexProcedure.ResultBuffer.getResult(int) |
| com.bigdata.btree.proc.AbstractKeyArrayIndexProcedure.ResultBuffer.getResultCount() |
| com.bigdata.relation.rule.eval.IJoinNexus.getRuleTaskFactory(boolean, IRule)
by annotations on individual
BOps which specify which
join operator is to be used on a join by join basis. |
| com.bigdata.mdi.LocalPartitionMetadata.getSourcePartitionId()
MoveTask manages without this field (it was required by the
previous MOVE implementation).
|
| com.bigdata.rdf.spo.SPORelation.getSPOOnlyBTree(boolean)
Comment out when we drop the
DistinctSPOIterator. |
| com.bigdata.rdf.store.IRawTripleStore.getStatement(IV, IV, IV)
does not support quads.
|
| com.bigdata.btree.raba.codec.CanonicalHuffmanRabaCoder.getSumCodedValueBitLengths(BitVector[], IRaba, CanonicalHuffmanRabaCoder.Byte2Symbol)
Leave this field and the #of bits per codedValueOffset[]
element blank until we have written out the coded values and
then rewind the OBS and fill in those fields. Otherwise we
are encoding the same byte[][] data twice, which is wasted
effort.
|
| com.bigdata.btree.proc.IKeyArrayIndexProcedure.getValue(int) |
| com.bigdata.bop.IPredicate.getVariableCount()
This is only used in a few places, which should probably use
BOpUtility.getArgumentVariableCount(BOp) instead. |
| com.bigdata.rdf.store.AbstractTripleStore.hasStatement(IV, IV, IV) |
| com.bigdata.relation.AbstractResource.isForceSerialExecution()
by
BOp annotations. |
| com.bigdata.util.httpd.MIMEType.isWildcard()
Use
MIMEType.isSubtypeWildcard() instead. |
| com.bigdata.counters.linux.SysstatUtil.newDateFormat()
sysstat only reports the TIME OF DAY. In order to get the UTC
time it has to be corrected by the UTC time of the start of
the current day. Since very little latency is expected
between the report by sysstat of its performance counters and
the parsing of those performance counters by our code, it is
MUCH easier and more robust to simply use the current time as
reported by
System.currentTimeMillis(). |
| com.bigdata.btree.AbstractBTreeTupleCursor.newTemporaryPosition(AbstractBTreeTupleCursor.ICursorPosition This is never used.
|
| com.bigdata.journal.Journal.nextTimestamp()
This is here for historical reasons and is only used by the
test suite. Use
Journal.getLocalTransactionManager() and
ITimestampService.nextTimestamp(). |
| com.bigdata.resources.AsynchronousOverflowTask.putUsed(String, String)
This is no longer valid as many index partitions are entered
onto BOTH the buildQueue and the mergeQueue rather than
exclusively being assigned one task or the other.
|
| com.bigdata.btree.AbstractBTree.rangeCheck(byte[], boolean)
This method has been disabled. It always returns true.
The method is disabled because it forces the caller to ensure
that the query lies within the specified range. While that is
all well and good, this places an undue burden on
|
| com.bigdata.io.FileChannelUtility.readAll(FileChannel, ByteBuffer, long)
by
FileChannelUtility.readAll(IReopenChannel, ByteBuffer, long) which
handles transparent re-opening of the store in order to
complete the read operation. |
| com.bigdata.gom.om.ObjectMgrModel.recall(URI) |
| com.bigdata.gom.om.IObjectManager.recall(URI) |
| com.bigdata.gom.om.ObjectMgrModel.recallAsGPO(URI) |
| com.bigdata.journal.AbstractJournal.registerIndex(String, IndexMetadata) |
| com.bigdata.gom.om.ObjectMgrModel.save(URI, Value) |
| com.bigdata.gom.om.IObjectManager.save(URI, Value) |
| com.bigdata.rdf.sail.BigdataSailUpdate.setDataset(Dataset) |
| com.bigdata.bop.IPredicate.setRelationName(String[])
This will be modified to use a scalar relation name per
IPredicate.getOnlyRelationName(). |
| com.bigdata.rdf.store.IRawTripleStore.toString(IV, IV, IV) |
| com.bigdata.counters.render.XHTMLRenderer.value(ICounter, Object)
Move into formatter objects.
|
| com.bigdata.io.FileChannelUtility.writeAll(FileChannel, ByteBuffer, long) |
| com.bigdata.counters.render.XHTMLRenderer.writeFullPath(Writer, String)
by refactor inside of a rendering object.
|
| com.bigdata.counters.render.XHTMLRenderer.writePath(Writer, String, int)
by refactor inside of a rendering object.
|
| Constructor and Description |
|---|
| com.bigdata.rdf.store.TempTripleStore(Properties)
by
TempTripleStore.TempTripleStore(TemporaryStore, Properties, AbstractTripleStore)
which permits you to reuse the same backing
TemporaryStore instance until it becomes full. |
| com.bigdata.rdf.store.TempTripleStore(Properties, AbstractTripleStore)
Use
TempTripleStore.TempTripleStore(TemporaryStore, Properties, AbstractTripleStore)
instead and provide the TemporaryStore reference
returned by IIndexStore.getTempStore(). This has the
advantage of reusing a single shared TemporaryStore
instance until it becomes "large" and then allocating a new
instance (note that each instance will consume a direct
ByteBuffer from the DirectBufferPool). This
is especially important for operations like
TruthMaintenance which have to create a lot of
temporary stores. |
| com.bigdata.rdf.sparql.ast.ValueExpressionNode(IValueExpression)
This was just for compatibility with SOp2ASTUtility. It is
only used by the test suite now. It should be removed now
that we are done with the SPARQL to AST direct translation.
|
| Enum Constant and Description |
|---|
| com.bigdata.resources.OverflowSubtaskEnum.CopyHistory
by
MoveTask |
| com.bigdata.resources.OverflowSubtaskEnum.SendIndexSegment
by
MoveTask |
Copyright © 2006-2012 SYSTAP, LLC. All Rights Reserved.