Apache
/
lucene
mirror of https://github.com/apache/lucene.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Ref Guide: small typos; i.e. and e.g. cleanups

This commit is contained in:
Cassandra Targett 2018-08-10 14:58:57 -05:00
parent 4a3f8f6b44
commit cdc0959afc
4 changed files with 85 additions and 90 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
solr/solr-ref-guide/src/colocating-collections.adoc
View File

@ -65,7 +65,7 @@ In case, replicas have to be moved from one node to another, perhaps in response
nodes will be chosen by preferring nodes that already have a replica of the `withCollection` so that the number of moves nodes will be chosen by preferring nodes that already have a replica of the `withCollection` so that the number of moves
is minimized. However, this also means that unless there are Autoscaling policy violations, Solr will continue to move is minimized. However, this also means that unless there are Autoscaling policy violations, Solr will continue to move
such replicas to already loaded nodes instead of preferring empty nodes. Therefore, it is advised to have policy rules such replicas to already loaded nodes instead of preferring empty nodes. Therefore, it is advised to have policy rules
which can prevent such overloading by e.g. setting the maximum number of cores per node to a fixed value. which can prevent such overloading by e.g., setting the maximum number of cores per node to a fixed value.
Example: Example:
`{'cores' : '<8', 'node' : '#ANY'}` `{'cores' : '<8', 'node' : '#ANY'}`

123
solr/solr-ref-guide/src/json-facet-api.adoc
View File

