-
com.alibaba.daybits.DayBits.explain()
-
com.browseengine.bobo.api.BoboBrowser.explain()
-
com.browseengine.bobo.query.scoring.BoboDocScorer.explain()
-
com.mongodb.DBCursor.explain()
Returns an object containing basic information about the execution of the query that created this cursor This creates a DBObject
with the key/value pairs: "cursor" : cursor type "nScanned" : number of records examined by the database for this query "n" : the number of records that the database returned "millis" : how long it took the database to execute the query
@return a DBObject
@dochub explain
-
com.salesforce.phoenix.iterate.ResultIterator.explain()
-
mondrian.spi.ProfileHandler.explain()
Called when a statement has finished executing.
@param plan Annotated plan
@param timing Query timings
-
net.sf.saxon.query.XQueryExpression.explain()
Diagnostic method: display a representation of the compiled query on the selected output stream.
@param out an ExpressionPresenter to which the XML representation of the compiled querywill be sent
-
nux.xom.xquery.XQuery.explain()
Returns a description of the compiled and optimized expression tree; useful for advanced performance diagnostics only.
@return a string description
-
org.apache.lucene.queries.function.FunctionValues.explain()
-
org.apache.lucene.search.IndexSearcher.explain()
Returns an Explanation that describes how
doc
scored against
query
.
This is intended to be used in developing Similarity implementations, and, for good performance, should not be displayed with every hit. Computing an explanation is as expensive as executing the query over the entire index.
-
org.apache.lucene.search.Rescorer.explain()
Explains how the score for the specified document was computed.
-
org.apache.lucene.search.Scorer.explain()
Returns an explanation of the score for a document.
When this method is used, the {@link #next()}, {@link #skipTo(int)} and{@link #score(HitCollector)} methods should not be used.
@param doc The document number for the explanation.
@deprecated Please use {@link IndexSearcher#explain}or {@link Weight#explain} instead.
-
org.apache.lucene.search.Searcher.explain()
Returns an Explanation that describes how
doc
scored against
query
.
This is intended to be used in developing Similarity implementations, and, for good performance, should not be displayed with every hit. Computing an explanation is as expensive as executing the query over the entire index.
-
org.apache.lucene.search.Weight.explain()
An explanation of the score computation for the named document.
@param context the readers context to create the {@link Explanation} for.
@param doc the document's id relative to the given context's reader
@return an Explanation for the score
@throws IOException if an {@link IOException} occurs
-
org.apache.lucene.search.similarities.Similarity.ExactSimScorer.explain()
-
org.apache.lucene.search.similarities.Similarity.SimScorer.explain()
-
org.apache.lucene.search.similarities.Similarity.SloppySimScorer.explain()
-
org.apache.phoenix.iterate.ResultIterator.explain()
-
org.apache.pig.PigServer.explain()
Provide information on how a pig query will be executed. For now this information is very developer focussed, and probably not very useful to the average user.
@param alias Name of alias to explain.
@param stream PrintStream to write explanation to.
@throws IOException if the requested alias cannot be found.
-
org.apache.pig.backend.executionengine.ExecPhysicalPlan.explain()
To provide an "explanation" about how the physical plan has been constructed
-
org.apache.pig.backend.hadoop.executionengine.mapReduceLayer.MapReduceLauncher.explain()
-
org.apache.pig.backend.hadoop.executionengine.physicalLayer.plans.PhysicalPlan.explain()
Write a visual representation of the Physical Plan into the given output stream
@param out : OutputStream to which the visual representation is written
-
org.apache.pig.impl.logicalLayer.LogicalPlan.explain()
-
org.apache.pig.newplan.logical.expression.LogicalExpressionPlan.explain()
-
org.apache.pig.newplan.logical.relational.LogicalPlan.explain()
-
org.elasticsearch.action.admin.cluster.reroute.ClusterRerouteRequest.explain()
Sets the explain flag, which will collect information about the reroute request without executing the actions. Similar to dryRun, but human-readable.
-
org.elasticsearch.action.admin.indices.validate.query.ValidateQueryRequest.explain()
Indicate if detailed information about query is requested
-
org.elasticsearch.search.builder.SearchSourceBuilder.explain()
Should each {@link org.elasticsearch.search.SearchHit} be returned with anexplanation of the hit (ranking).
-
org.elasticsearch.search.internal.ContextIndexSearcher.explain()
-
org.elasticsearch.search.rescore.Rescorer.explain()
Executes an {@link Explanation} phase on the rescorer.
@param topLevelDocId the global / top-level document ID to explain
@param context the explanation for the results being fed to this rescorer
@param rescoreContext context for this rescorer
@param sourceExplanation explanation of the source of the documents being fed into this rescore
@return the explain for the given top level document ID.
@throws IOException if an {@link IOException} occurs
-
org.epic.perleditor.views.ExplainErrorsView.explain()
-
org.hibernate.search.FullTextQuery.explain()
Return the Lucene {@link org.apache.lucene.search.Explanation}object describing the score computation for the matching object/document in the current query
@param documentId Lucene Document id to be explain. This is NOT the object id
@return Lucene Explanation
-
org.infinispan.query.CacheQuery.explain()
Return the Lucene {@link org.apache.lucene.search.Explanation}object describing the score computation for the matching object/document in the current query
@param documentId Lucene Document id to be explain. This is NOT the object key
@return Lucene Explanation
-
org.jzkit.search.SearchSessionFactory.explain()
-
org.voltdb.expressions.AbstractExpression.explain()
-
solver.explanations.ExplanationEngine.explain()
Provides an explanation for the removal of value val
from variable var
; the implementation is recording policy dependent for a flattened policy, the database is checked (automatically flattening explanations) for a non flattened policy, only the value removal is returned
@param var an integer variable
@param val an integer value
@return a deduction
-
solver.variables.Variable.explain()
returns an explanation of the current state of the Variable
@param what specifies what we are interested in
@param to explanation to feed