| Interface and Description |
|---|
| com.bigdata.bfs.IContentRepository
This is part of the BFS support.
|
| com.bigdata.ha.msg.IHAGlobalWriteLockRequest |
| 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.
|
| 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.rdf.sparql.ast.optimizers.ASTComplexOptionalOptimizer |
| com.bigdata.rdf.sparql.ast.optimizers.ASTJoinOrderByTypeOptimizer |
| com.bigdata.rdf.sail.BigdataSailHelper
The workbench provides configuration guidance. This class also
provides some support for people who want to modify some
properties after a namespace has been created. This is in fact
possible for some kinds of properties but not for others, but
there is very little documentation about when this is and is not
possible. You need to actually understand and reason about
whether the property controls the manner in which the data is
stored on the disk or whether it simply controls the runtime
behavior in a manner that does not impact the disk storage.
|
| com.bigdata.search.DefaultAnalyzerFactory
Using
ConfigurableAnalyzerFactory with
the ConfigurableAnalyzerFactory.Options.NATURAL_LANGUAGE_SUPPORT
uses the appropriate natural language analyzers for the two letter codes
and for tags which include sub-tags. |
| 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.rdf.vocab.decls.GeoSpatialVocabularyDecl |
| com.bigdata.ha.msg.HAGlobalWriteLockRequest |
| 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.internal.encoder.IVBindingSetEncoderWithIVCache |
| 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.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.service.TestCase3
This is currently duplicating a class by the same name in
com.bigdata.io in the JOURNAL_HA_BRANCH. Those classes should be
reconciled.
I have added |
| com.bigdata.journal.TestDiskJournal |
| com.bigdata.rdf.internal.encoder.TestIVBindingSetEncoderWithCache |
| com.bigdata.journal.TestRollbackCommit
Along with
AbstractJournal.rollback() |
| com.bigdata.rdf.sparql.ast.eval.rto.TestRTO_FOAF
None of these test queries are complicated enough to trigger the
RTO. The class and its queries should just be dropped.
|
| com.bigdata.rdf.lexicon.TestSubjectCentricFullTextIndex
Feature was never completed due to scalability issues. See
BZLG-1548, BLZG-563.
|
| cern.colt.matrix.doublealgo.Transform |
| it.unimi.dsi.bits.Utf16TransformationStrategy |
| com.bigdata.rdf.sparql.ast.ZeroLengthPathNode
Does not work - leads to cardinality problems and can be removed.
Zero Length Paths are integrated into the ALP node /
ArbitraryLengthPathOp now.
|
| com.bigdata.bop.paths.ZeroLengthPathOp
Does not work. Leads to cardinality problems and can be removed.
Zero Length Paths are integrated into the ALP node /
ArbitraryLengthPathOp now.
|
| Field and Description |
|---|
| com.bigdata.util.httpd.Config.BIGDATA_PATH |
| 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.service.geospatial.GeoSpatial.DEFAULT_DATATYPE |
| 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.rwstore.RWStore.Options.DEFAULT_META_BITS_SIZE |
| com.bigdata.rdf.store.BDS.DEFAULT_PREFIX_MATCH
This option is now invoked using a wildcard.
|
| com.bigdata.rdf.store.AbstractTripleStore.Options.DEFAULT_SUBJECT_CENTRIC_TEXT_INDEX |
| com.bigdata.rdf.store.BDS.DEFAULT_SUBJECT_SEARCH |
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.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.rwstore.RWStore.Options.META_BITS_SIZE |
| it.unimi.dsi.logging.ProgressLogger.modulus
Replaced by
ProgressLogger.log2Modulus, which avoids the very slow modulus operator at each ProgressLogger.lightUpdate() call. |
| 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.rdf.store.BDS.PREFIX_MATCH
Prefix matching is now invoked using a wildcard.
|
| com.bigdata.btree.AbstractBTree.storeCache |
| com.bigdata.rdf.store.AbstractTripleStore.Options.SUBJECT_CENTRIC_TEXT_INDEX
Feature was never completed due to scalability issues.
See BZLG-1548, BLZG-563.
|
| com.bigdata.rdf.store.BDS.SUBJECT_SEARCH
Feature was never completed due to scalability issues. See
BZLG-1548, BLZG-563.
|
| com.bigdata.BigdataStatics.threadLocalBuffers
This is ugly. Remove once the issue has been resolved.
|
| Constructor and Description |
|---|
| com.bigdata.rdf.sail.remote.BigdataSailRemoteRepository(String) |
| com.bigdata.ha.msg.HAWriteMessage(UUID, long, long, long, int, int, StoreTypeEnum, long, long, long)
by the version that accepts the compressor key.
|
| 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–2019 SYSTAP, LLC DBA Blazegraph. All rights reserved.