| clear query|facets|time |
Search criteria: relevancy computation.
Results from 161 to 170 from
488 (5.892s).
|
|
|
Loading phrases to help you
refine your search...
|
|
Index (Lucene 4.2.0 API) - Lucene - [web site]
|
|
... in class org.apache.lucene.queries.CustomScoreProvider
Explain the custom score.
customScore(int, float, float[]) - Method in class org.apache.lucene.queries.CustomScoreProvider
Compute...
|
|
... a custom score by the subQuery score and a number of
FunctionQuery scores.
customScore(int, float, float) - Method in class org.apache.lucene.queries.CustomScoreProvider
Compute a custom...
|
[+ show more]
[- hide]
| ...).
Subclasses can modify the computation by overriding CustomScoreQuery.getCustomScoreProvider(org.apache.lucene.index.AtomicReaderContext).
CustomScoreQuery(Query) - Constructor for class org... |
|
|
http://lucene.apache.org/core/4_2_0/queries/index-all.html
2013-03-11, 05:47
|
|
|
Elasticsearch Date Histogram Facet » Elasticsearch - ElasticSearch - [web site]
|
|
.... It is possible to provide a time zone (both pre rounding, and post rounding) value, which will cause all computations to take the relevant zone into account. The time returned for each bucket...
|
|
... time setting like 1.5h (up to w for weeks).
Time Zone
By default, times are stored as UTC milliseconds since the epoch. Thus, all computation and “bucketing” / “rounding” is done on UTC...
|
[+ show more]
[- hide]
| ...: 2012-04-01T04:00:00Z. Note, we are consistent in the results, returning the rounded value in UTC.
post_zone simply takes the result, and adds the relevant offset.
Sometimes, we want to apply... |
| ... to change the value in the field to milliseconds to actual do the relevant rounding, and then be applied again to get to the original unit. For example, when storing in a numeric field seconds... |
| ... will then return the total and mean for that field values of the hits within the relevant bucket. For example:
{
"query" : {
"match_all" : {}
},
"facets" : {
"histo1... |
|
|
http://www.elasticsearch.org/guide/reference/api/s.../date-histogram-facet.html
|
|
|
Elasticsearch Search Type » Elasticsearch - ElasticSearch - [web site]
|
|
...
Search Type
There are different execution paths that can be done when executing a distributed search. The distributed search operation needs to be scattered to all the relevant...
|
|
... executing a distributed search is how much results to retrieve from each shard. For example, if we have 10 shards, the 1st shard might hold the most relevant results from 0 till 10, with other...
|
[+ show more]
[- hide]
| ... frequencies and other search engine information from the other shards. If we want to support accurate ranking, we would need to first execute the query against all shards and gather the relevant term... |
| ...
Parameter value: query_and_fetch.
The most naive (and possibly fastest) implementation is to simply execute the query on all relevant shards and return the results. Each shard returns size results... |
| ... is executed against all shards, but only enough information is returned (not the document content). The results are then sorted and ranked, and based on it, only the relevant shards are asked... |
|
|
http://www.elasticsearch.org/guide/reference/api/search/search-type.html
|
|
|
Index (Lucene 4.1.0 API) - Lucene - [web site]
|
|
....apache.lucene.search.grouping.AbstractGroupFacetCollector
setAllGroupHeads(boolean) - Method in class org.apache.lucene.search.grouping.GroupingSearch
Whether to compute all group heads (most relevant document per group) matching the query.
set...
|
|
....apache.lucene.search.grouping
This collector specializes in collecting the most relevant document (group head) for each group that match the query.
AbstractAllGroupHeadsCollector(int) - Constructor for class org...
|
[+ show more]
[- hide]
| ....apache.lucene.search.grouping.AbstractFirstPassGroupingCollector
Create the first pass collector.
AbstractGroupFacetCollector - Class in org.apache.lucene.search.grouping
Base class for computing grouped facets.
Abstract... |
| ... relevant document.
compare(int, int) - Method in class org.apache.lucene.search.grouping.function.FunctionAllGroupHeadsCollector.GroupHead
compIDXEnd - Variable in class org... |
| ...AllGroupHeadsCollector.GroupHead<?>> - Class in org.apache.lucene.search.grouping.dv
A base implementation of AbstractAllGroupHeadsCollector for retrieving
the most relevant groups when grouping on a indexed doc values field... |
|
|
http://lucene.apache.org/core/4_1_0/grouping/index-all.html
2013-01-22, 06:26
|
|
|
Facet Userguide - Lucene - [web site]
|
|
... a list of relevant price ranges; for the author facet, we get a list of
relevant authors; and so on. In most UIs, when users click one of these subcategories,
the search is narrowed, or drilled...
|
|
... in itself,
even when the user never drills down. This list allows the user to see at one glance
some statistics on the search results, e.g., what price ranges and which authors are
most relevant...
|
[+ show more]
[- hide]
| ... computing the label is a time consuming task, and hence applications can
specify with a facet request to return top 1000 facets but to compute the label only for
the top 10 facets. In order... |
| ... to compute labels for more of the facet results it is not
required to perform accumulation again.
See FacetRequest.getNumResults(), FacetRequest.getNumLabel() and
Facet... |
| ... cases, once top facets are found over the sample set, exact
accumulations are computed for those facets only, this time over the entire matching
document set.
Two kinds of sampling exist... |
|
|
http://lucene.apache.org/java/4_1_0/facet/org/apache/lucene/f.../userguide.html
2013-01-22, 06:26
|
|
|
org.apache.lucene.search (Lucene 4.1.0 API) - Lucene - [web site]
|
|
... results from a search, and implement sorting
or custom result filtering, collation, etc.
ComplexExplanation
Expert: Describes the score computation for document and query, and
can...
|
|
... class defines methods to iterate over a set of non-decreasing
doc ids.
Explanation
Expert: Describes the score computation for document and query.
FieldCache.CacheEntry
EXPERT: A unique...
|
[+ show more]
[- hide]
| ...Cache.getLongs(org.apache.lucene.index.AtomicReader, java.lang.String, boolean) and sorts by ascending value
FieldComparator.NumericComparator<T extends Number>
Base FieldComparator class for numeric types
FieldComparator.Relevance... |
| ...Comparator
Sorts by descending relevance.
FieldComparator.ShortComparator
Parses field's values as short (using FieldCache.getShorts(org.apache.lucene.index.AtomicReader, java.lang.String, boolean... |
| ....
MultiTermQuery.TopTermsBoostOnlyBooleanQueryRewrite
A rewrite method that first translates each term into
BooleanClause.Occur.SHOULD clause in a BooleanQuery, but the scores
are only computed... |
|
|
http://lucene.apache.org/java/4_1_0/core/org/apache/luc.../package-summary.html
2013-01-22, 06:26
|
|
|
Re: Using Multiple Cores for Multiple Users - Solr - [mail # user]
|
|
... for 'monkeys' and one of his feeds has a document with this word, but someone else is a zoophile, 'monkeys' will be a common word in the index. This will skew the relevance computation for user A. You...
|
|
...There is a standard problem with this: relevance is determined from all of the words in a field of all documents, not just the documents that match the query. That is, when user A searches...
|
|
|
Author: Lance Norskog,
2010-11-10, 03:07
|
|
|
Index (Lucene 4.1.0 API) - Lucene - [web site]
|
|
....apache.lucene.benchmark.byTask.feeds.ContentItemsSource
update count of items generated by this source
addResult(int, boolean, long) - Method in class org.apache.lucene.benchmark.quality.QualityStats
Add a (possibly relevant) doc.
add...
|
|
... in class org.apache.lucene.benchmark.quality.QualityStats
Returns the number of good points (only relevant points).
getNumParallelTasks() - Method in class org...
|
[+ show more]
[- hide]
| ....apache.lucene.benchmark.byTask.stats.TaskStats
getNumPoints() - Method in class org.apache.lucene.benchmark.quality.QualityStats
Returns the number of points (both relevant and irrelevant points).
getNumRuns() - Method in class org... |
| ... in class org.apache.lucene.benchmark.quality.QualityStats
Return the precision at rank n:
|{relevant hits within first n hits}| / n.
getProps() - Method in class org... |
| ...Rank() - Method in class org.apache.lucene.benchmark.quality.QualityStats.RecallPoint
Returns the rank: where on the list of returned docs this relevant doc appeared.
getRate() - Method in class org... |
|
|
http://lucene.apache.org/core/4_1_0/benchmark/index-all.html
2013-01-22, 06:26
|
|
|
Uses of Class org.apache.lucene.index.AtomicReaderContext (Lucene 4.1.0 API) - Lucene - [web site]
|
|
... computation for the named document.
Explanation DisjunctionMaxQuery.DisjunctionMaxWeight.explain(AtomicReaderContext context,
int doc)
Explain the score we computed for doc
Explanation...
|
|
...ValuesComparator.setNextReader(AtomicReaderContext context)
FieldComparator<Long> FieldComparator.LongComparator.setNextReader(AtomicReaderContext context)
FieldComparator<Float> FieldComparator.Relevance...
|
|
|
http://lucene.apache.org/java/4_1_0/core/org/apache.../AtomicReaderContext.html
2013-01-22, 06:26
|
|
|
Elasticsearch Histogram Facet » Elasticsearch - ElasticSearch - [web site]
|
|
... and value. The key is used to place the hit/document within the appropriate bucket, and the value is used to compute statistical data (for example, total). Here is an example:
{
"query...
|
|
..., and for the value, when the statistical data is computed per bucket scripts can be used. Here is an example:
{
"query" : {
"match_all" : {}
},
"facets" : {
"histo1...
|
[+ show more]
[- hide]
| ... use a date type field called date to get the minute of hour from it, and the total will be computed based on another field num1. Note, in this case, no interval was provided, so the bucket... |
| ...
}
}
}
}
}
Memory Considerations
In order to implement the histogram facet, the relevant field values are loaded into memory from the index. This means that per shard, there should be enough memory... |
| ... to contain them. Since by default, dynamic introduced types are long and double, one option to reduce the memory footprint is to explicitly set the types for the relevant fields to either short... |
|
|
http://www.elasticsearch.org/guide/reference/api/search.../histogram-facet.html
|
|
|
|
