Package org.apache.solr.common.params
Interface FacetParams
public interface FacetParams
Facet parameters
-
Nested Class Summary
Nested ClassesModifier and TypeInterfaceDescriptionstatic enumAn enumeration of the legal values forFACET_DATE_INCLUDEandFACET_RANGE_INCLUDE
lower = all gap based ranges include their lower bound upper = all gap based ranges include their upper bound edge = the first and last gap ranges include their edge bounds (ie: lower for the first one, upper for the last one) even if the corresponding upper/lower option is not specified outer = the BEFORE and AFTER ranges should be inclusive of their bounds, even if the first or last ranges already include those boundaries.static enumAn enumeration of the legal values forFACET_RANGE_METHODfilter = dv =static enumAn enumeration of the legal values forFACET_RANGE_OTHERandFACET_DATE_OTHER... -
Field Summary
FieldsModifier and TypeFieldDescriptionstatic final StringShould facet counts be calculated?static final StringOnly return constraints of a facet field containing the given string.static final StringIf using facet contains, ignore case when comparing values.static final StringAny field whose terms the user wants to enumerate over for Facet Contraint Counts (multi-value)static final StringDate string indicating the ending point for a date facet range.static final StringDate Math string indicating the interval of sub-ranges for a date facet range.static final StringBoolean indicating how counts should be computed if the range between 'start' and 'end' is not evenly divisible by 'gap'.static final StringMultivalued string indicating what rules should be applied to determine when the ranges generated for date faceting should be inclusive or exclusive of their end points.static final StringString indicating what "other" ranges should be computed for a date facet range (multi-value).static final StringDate string indicating the starting point for a date facet range.static final StringWhen faceting by enumerating the terms in a field, only use the filterCache for terms with a df >= to this parameter.static final StringOnly return constraints of a facet field excluding the given string.static final StringA boolean parameter that caps the facet counts at 1.static final StringAny field whose terms the user wants to enumerate over for Facet Constraint Counts (multi-value)static final StringA spatial RPT field to generate a 2D "heatmap" (grid of facet counts) on.static final StringUsed to determine the heatmap grid level to compute (optional).static final StringUsed to determine the heatmap grid level to compute, defaulting to 0.15.static final StringThe format of the heatmap: either png or ints2D (default).static final StringThe region the heatmap should minimally enclose.static final StringSpecify the heatmap grid level explicitly, instead of deriving it via distErr or distErrPct.static final StringThe maximum number of cells (grid squares) the client is willing to handle.static final StringAny field whose values the user wants to enumerate as explicit intervals of terms.static final StringSet of terms for a single interval to facet on.static final StringNumeric option indicating the maximum number of facet field counts be included in the response for each field - in descending order of count.static final StringOnly return constraints of a facet field containing the given string.static final StringWhat method should be used to do the facetingstatic final StringValue for FACET_METHOD param to indicate that Solr should enumerate over terms in a field to calculate the facet counts.static final StringValue for FACET_METHOD param to indicate that Solr should enumerate over documents and count up terms by consulting an uninverted representation of the field values (such as the FieldCache used for sorting).static final StringValue for FACET_METHOD param, like FACET_METHOD_fc but counts per-segment.static final StringValue for FACET_METHOD param to indicate that Solr should use an UnInvertedFieldstatic final StringNumeric option indicating the minimum number of hits before a facet should be included in the response.static final StringBoolean option indicating whether the response should include a facet field count for all records which have no value for the facet field.static final StringThe offset into the list of facets.static final Stringstatic final StringAn additional amount to over-request by when performing initial distributed requests.static final StringThe percentage to over-request by when performing initial distributed requests.static final StringComma separated list of fields to pivotstatic final StringMinimum number of docs that need to match to be included in the subliststatic final StringOnly return constraints of a facet field with the given prefix.static final StringAny lucene formatted queries the user would like to use for Facet Constraint Counts (multi-value)static final StringAny numerical field whose terms the user wants to enumerate over Facet Constraint Counts for selected ranges.static final StringNumber indicating the ending point for a numerical range facet.static final StringNumber indicating the interval of sub-ranges for a numerical facet range.static final StringBoolean indicating how counts should be computed if the range between 'start' and 'end' is not evenly divisible by 'gap'.static final StringMultivalued string indicating what rules should be applied to determine when the ranges generated for numeric faceting should be inclusive or exclusive of their end points.static final StringString indicating the method to use to resolve range facets.static final StringString indicating what "other" ranges should be computed for a numerical range facet (multi-value).static final StringNumber indicating the starting point for a numerical range facet.static final StringString option: "count" causes facets to be sorted by the count, "index" results in index order.static final Stringstatic final Stringstatic final Stringstatic final Stringstatic final StringNumeric option indicating the maximum number of threads to be used in counting facet field valesstatic final StringBoolean option indicating whether facet field counts of "0" should be included in the response.
-
Field Details
-
FACET
Should facet counts be calculated?- See Also:
-
FACET_THREADS
Numeric option indicating the maximum number of threads to be used in counting facet field vales- See Also:
-
FACET_METHOD
What method should be used to do the faceting- See Also:
-
FACET_METHOD_enum
Value for FACET_METHOD param to indicate that Solr should enumerate over terms in a field to calculate the facet counts.- See Also:
-
FACET_METHOD_fc
Value for FACET_METHOD param to indicate that Solr should enumerate over documents and count up terms by consulting an uninverted representation of the field values (such as the FieldCache used for sorting).- See Also:
-
FACET_METHOD_fcs
Value for FACET_METHOD param, like FACET_METHOD_fc but counts per-segment.- See Also:
-
FACET_METHOD_uif
Value for FACET_METHOD param to indicate that Solr should use an UnInvertedField- See Also:
-
FACET_QUERY
Any lucene formatted queries the user would like to use for Facet Constraint Counts (multi-value)- See Also:
-
FACET_FIELD
Any field whose terms the user wants to enumerate over for Facet Constraint Counts (multi-value)- See Also:
-
FACET_OFFSET
The offset into the list of facets. Can be overridden on a per field basis.- See Also:
-
FACET_LIMIT
Numeric option indicating the maximum number of facet field counts be included in the response for each field - in descending order of count. Can be overridden on a per field basis.- See Also:
-
FACET_MINCOUNT
Numeric option indicating the minimum number of hits before a facet should be included in the response. Can be overridden on a per field basis.- See Also:
-
FACET_ZEROS
Boolean option indicating whether facet field counts of "0" should be included in the response. Can be overridden on a per field basis.- See Also:
-
FACET_MISSING
Boolean option indicating whether the response should include a facet field count for all records which have no value for the facet field. Can be overridden on a per field basis.- See Also:
-
FACET_OVERREQUEST
- See Also:
-
FACET_OVERREQUEST_RATIO
The percentage to over-request by when performing initial distributed requests.default value is 1.5
- See Also:
-
FACET_OVERREQUEST_COUNT
An additional amount to over-request by when performing initial distributed requests. This value will be added after accounting for the over-request ratio.default value is 10
- See Also:
-
FACET_PIVOT
Comma separated list of fields to pivotexample: author,type (for types by author / types within author)
- See Also:
-
FACET_PIVOT_MINCOUNT
Minimum number of docs that need to match to be included in the sublistdefault value is 1
- See Also:
-
FACET_SORT
String option: "count" causes facets to be sorted by the count, "index" results in index order.- See Also:
-
FACET_SORT_COUNT
- See Also:
-
FACET_SORT_COUNT_LEGACY
- See Also:
-
FACET_SORT_INDEX
- See Also:
-
FACET_SORT_INDEX_LEGACY
- See Also:
-
FACET_PREFIX
Only return constraints of a facet field with the given prefix.- See Also:
-
FACET_CONTAINS
Only return constraints of a facet field containing the given string.- See Also:
-
FACET_MATCHES
Only return constraints of a facet field containing the given string.- See Also:
-
FACET_CONTAINS_IGNORE_CASE
If using facet contains, ignore case when comparing values.- See Also:
-
FACET_EXCLUDETERMS
Only return constraints of a facet field excluding the given string.- See Also:
-
FACET_ENUM_CACHE_MINDF
When faceting by enumerating the terms in a field, only use the filterCache for terms with a df >= to this parameter.- See Also:
-
FACET_EXISTS
A boolean parameter that caps the facet counts at 1. With this set, a returned count will only be 0 or 1. For apps that don't need the count, this should be an optimization- See Also:
-
FACET_DATE
Any field whose terms the user wants to enumerate over for Facet Contraint Counts (multi-value)- See Also:
-
FACET_DATE_START
Date string indicating the starting point for a date facet range. Can be overridden on a per field basis.- See Also:
-
FACET_DATE_END
Date string indicating the ending point for a date facet range. Can be overridden on a per field basis.- See Also:
-
FACET_DATE_GAP
Date Math string indicating the interval of sub-ranges for a date facet range. Can be overridden on a per field basis.- See Also:
-
FACET_DATE_HARD_END
Boolean indicating how counts should be computed if the range between 'start' and 'end' is not evenly divisible by 'gap'. If this value is true, then all counts of ranges involving the 'end' point will use the exact endpoint specified -- this includes the 'between' and 'after' counts as well as the last range computed using the 'gap'. If the value is false, then 'gap' is used to compute the effective endpoint closest to the 'end' param which results in the range between 'start' and 'end' being evenly divisible by 'gap'.The default is false.
Can be overridden on a per field basis.
- See Also:
-
FACET_DATE_OTHER
String indicating what "other" ranges should be computed for a date facet range (multi-value).Can be overridden on a per field basis.
- See Also:
-
FACET_DATE_INCLUDE
Multivalued string indicating what rules should be applied to determine when the ranges generated for date faceting should be inclusive or exclusive of their end points.The default value if none are specified is: [lower,upper,edge] (NOTE: This is different then FACET_RANGE_INCLUDE)
Can be overridden on a per field basis.
- See Also:
-
FACET_RANGE
Any numerical field whose terms the user wants to enumerate over Facet Constraint Counts for selected ranges.- See Also:
-
FACET_RANGE_START
Number indicating the starting point for a numerical range facet. Can be overridden on a per field basis.- See Also:
-
FACET_RANGE_END
Number indicating the ending point for a numerical range facet. Can be overridden on a per field basis.- See Also:
-
FACET_RANGE_GAP
Number indicating the interval of sub-ranges for a numerical facet range. Can be overridden on a per field basis.- See Also:
-
FACET_RANGE_HARD_END
Boolean indicating how counts should be computed if the range between 'start' and 'end' is not evenly divisible by 'gap'. If this value is true, then all counts of ranges involving the 'end' point will use the exact endpoint specified -- this includes the 'between' and 'after' counts as well as the last range computed using the 'gap'. If the value is false, then 'gap' is used to compute the effective endpoint closest to the 'end' param which results in the range between 'start' and 'end' being evenly divisible by 'gap'.The default is false.
Can be overridden on a per field basis.
- See Also:
-
FACET_RANGE_OTHER
String indicating what "other" ranges should be computed for a numerical range facet (multi-value). Can be overridden on a per field basis.- See Also:
-
FACET_RANGE_INCLUDE
Multivalued string indicating what rules should be applied to determine when the ranges generated for numeric faceting should be inclusive or exclusive of their end points.The default value if none are specified is: lower
Can be overridden on a per field basis.
- See Also:
-
FACET_RANGE_METHOD
String indicating the method to use to resolve range facets.Can be overridden on a per field basis.
- See Also:
-
FACET_INTERVAL
Any field whose values the user wants to enumerate as explicit intervals of terms.- See Also:
-
FACET_INTERVAL_SET
Set of terms for a single interval to facet on.- See Also:
-
FACET_HEATMAP
A spatial RPT field to generate a 2D "heatmap" (grid of facet counts) on. Just like the other faceting types, this may include a 'key' or local-params to facet multiple times. All parameters with this suffix can be overridden on a per-field basis.- See Also:
-
FACET_HEATMAP_FORMAT
The format of the heatmap: either png or ints2D (default).- See Also:
-
FACET_HEATMAP_GEOM
The region the heatmap should minimally enclose. It defaults to the world if not set. The format can either be a minimum to maximum point range format:["-150 10" TO "-100 30"]
(the first is bottom-left and second is bottom-right, both of which are parsed as points are parsed). OR, any WKT can be provided, and it's bounding box will be taken.- See Also:
-
FACET_HEATMAP_LEVEL
Specify the heatmap grid level explicitly, instead of deriving it via distErr or distErrPct.- See Also:
-
FACET_HEATMAP_DIST_ERR_PCT
Used to determine the heatmap grid level to compute, defaulting to 0.15. It has the same interpretation of distErrPct when searching on RPT, but relative to the shape in 'bbox'. It's a fraction (not a %) of the radius of the shape that grid squares must fit into without exceeding. > 0 and <= 0.5. Mutually exclusive with distErr & gridLevel.- See Also:
-
FACET_HEATMAP_DIST_ERR
Used to determine the heatmap grid level to compute (optional). It has the same interpretation of maxDistErr or distErr with RPT. It's an absolute distance (in units of what's specified on the field type) that a grid square must maximally fit into (width & height). It can be used to more explicitly specify the maximum grid square size without knowledge of what particular grid levels translate to. This can in turn be used with knowledge of the size of 'bbox' to get a target minimum number of grid cells. Mutually exclusive with distErrPct & gridLevel.- See Also:
-
FACET_HEATMAP_MAX_CELLS
The maximum number of cells (grid squares) the client is willing to handle. If this limit would be exceeded, we throw an error instead. Defaults to 100k.- See Also:
-