@ -99,7 +99,7 @@ In this guide, we will often just present the **facet command block**:
[source,java] [source,java]
---- ----
{ {
x : "average(mul(price,popularity))" x: "average(mul(price,popularity))"
} }
---- ----
@ -109,7 +109,7 @@ To execute a facet command block such as this, you'll need to use the `json.face
---- ----
curl http://localhost:8983/solr/techproducts/query -d 'q=*:*&json.facet= curl http://localhost:8983/solr/techproducts/query -d 'q=*:*&json.facet=
{ {
x : "avg(mul(price,popularity))" x: "avg(mul(price,popularity))"
} }
' '
---- ----
@ -120,10 +120,10 @@ Another option is to use the JSON Request API to provide the entire request in J
---- ----
curl http://localhost:8983/solr/techproducts/query -d ' curl http://localhost:8983/solr/techproducts/query -d '
{ {
query : "*:*", // this is the base query query: "*:*", // this is the base query
filter : [ "inStock:true" ], // a list of filters filter: [ "inStock:true" ], // a list of filters
facet : { facet: {
x : "avg(mul(price,popularity))" // and our funky metric of average of price * popularity x: "avg(mul(price,popularity))" // and our funky metric of average of price * popularity
} }
} }
' '
@ -207,7 +207,7 @@ An example of the simplest form of the query facet is `"query":"query string"`.
[source,java] [source,java]
---- ----
{ {
high_popularity : { query : "popularity:[8 TO 10]" } high_popularity: {query: "popularity:[8 TO 10]" }
} }
---- ----
@ -405,7 +405,7 @@ An expanded form allows for <<local-parameters-in-queries.adoc#local-parameters-
== Nested Facets == Nested Facets
Nested facets, or **sub-facets**, allow one to nest facet commands under any facet command that partitions the domain into buckets (ie: `terms`, `range`, `query`). These sub-facets are then evaluated against the domains defined by the set of all documents in each bucket of their parent. Nested facets, or **sub-facets**, allow one to nest facet commands under any facet command that partitions the domain into buckets (i.e., `terms`, `range`, `query`). These sub-facets are then evaluated against the domains defined by the set of all documents in each bucket of their parent.
The syntax is identical to top-level facets - just add a `facet` command to the facet command block of the parent facet. Technically, every facet command is actually a sub-facet since we start off with a single facet bucket with a domain defined by the main query and filters. The syntax is identical to top-level facets - just add a `facet` command to the facet command block of the parent facet. Technically, every facet command is actually a sub-facet since we start off with a single facet bucket with a domain defined by the main query and filters.
@ -497,14 +497,14 @@ The default sort for a field or terms facet is by bucket count descending. We ca
} }
---- ----
== Changing The Domain == Changing the Domain
As discussed above, facets compute buckets or statistics based on a "domain" which is typically implicit: As discussed above, facets compute buckets or statistics based on a "domain" which is typically implicit:
* By default, facets use the set of all documents matching the main query as their domain. * By default, facets use the set of all documents matching the main query as their domain.
* Nested "sub-facets" are computed for every bucket of their parent facet, using a domain containing all documents in that bucket. * Nested "sub-facets" are computed for every bucket of their parent facet, using a domain containing all documents in that bucket.
But users can also override the "domain" of a facet that partitions data, using an explicit `domain` attribute whose value is a JSON Object that can support various options for restricting, expanding, or completley changing the original domain before the buckets are computed for the associated facet. But users can also override the "domain" of a facet that partitions data, using an explicit `domain` attribute whose value is a JSON Object that can support various options for restricting, expanding, or completely changing the original domain before the buckets are computed for the associated facet.
[NOTE] [NOTE]
==== ====
@ -516,16 +516,16 @@ A `\*:*` query facet with a `domain` change can be used to group multiple sub-fa
=== Adding Domain Filters === Adding Domain Filters
The simplest example of a domain change is to specify an additional filter which will be applied to the existing domain. This can be done via the `filter` keyword in the `domain` block of the facet. The simplest example of a domain change is to specify an additional filter which will be applied to the existing domain. This can be done via the `filter` keyword in the `domain` block of the facet.
Example: Example:
[source,java] [source,json]
---- ----
{ {
categories : { categories: {
type : terms, type: terms,
field : cat, field: cat,
domain : { filter : "popularity:[5 TO 10]" } domain: {filter: "popularity:[5 TO 10]" }
} }
} }
---- ----
@ -558,22 +558,22 @@ Example:
The value of `excludeTags` can be a single string tag, array of string tags or comma-separated tags in the single string. The value of `excludeTags` can be a single string tag, array of string tags or comma-separated tags in the single string.
When an `excludeTags` option is combined with other `domain` changing options, it expands the domain _before_ any other domain changes take place. When an `excludeTags` option is combined with other `domain` changing options, it expands the domain _before_ any other domain changes take place.
See also the section on <<faceting.adoc#tagging-and-excluding-filters,multi-select faceting>>. See also the section on <<faceting.adoc#tagging-and-excluding-filters,multi-select faceting>>.
=== Arbitrary Domain Query === Arbitrary Domain Query
A `query` domain can be specified when you wish to compute a facet against an arbitrary set of documents, regardless of the original domain. The most common use case would be to compute a top level facet against a specific subset of the collection, regardless of the main query. But it can also be useful on nested facets when building <<Semantic Knowledge Graphs>>. A `query` domain can be specified when you wish to compute a facet against an arbitrary set of documents, regardless of the original domain. The most common use case would be to compute a top level facet against a specific subset of the collection, regardless of the main query. But it can also be useful on nested facets when building <<Semantic Knowledge Graphs>>.
Example: Example:
[source,json] [source,json]
---- ----
{ {
"categories" : { "categories": {
"type" : "terms", "type": "terms",
"field" : "cat", "field": "cat",
"domain" : { "query" : "*:*" } "domain": {"query": "*:*" }
} }
} }
---- ----
@ -581,38 +581,35 @@ Example:
The value of `query` can be a single query, or a JSON list of queries. Each query can be: The value of `query` can be a single query, or a JSON list of queries. Each query can be:
* a string containing a query in Solr query syntax * a string containing a query in Solr query syntax
* a reference to a request parameter containing Solr query syntax, of the form: `{param : <request_param_name>}` * a reference to a request parameter containing Solr query syntax, of the form: `{param: <request_param_name>}`
NOTE: While a `query` domain can be comibined with an additional domain `filter`, It is not possible to also use `excludeTags`, because the tags would be meaningless: The `query` domain already completely ignores the top-level query and all previous filters. NOTE: While a `query` domain can be combined with an additional domain `filter`, It is not possible to also use `excludeTags`, because the tags would be meaningless: The `query` domain already completely ignores the top-level query and all previous filters.
=== Block Join Domain Changes === Block Join Domain Changes
When a collection contains <<uploading-data-with-index-handlers.adoc#nested-child-documents, Block Join child documents>>, the `blockChildren` or `blockParent` domain options can be used transform an existing domain containing one type of document, into a domain containing the documents with the specified relationship (child or parent of) to the documents from the original domain. When a collection contains <<uploading-data-with-index-handlers.adoc#nested-child-documents, Block Join child documents>>, the `blockChildren` or `blockParent` domain options can be used transform an existing domain containing one type of document, into a domain containing the documents with the specified relationship (child or parent of) to the documents from the original domain.
Both of these options work similar to the corrisponding <<other-parsers.adoc#block-join-query-parsers,Block Join Query Parsers>> by taking in a single String query that exclusively matches all parent documents in the collection. If `blockParent` is used, then the resulting domain will contain all parent documents of the children from the original domain. If If `blockChildren` is used, then the resulting domain will contain all child documents of the parents from the original domain. Both of these options work similar to the corresponding <<other-parsers.adoc#block-join-query-parsers,Block Join Query Parsers>> by taking in a single String query that exclusively matches all parent documents in the collection. If `blockParent` is used, then the resulting domain will contain all parent documents of the children from the original domain. If If `blockChildren` is used, then the resulting domain will contain all child documents of the parents from the original domain.
Example: Example:
[source,json,subs="verbatim,callouts"]] [source,json,subs="verbatim,callouts"]]
---- ----
{ {
"colors" : { // <1> "colors": { // <1>
"type" : "terms", "type": "terms",
"field" : "sku_color", // <2> "field": "sku_color", // <2>
"facet" : { "facet" : {
"brands" : { "brands" : {
"type" : "terms", "type": "terms",
"field" : "product_brand", // <3> "field": "product_brand", // <3>
"domain" : { "domain": {
"blockParent" : "doc_type:product" "blockParent": "doc_type:product"
} }
} }}}}
}
}
}
---- ----
<1> This example assumes we parent documents corrisponding to Products, with child documents corrisponding to individual SKUs with unique colors, and that our original query was against SKU documents. <1> This example assumes we parent documents corresponding to Products, with child documents corresponding to individual SKUs with unique colors, and that our original query was against SKU documents.
<2> The `colors` facet will be computed against all of the original SKU documents matching our search. <2> The `colors` facet will be computed against all of the original SKU documents matching our search.
<3> For each bucket in the `colors` facet, the set of all matching SKU documents will be transformed into the set of corrisponding parent Product documents. The resulting `brands` sub-facet will count how many Product documents (that have SKUs with the associated color) exist for each Brand. <3> For each bucket in the `colors` facet, the set of all matching SKU documents will be transformed into the set of corresponding parent Product documents. The resulting `brands` sub-facet will count how many Product documents (that have SKUs with the associated color) exist for each Brand.
=== Join Query Domain Changes === Join Query Domain Changes
@ -624,19 +621,19 @@ Example:
[source,json] [source,json]
---- ----
{ {
"colors" : { "colors": {
"type" : "terms", "type": "terms",
"field" : "sku_color", "field": "sku_color",
"facet" : { "facet": {
"brands" : { "brands": {
"type" : "terms", "type": "terms",
"field" : "product_brand", "field": "product_brand",
"domain" : { "domain" : {
"join" : { "join" : {
"from" : "product_id_of_this_sku", "from": "product_id_of_this_sku",
"to" : "id" "to": "id"
}, },
"filter" : "doc_type:product" "filter": "doc_type:product"
} }
} }
} }
@ -649,20 +646,20 @@ Example:
A `graph` domain change option works similarly to the `join` domain option, but can do traversal multiple hops `from` the existing domain `to` other documents. A `graph` domain change option works similarly to the `join` domain option, but can do traversal multiple hops `from` the existing domain `to` other documents.
This works very similar to the <<other-parsers.adoc#graph-query-parser,Graph Query Parser>>, supporting all of it's optional paramaters, and has the same limitations when dealing with multi-shard collections. This works very similar to the <<other-parsers.adoc#graph-query-parser,Graph Query Parser>>, supporting all of it's optional parameters, and has the same limitations when dealing with multi-shard collections.
Example: Example:
[source,json] [source,json]
---- ----
{ {
"related_brands" : { "related_brands": {
"type" : "terms", "type": "terms",
"field" : "brand", "field": "brand",
"domain" : { "domain": {
"graph" : { "graph": {
"from" : "related_product_ids", "from": "related_product_ids",
"to" : "id", "to": "id",
"maxDepth" : 3 "maxDepth": 3
} }
} }
} }
@ -671,13 +668,13 @@ Example:
== Block Join Counts == Block Join Counts
When a collection contains <<uploading-data-with-index-handlers.adoc#nested-child-documents, Block Join child documents>>, the `blockChildren` and `blockParent` domain changes mentioned above can be useful when searching for parent documents and you want to compute stats against all of the affected children documents (or vice versa). But in the situation where the _count_ of all the blocks that exist in the current domain is sufficient, a more effecient option is the `uniqueBlock()` aggregate function. When a collection contains <<uploading-data-with-index-handlers.adoc#nested-child-documents, Block Join child documents>>, the `blockChildren` and `blockParent` domain changes mentioned above can be useful when searching for parent documents and you want to compute stats against all of the affected children documents (or vice versa). But in the situation where the _count_ of all the blocks that exist in the current domain is sufficient, a more efficient option is the `uniqueBlock()` aggregate function.
=== Block Join Counts Example === Block Join Counts Example
Suppose we have products with multiple SKUs, and we want to count products for each color. Suppose we have products with multiple SKUs, and we want to count products for each color.
[source,java] [source,json]
---- ----
{ {
"id": "1", "type": "product", "name": "Solr T-Shirt", "id": "1", "type": "product", "name": "Solr T-Shirt",
@ -742,11 +739,11 @@ Unlike most aggregation functions, the `relatedness(...)` function is aware of w
NOTE: While it's very common to define the Background Set as `\*:*`, or some other super-set of the Foreground Query, it is not strictly required. The `relatedness(...)` function can be used to compare the statistical relatedness of sets of documents to orthogonal foreground/background queries. NOTE: While it's very common to define the Background Set as `\*:*`, or some other super-set of the Foreground Query, it is not strictly required. The `relatedness(...)` function can be used to compare the statistical relatedness of sets of documents to orthogonal foreground/background queries.
[[relatedness-options]] [[relatedness-options]]
=== `relatedness()` Options === relatedness() Options
When using the extended `type:func` syntax for specifying a `relatedness()` aggregation, an opional `min_popularity` (float) option can be used to specify a lower bound on the `foreground_popularity` and `background_popularity` values, that must be met in order for the `relatedness` score to be valid -- If this `min_popularity` is not met, then the `relatedness` score will be `-Infinity`. When using the extended `type:func` syntax for specifying a `relatedness()` aggregation, an opional `min_popularity` (float) option can be used to specify a lower bound on the `foreground_popularity` and `background_popularity` values, that must be met in order for the `relatedness` score to be valid -- If this `min_popularity` is not met, then the `relatedness` score will be `-Infinity`.
[source,javascript] [source,json]
---- ----
{ "type": "func", { "type": "func",
"func": "relatedness($fore,$back)", "func": "relatedness($fore,$back)",
@ -814,7 +811,7 @@ curl -sS -X POST http://localhost:8983/solr/gettingstarted/query -d 'rows=0&q=*:
<4> In both calls to the `relatedness(...)` function, we use <<local-parameters-in-queries.adoc#parameter-dereferencing,Parameter Variables>> to refer to the previously defined `fore` and `back` queries. <4> In both calls to the `relatedness(...)` function, we use <<local-parameters-in-queries.adoc#parameter-dereferencing,Parameter Variables>> to refer to the previously defined `fore` and `back` queries.
.The Facet Response .The Facet Response
[source,javascript,subs="verbatim,callouts"] [source,json,subs="verbatim,callouts"]
---- ----
"facets":{ "facets":{
"count":16, "count":16,
@ -860,8 +857,6 @@ curl -sS -X POST http://localhost:8983/solr/gettingstarted/query -d 'rows=0&q=*:
<6> The number documents matching `age:[35 TO *]` _and_ `hobbies:golf` _and_ `state:AZ` is 18.75% of the total number of documents in the Background Set <6> The number documents matching `age:[35 TO *]` _and_ `hobbies:golf` _and_ `state:AZ` is 18.75% of the total number of documents in the Background Set
<7> 50% of the documents in the Background Set match `state:AZ` <7> 50% of the documents in the Background Set match `state:AZ`
[[References]]
== References == References
This documentation was originally adapted largely from the following blog pages: This documentation was originally adapted largely from the following blog pages:

6
solr/solr-ref-guide/src/metrics-reporting.adoc
View File

@ -247,15 +247,15 @@ You can start a local MBean server with a system property at startup by adding `
The SLF4J Reporter uses the `org.apache.solr.metrics.reporters.SolrSlf4jReporter` class. The SLF4J Reporter uses the `org.apache.solr.metrics.reporters.SolrSlf4jReporter` class.
It takes the following arguments, in addition to the common arguments <<Reporter Arguments,above>>. It takes the following arguments, in addition to common arguments described <<Reporter Arguments,above>>.
`logger`:: `logger`::
The name of the logger to use. Default is empty, in which case the group (or the initial part of the registry name that identifies a metrics group) will be used if specified in the plugin configuration. The name of the logger to use. Default is empty, in which case the group (or the initial part of the registry name that identifies a metrics group) will be used if specified in the plugin configuration.
Users can specify logger name (and the corresponding logger configuration in e.g., Log4j configuration) to output metrics-related logging to separate file(s), which can then be processed by external applications. Users can specify logger name (and the corresponding logger configuration in e.g., Log4j configuration) to output metrics-related logging to separate file(s), which can then be processed by external applications.
Here is an example for configuring the default log4j2.xml which ships in solr. This can be used in conjunction with the solr.xml example provided earlier in this page to configure the SolrSlf4jReporter Here is an example for configuring the default `log4j2.xml` which ships in Solr. This can be used in conjunction with the `solr.xml` example provided earlier in this page to configure the SolrSlf4jReporter:
[source,text] [source,xml]
---- ----
<Configuration> <Configuration>
<Appenders> <Appenders>

44
solr/solr-ref-guide/src/solrcloud-autoscaling-policy-preferences.adoc
View File

@ -20,7 +20,7 @@
The autoscaling policy and preferences are a set of rules and sorting preferences that help Solr select the target of cluster management operations so the overall load on the cluster remains balanced. The autoscaling policy and preferences are a set of rules and sorting preferences that help Solr select the target of cluster management operations so the overall load on the cluster remains balanced.
Solr consults the configured policy and preferences when performing <<Commands That Use Autoscaling Policy and Preferences,Collections API commands>> in all contexts: manual, e.g. using `bin/solr`; semi-automatic, via the <<solrcloud-autoscaling-api.adoc#suggestions-api,Suggestions API>> or the Admin UI's <<suggestions-screen.adoc#suggestions-screen,Suggestions Screen>>; or fully automatic, via configured <<solrcloud-autoscaling-triggers.adoc#solrcloud-autoscaling-triggers,Triggers>>. Solr consults the configured policy and preferences when performing <<Commands That Use Autoscaling Policy and Preferences,Collections API commands>> in all contexts: manual, e.g., using `bin/solr`; semi-automatic, via the <<solrcloud-autoscaling-api.adoc#suggestions-api,Suggestions API>> or the Admin UI's <<suggestions-screen.adoc#suggestions-screen,Suggestions Screen>>; or fully automatic, via configured <<solrcloud-autoscaling-triggers.adoc#solrcloud-autoscaling-triggers,Triggers>>.
== Cluster Preferences Specification == Cluster Preferences Specification
@ -92,10 +92,10 @@ A policy is a hard rule to be satisfied by each node. If a node does not satisfy
==== Rule Types ==== Rule Types
Policy rules can be either global or per-collection: Policy rules can be either global or per-collection:
* *Global rules* constrain the number of cores per node or node group. This type of rule applies to cores from all collections hosted on the specified node(s). As a result, <<Defining Collection-Specific Policies,collection-specific policies>>, which are associated with individual collections, may not contain global rules. * *Global rules* constrain the number of cores per node or node group. This type of rule applies to cores from all collections hosted on the specified node(s). As a result, <<Defining Collection-Specific Policies,collection-specific policies>>, which are associated with individual collections, may not contain global rules.
* *Per-collection rules* constrain the number of replicas per node or node group. * *Per-collection rules* constrain the number of replicas per node or node group.
Global rules have three parts: Global rules have three parts:
@ -108,28 +108,28 @@ Per-collection rules have four parts:
* <<Node Selector>> * <<Node Selector>>
* <<Replica Selector and Rule Evaluation Context>> * <<Replica Selector and Rule Evaluation Context>>
* <<Replica Count Constraint>> * <<Replica Count Constraint>>
* <<Rule Strictness>> * <<Rule Strictness>>
==== Node Selector ==== Node Selector
Rule evaluation is restricted to node(s) matching the value of one of the following attributes: `node`, `port`, `ip_\*`, `sysprop.*`, or `diskType`. For replica/core count constraints other than `#EQUAL`, a condition specified in one of the following attributes may instead be used to select nodes: `freedisk`, `host`, `sysLoadAvg`, `heapUsage`, `nodeRole`, or `metrics.*`. Rule evaluation is restricted to node(s) matching the value of one of the following attributes: `node`, `port`, `ip_\*`, `sysprop.*`, or `diskType`. For replica/core count constraints other than `#EQUAL`, a condition specified in one of the following attributes may instead be used to select nodes: `freedisk`, `host`, `sysLoadAvg`, `heapUsage`, `nodeRole`, or `metrics.*`.
Except for `node`, the attributes above cause selected nodes to be partitioned into node groups. A node group is referred to as a "bucket". Those attributes usable with the `#EQUAL` directive may define buckets either via the value `#EACH` or an array `["value1", ...]` (a subset of all possible values); in both cases, each node is placed in the bucket corresponding to the matching attribute value. Except for `node`, the attributes above cause selected nodes to be partitioned into node groups. A node group is referred to as a "bucket". Those attributes usable with the `#EQUAL` directive may define buckets either via the value `#EACH` or an array `["value1", ...]` (a subset of all possible values); in both cases, each node is placed in the bucket corresponding to the matching attribute value.
The `node` attribute always places each selected node into its own bucket, regardless of the attribute value's form (`#ANY`, `node-name`, or `["node1-name", ...]`). The `node` attribute always places each selected node into its own bucket, regardless of the attribute value's form (`#ANY`, `node-name`, or `["node1-name", ...]`).
Replica and core count constraints, described below, are evaluated against the total number in each bucket. Replica and core count constraints, described below, are evaluated against the total number in each bucket.
==== Core Count Constraint ==== Core Count Constraint
The `cores` attribute value can be specified in one of the following forms: The `cores` attribute value can be specified in one of the following forms:
* the `#EQUAL` directive, which will cause cores to be distributed equally among the nodes specified via the rule's <<Node Selector>>. * the `#EQUAL` directive, which will cause cores to be distributed equally among the nodes specified via the rule's <<Node Selector>>.
* a constraint on the core count on each <<Node Selector,selected node>>, specified as one of: * a constraint on the core count on each <<Node Selector,selected node>>, specified as one of:
** an integer value (e.g. `2`), a lower bound (e.g. `>0`), or an upper bound (e.g. `<3`) ** an integer value (e.g., `2`), a lower bound (e.g., `>0`), or an upper bound (e.g., `<3`)
** a decimal value, interpreted as an acceptable range of core counts, from the floor of the value to the ceiling of the value, with the system preferring the rounded value (e.g. `1.6`: `1` or `2` is acceptable, and `2` is preferred) ** a decimal value, interpreted as an acceptable range of core counts, from the floor of the value to the ceiling of the value, with the system preferring the rounded value (e.g., `1.6`: `1` or `2` is acceptable, and `2` is preferred)
** a range of acceptable core counts, as inclusive lower and upper integer bounds separated by a hyphen (e.g. `3-5`) ** a range of acceptable core counts, as inclusive lower and upper integer bounds separated by a hyphen (e.g., `3-5`)
** a percentage (e.g. `33%`), which is multiplied by the number of cores in the cluster at runtime. This value is then interpreted as described above for literal decimal values. ** a percentage (e.g., `33%`), which is multiplied by the number of cores in the cluster at runtime. This value is then interpreted as described above for literal decimal values.
==== Replica Selector and Rule Evaluation Context ==== Replica Selector and Rule Evaluation Context
@ -150,14 +150,14 @@ The `replica` attribute value can be specified in one of the following forms:
* `#ALL`: All <<Replica Selector and Rule Evaluation Context,selected replicas>> will be placed on the <<Node Selector,selected nodes>>. * `#ALL`: All <<Replica Selector and Rule Evaluation Context,selected replicas>> will be placed on the <<Node Selector,selected nodes>>.
* `#EQUAL`: Distribute <<Replica Selector and Rule Evaluation Context,selected replicas>> evenly among all the <<Node Selector,selected nodes>>. * `#EQUAL`: Distribute <<Replica Selector and Rule Evaluation Context,selected replicas>> evenly among all the <<Node Selector,selected nodes>>.
* a constraint on the replica count on each <<Node Selector,selected node>>, specified as one of: * a constraint on the replica count on each <<Node Selector,selected node>>, specified as one of:
** an integer value (e.g. `2`), a lower bound (e.g. `>0`), or an upper bound (e.g. `<3`) ** an integer value (e.g., `2`), a lower bound (e.g., `>0`), or an upper bound (e.g., `<3`)
** a decimal value, interpreted as an acceptable range of replica counts, from the floor of the value to the ceiling of the value, with the system preferring the rounded value (e.g. `1.6`: `1` or `2` is acceptable, and `2` is preferred) ** a decimal value, interpreted as an acceptable range of replica counts, from the floor of the value to the ceiling of the value, with the system preferring the rounded value (e.g., `1.6`: `1` or `2` is acceptable, and `2` is preferred)
** a range of acceptable replica counts, as inclusive lower and upper integer bounds separated by a hyphen (e.g. `3-5`) ** a range of acceptable replica counts, as inclusive lower and upper integer bounds separated by a hyphen (e.g., `3-5`)
** a percentage (e.g. `33%`), which is multiplied by the number of <<Replica Selector and Rule Evaluation Context,selected replicas>> at runtime. This value is then interpreted as described above for literal decimal values. ** a percentage (e.g., `33%`), which is multiplied by the number of <<Replica Selector and Rule Evaluation Context,selected replicas>> at runtime. This value is then interpreted as described above for literal decimal values.
==== Rule Strictness ==== Rule Strictness
By default, the rule must be satisfied, and if it can't, then no action will be taken. By default, the rule must be satisfied, and if it can't, then no action will be taken.
If the `strict` attribute value is specified as `false`, Solr tries to satisfy the rule on a best effort basis, but if no node can satisfy the rule then any node may be chosen. If the `strict` attribute value is specified as `false`, Solr tries to satisfy the rule on a best effort basis, but if no node can satisfy the rule then any node may be chosen.
@ -228,7 +228,7 @@ Each attribute in the policy may specify one of the following operators along wi
* `>`: Greater than * `>`: Greater than
* `!`: Not * `!`: Not
* Range operator `(-)`: a value such as `"3-5"` means a value between 3 to 5 (inclusive). This is only supported in the `replica` and `cores` attributes. * Range operator `(-)`: a value such as `"3-5"` means a value between 3 to 5 (inclusive). This is only supported in the `replica` and `cores` attributes.
* Array operator `[]`. e.g: `sysprop.zone = ["east", "west","apac"]`. This is equivalent to having multiple rules with each of these values. This can be used in the following attributes * Array operator `[]`: e.g., `sysprop.zone= ["east","west","apac"]`. This is equivalent to having multiple rules with each of these values. This can be used in the following attributes:
** `sysprop.*` ** `sysprop.*`
** `port` ** `port`
** `ip_*` ** `ip_*`
@ -240,13 +240,13 @@ Each attribute in the policy may specify one of the following operators along wi
This supports values calculated at the time of execution. This supports values calculated at the time of execution.
* `%` : A certain percentage of the value. This is supported by the following attributes * `%` : A certain percentage of the value. This is supported by the following attributes:
** `replica` ** `replica`
** `cores` ** `cores`
** `freedisk` ** `freedisk`
* `#ALL` : This is applied to the `replica` attribute only. This means all replicas that meet the rule condition. * `#ALL` : This is applied to the `replica` attribute only. This means all replicas that meet the rule condition.
* `#EQUAL`: This is applied to the `replica` and `cores` attributes only. This means equal number of replicas/cores in each bucket. The buckets can be defined using an array operator (`[]`) or `#EACH`. The buckets can be defined using the following properties: * `#EQUAL`: This is applied to the `replica` and `cores` attributes only. This means an equal number of replicas/cores in each bucket. The buckets can be defined using an array operator (`[]`) or `#EACH`. The buckets can be defined using the following properties:
** `node` \<- <<Rule Types,global rules>>, i.e. with the `cores` attribute, may only specify this attribute ** `node` \<- <<Rule Types,global rules>>, i.e., with the `cores` attribute, may only specify this attribute
** `sysprop.*` ** `sysprop.*`
** `port` ** `port`
** `diskType` ** `diskType`