You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@lucene.apache.org by ho...@apache.org on 2017/05/09 04:36:48 UTC
[4/4] lucene-solr:jira/solr-10290: batch remove OLD_CONFLUENCE_ID
comments now that all inter-page links have been fixed
batch remove OLD_CONFLUENCE_ID comments now that all inter-page links have been fixed
Project: http://git-wip-us.apache.org/repos/asf/lucene-solr/repo
Commit: http://git-wip-us.apache.org/repos/asf/lucene-solr/commit/4a0b9b53
Tree: http://git-wip-us.apache.org/repos/asf/lucene-solr/tree/4a0b9b53
Diff: http://git-wip-us.apache.org/repos/asf/lucene-solr/diff/4a0b9b53
Branch: refs/heads/jira/solr-10290
Commit: 4a0b9b5395f07961ded6ed9e041a8772de690b24
Parents: 10152ba
Author: Chris Hostetter <ho...@apache.org>
Authored: Mon May 8 21:36:34 2017 -0700
Committer: Chris Hostetter <ho...@apache.org>
Committed: Mon May 8 21:36:34 2017 -0700
----------------------------------------------------------------------
solr/solr-ref-guide/src/collections-api.adoc | 1 -
.../src/cross-data-center-replication-cdcr-.adoc | 6 ------
solr/solr-ref-guide/src/faceting.adoc | 1 -
solr/solr-ref-guide/src/other-schema-elements.adoc | 1 -
solr/solr-ref-guide/src/phonetic-matching.adoc | 1 -
solr/solr-ref-guide/src/rule-based-replica-placement.adoc | 3 ---
solr/solr-ref-guide/src/running-solr-on-hdfs.adoc | 1 -
.../solr-ref-guide/src/solr-control-script-reference.adoc | 5 -----
solr/solr-ref-guide/src/spatial-search.adoc | 2 --
solr/solr-ref-guide/src/spell-checking.adoc | 2 --
solr/solr-ref-guide/src/streaming-expressions.adoc | 1 -
solr/solr-ref-guide/src/the-dismax-query-parser.adoc | 8 --------
.../src/the-extended-dismax-query-parser.adoc | 2 --
solr/solr-ref-guide/src/the-standard-query-parser.adoc | 6 ------
solr/solr-ref-guide/src/the-terms-component.adoc | 1 -
.../solr-ref-guide/src/transforming-result-documents.adoc | 10 ----------
.../understanding-analyzers-tokenizers-and-filters.adoc | 2 --
solr/solr-ref-guide/src/update-request-processors.adoc | 1 -
solr/solr-ref-guide/src/upgrading-a-solr-cluster.adoc | 5 -----
.../uploading-data-with-solr-cell-using-apache-tika.adoc | 1 -
.../using-zookeeper-to-manage-configuration-files.adoc | 1 -
solr/solr-ref-guide/src/zookeeper-access-control.adoc | 1 -
22 files changed, 62 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/lucene-solr/blob/4a0b9b53/solr/solr-ref-guide/src/collections-api.adoc
----------------------------------------------------------------------
diff --git a/solr/solr-ref-guide/src/collections-api.adoc b/solr/solr-ref-guide/src/collections-api.adoc
index 0e27baa..1937368 100644
--- a/solr/solr-ref-guide/src/collections-api.adoc
+++ b/solr/solr-ref-guide/src/collections-api.adoc
@@ -1651,7 +1651,6 @@ In this example, two replicas in the "alreadyLeaders" section already had the le
Examining the clusterstate after issuing this call should show that every live node that has the "preferredLeader" property should also have the "leader" property set to _true_.
-// OLD_CONFLUENCE_ID: CollectionsAPI-FORCELEADER:ForceShardLeader
[[CollectionsAPI-FORCELEADER_ForceShardLeader]]
http://git-wip-us.apache.org/repos/asf/lucene-solr/blob/4a0b9b53/solr/solr-ref-guide/src/cross-data-center-replication-cdcr-.adoc
----------------------------------------------------------------------
diff --git a/solr/solr-ref-guide/src/cross-data-center-replication-cdcr-.adoc b/solr/solr-ref-guide/src/cross-data-center-replication-cdcr-.adoc
index a555287..4efaf4c 100644
--- a/solr/solr-ref-guide/src/cross-data-center-replication-cdcr-.adoc
+++ b/solr/solr-ref-guide/src/cross-data-center-replication-cdcr-.adoc
@@ -124,7 +124,6 @@ The CDCR replication logic requires modification to the maintenance logic of the
If the communication with one of the target data center is slow, the Updates Log on the source data center can grow to a substantial size. In such a scenario, it is necessary for the Updates Log to be able to efficiently find a given update operation given its identifier. Given that its identifier is an incremental number, it is possible to implement an efficient search strategy. Each transaction log file contains as part of its filename the version number of the first element. This is used to quickly traverse all the transaction log files and find the transaction log file containing one specific version number.
-// OLD_CONFLUENCE_ID: CrossDataCenterReplication(CDCR)-Monitoring
[[CrossDataCenterReplication_CDCR_-Monitoring]]
=== Monitoring
@@ -140,7 +139,6 @@ Information about the lifecycle and statistics will be provided on a per-shard b
The CDC Replicator is a background thread that is responsible for replicating updates from a Source data center to one or more target data centers. It is responsible in providing monitoring information on a per-shard basis. As there can be a large number of collections and shards in a cluster, we will use a fixed-size pool of CDC Replicator threads that will be shared across shards.
-// OLD_CONFLUENCE_ID: CrossDataCenterReplication(CDCR)-Limitations
[[CrossDataCenterReplication_CDCR_-Limitations]]
=== Limitations
@@ -151,14 +149,12 @@ The current design of CDCR has some limitations. CDCR will continue to evolve ov
* CDCR is currently only active-passive; data is pushed from the Source cluster to the target cluster. There is active work being done in this area in the 6x code line to remove this limitation.
* CDCR works most robustly with the same number of shards in the Source and target collection. The shards in the two collections may have different numbers of replicas.
-// OLD_CONFLUENCE_ID: CrossDataCenterReplication(CDCR)-Configuration
[[CrossDataCenterReplication_CDCR_-Configuration]]
== Configuration
The source and target configurations differ in the case of the data centers being in separate clusters. "Cluster" here means separate ZooKeeper ensembles controlling disjoint Solr instances. Whether these data centers are physically separated or not is immaterial for this discussion.
-// OLD_CONFLUENCE_ID: CrossDataCenterReplication(CDCR)-SourceConfiguration
[[CrossDataCenterReplication_CDCR_-SourceConfiguration]]
=== Source Configuration
@@ -195,7 +191,6 @@ Here is a sample of a source configuration file, a section in `solrconfig.xml`.
</updateHandler>
----
-// OLD_CONFLUENCE_ID: CrossDataCenterReplication(CDCR)-TargetConfiguration
[[CrossDataCenterReplication_CDCR_-TargetConfiguration]]
=== Target Configuration
@@ -503,7 +498,6 @@ http://host:8983/solr/<collection_name>/cdcr?action=START
}
----
-// OLD_CONFLUENCE_ID: CrossDataCenterReplication(CDCR)-Monitoringcommands
[[CrossDataCenterReplication_CDCR_-Monitoringcommands]]
=== Monitoring commands
http://git-wip-us.apache.org/repos/asf/lucene-solr/blob/4a0b9b53/solr/solr-ref-guide/src/faceting.adoc
----------------------------------------------------------------------
diff --git a/solr/solr-ref-guide/src/faceting.adoc b/solr/solr-ref-guide/src/faceting.adoc
index b6a0ebf..26bfbe2 100644
--- a/solr/solr-ref-guide/src/faceting.adoc
+++ b/solr/solr-ref-guide/src/faceting.adoc
@@ -341,7 +341,6 @@ For more information, see the examples in the <<working-with-dates.adoc#working-
====
-// OLD_CONFLUENCE_ID: Faceting-Pivot(DecisionTree)Faceting
[[Faceting-Pivot_DecisionTree_Faceting]]
== Pivot (Decision Tree) Faceting
http://git-wip-us.apache.org/repos/asf/lucene-solr/blob/4a0b9b53/solr/solr-ref-guide/src/other-schema-elements.adoc
----------------------------------------------------------------------
diff --git a/solr/solr-ref-guide/src/other-schema-elements.adoc b/solr/solr-ref-guide/src/other-schema-elements.adoc
index 4c8496f..42254eb 100644
--- a/solr/solr-ref-guide/src/other-schema-elements.adoc
+++ b/solr/solr-ref-guide/src/other-schema-elements.adoc
@@ -20,7 +20,6 @@ Schema defaults and `copyFields` cannot be used to populate the `uniqueKey` fiel
Further, the operation will fail if the `uniqueKey` field is used, but is multivalued (or inherits the multivalue-ness from the `fieldtype`). However, `uniqueKey` will continue to work, as long as the field is properly used.
-// OLD_CONFLUENCE_ID: OtherSchemaElements-DefaultSearchField&QueryOperator
[[OtherSchemaElements-DefaultSearchField_QueryOperator]]
== Default Search Field & Query Operator
http://git-wip-us.apache.org/repos/asf/lucene-solr/blob/4a0b9b53/solr/solr-ref-guide/src/phonetic-matching.adoc
----------------------------------------------------------------------
diff --git a/solr/solr-ref-guide/src/phonetic-matching.adoc b/solr/solr-ref-guide/src/phonetic-matching.adoc
index a3154dd..1f2f3c0 100644
--- a/solr/solr-ref-guide/src/phonetic-matching.adoc
+++ b/solr/solr-ref-guide/src/phonetic-matching.adoc
@@ -6,7 +6,6 @@ Phonetic matching algorithms may be used to encode tokens so that two different
For overviews of and comparisons between algorithms, see http://en.wikipedia.org/wiki/Phonetic_algorithm and http://ntz-develop.blogspot.com/2011/03/phonetic-algorithms.html
-// OLD_CONFLUENCE_ID: PhoneticMatching-Beider-MorsePhoneticMatching(BMPM)
[[PhoneticMatching-Beider-MorsePhoneticMatching_BMPM_]]
== Beider-Morse Phonetic Matching (BMPM)
http://git-wip-us.apache.org/repos/asf/lucene-solr/blob/4a0b9b53/solr/solr-ref-guide/src/rule-based-replica-placement.adoc
----------------------------------------------------------------------
diff --git a/solr/solr-ref-guide/src/rule-based-replica-placement.adoc b/solr/solr-ref-guide/src/rule-based-replica-placement.adoc
index 59e8300..8ca438d 100644
--- a/solr/solr-ref-guide/src/rule-based-replica-placement.adoc
+++ b/solr/solr-ref-guide/src/rule-based-replica-placement.adoc
@@ -48,7 +48,6 @@ A condition can have one of the following operators to set the parameters for th
* *less than (<)*: `tag:<x` means tag value less than ‘x’. x must be a number
* *not equal (!)*: `tag:!x` means tag value MUST NOT be equal to ‘x’. The equals check is performed on String value
-// OLD_CONFLUENCE_ID: Rule-basedReplicaPlacement-FuzzyOperator(~)
[[Rule-basedReplicaPlacement-FuzzyOperator_]]
=== Fuzzy Operator (~)
@@ -102,7 +101,6 @@ snitch=class:fqn.ClassName,key1:val1,key2:val2,key3:val3
[[Rule-basedReplicaPlacement-Examples]]
== Examples
-// OLD_CONFLUENCE_ID: Rule-basedReplicaPlacement-Keeplessthan2replicas(atmost1replica)ofthiscollectiononanynode
[[Rule-basedReplicaPlacement-Keeplessthan2replicas_atmost1replica_ofthiscollectiononanynode]]
=== Keep less than 2 replicas (at most 1 replica) of this collection on any node
@@ -115,7 +113,6 @@ replica:<2,node:*
// this is equivalent to replica:<2,node:*,shard:**. We can omit shard:** because ** is the default value of shard
----
-// OLD_CONFLUENCE_ID: Rule-basedReplicaPlacement-Foragivenshard,keeplessthan2replicasonanynode
[[Rule-basedReplicaPlacement-Foragivenshard_keeplessthan2replicasonanynode]]
=== For a given shard, keep less than 2 replicas on any node
http://git-wip-us.apache.org/repos/asf/lucene-solr/blob/4a0b9b53/solr/solr-ref-guide/src/running-solr-on-hdfs.adoc
----------------------------------------------------------------------
diff --git a/solr/solr-ref-guide/src/running-solr-on-hdfs.adoc b/solr/solr-ref-guide/src/running-solr-on-hdfs.adoc
index e6097c5..de0ecde 100644
--- a/solr/solr-ref-guide/src/running-solr-on-hdfs.adoc
+++ b/solr/solr-ref-guide/src/running-solr-on-hdfs.adoc
@@ -53,7 +53,6 @@ bin/solr start -c -Dsolr.directoryFactory=HdfsDirectoryFactory
This command starts Solr in SolrCloud mode, using the defined JVM properties.
-// OLD_CONFLUENCE_ID: RunningSolronHDFS-Modifyingsolr.in.sh(*nix)orsolr.in.cmd(Windows)
[[RunningSolronHDFS-Modifyingsolr.in.sh_nix_orsolr.in.cmd_Windows_]]
=== Modifying solr.in.sh (*nix) or solr.in.cmd (Windows)
http://git-wip-us.apache.org/repos/asf/lucene-solr/blob/4a0b9b53/solr/solr-ref-guide/src/solr-control-script-reference.adoc
----------------------------------------------------------------------
diff --git a/solr/solr-ref-guide/src/solr-control-script-reference.adoc b/solr/solr-ref-guide/src/solr-control-script-reference.adoc
index d7f4286..3d5a7f7 100644
--- a/solr/solr-ref-guide/src/solr-control-script-reference.adoc
+++ b/solr/solr-ref-guide/src/solr-control-script-reference.adoc
@@ -421,7 +421,6 @@ NOTE: Solr should have been started at least once before issuing these commands
Use the `zk upconfig` command to upload one of the pre-configured configuration set or a customized configuration set to ZooKeeper.
-// OLD_CONFLUENCE_ID: SolrControlScriptReference-AvailableParameters(allparametersarerequired)
[[SolrControlScriptReference-AvailableParameters_allparametersarerequired_]]
==== Available Parameters (all parameters are required)
@@ -467,7 +466,6 @@ This command does *not* automatically make changes effective! It simply uploads
Use the `zk downconfig` command to download a configuration set from ZooKeeper to the local filesystem.
-// OLD_CONFLUENCE_ID: SolrControlScriptReference-AvailableParameters(allparametersarerequired).1
[[SolrControlScriptReference-AvailableParameters_allparametersarerequired_.1]]
==== Available Parameters (all parameters are required)
@@ -563,7 +561,6 @@ An example of this command with the parameters is:
`bin/solr zk rm /configs/myconfigset/schema.xml`
-// OLD_CONFLUENCE_ID: SolrControlScriptReference-MoveOneZooKeeperznodetoAnother(Rename)
[[SolrControlScriptReference-MoveOneZooKeeperznodetoAnother_Rename_]]
=== Move One ZooKeeper znode to Another (Rename)
@@ -587,7 +584,6 @@ An example of this command is:
`bin/solr zk mv /configs/oldconfigset /configs/newconfigset`
-// OLD_CONFLUENCE_ID: SolrControlScriptReference-ListaZooKeeperznode'sChildren
[[SolrControlScriptReference-ListaZooKeeperznode_sChildren]]
=== List a ZooKeeper znode's Children
@@ -613,7 +609,6 @@ An example of this command with the parameters is:
`bin/solr zk ls /collections`
-// OLD_CONFLUENCE_ID: SolrControlScriptReference-Createaznode(supportschroot)
[[SolrControlScriptReference-Createaznode_supportschroot_]]
=== Create a znode (supports chroot)
http://git-wip-us.apache.org/repos/asf/lucene-solr/blob/4a0b9b53/solr/solr-ref-guide/src/spatial-search.adoc
----------------------------------------------------------------------
diff --git a/solr/solr-ref-guide/src/spatial-search.adoc b/solr/solr-ref-guide/src/spatial-search.adoc
index f4268a4..af1d0ba 100644
--- a/solr/solr-ref-guide/src/spatial-search.adoc
+++ b/solr/solr-ref-guide/src/spatial-search.adoc
@@ -120,7 +120,6 @@ Here's an example:
LatLonType (deprecated) does *not* support rectangles that cross the dateline. For RPT and BBoxField, if you are non-geospatial coordinates (`geo="false"`) then you must quote the points due to the space, e.g. `"x y"`.
-// OLD_CONFLUENCE_ID: SpatialSearch-Optimizing:CacheorNot
[[SpatialSearch-Optimizing_CacheorNot]]
=== Optimizing: Cache or Not
@@ -133,7 +132,6 @@ If you know the filter query (be it spatial or not) is fairly unique and not lik
LLPSF does not support Solr's "PostFilter".
-// OLD_CONFLUENCE_ID: SpatialSearch-DistanceSortingorBoosting(FunctionQueries)
[[SpatialSearch-DistanceSortingorBoosting_FunctionQueries_]]
== Distance Sorting or Boosting (Function Queries)
http://git-wip-us.apache.org/repos/asf/lucene-solr/blob/4a0b9b53/solr/solr-ref-guide/src/spell-checking.adoc
----------------------------------------------------------------------
diff --git a/solr/solr-ref-guide/src/spell-checking.adoc b/solr/solr-ref-guide/src/spell-checking.adoc
index e6f8618..770ea44 100644
--- a/solr/solr-ref-guide/src/spell-checking.adoc
+++ b/solr/solr-ref-guide/src/spell-checking.adoc
@@ -276,7 +276,6 @@ This parameter specifies the maximum number of documents that should be collect
The default value for this parameter is *0*, but when `spellcheck.collateExtendedResults` is *false*, the optimization is always used as if a *1* had been specified.
-// OLD_CONFLUENCE_ID: SpellChecking-Thespellcheck.collateParam.*ParameterPrefix
[[SpellChecking-Thespellcheck.collateParam._ParameterPrefix]]
=== The `spellcheck.collateParam.*` Parameter Prefix
@@ -293,7 +292,6 @@ This parameter causes Solr to use the dictionary named in the parameter's argume
Specifies an accuracy value to be used by the spell checking implementation to decide whether a result is worthwhile or not. The value is a float between 0 and 1. Defaults to `Float.MIN_VALUE`.
-// OLD_CONFLUENCE_ID: SpellChecking-Thespellcheck.<DICT_NAME>.keyParameter
[[spellcheck_DICT_NAME]]
=== The `spellcheck.<DICT_NAME>.key` Parameter
http://git-wip-us.apache.org/repos/asf/lucene-solr/blob/4a0b9b53/solr/solr-ref-guide/src/streaming-expressions.adoc
----------------------------------------------------------------------
diff --git a/solr/solr-ref-guide/src/streaming-expressions.adoc b/solr/solr-ref-guide/src/streaming-expressions.adoc
index 6dbf77f..665fbf9 100644
--- a/solr/solr-ref-guide/src/streaming-expressions.adoc
+++ b/solr/solr-ref-guide/src/streaming-expressions.adoc
@@ -551,7 +551,6 @@ topic(checkpointCollection,
Stream decorators wrap other stream functions or perform operations on the stream.
-// OLD_CONFLUENCE_ID: StreamingExpressions-cartesianProduct(6.6)
=== cartesianProduct
//TODO
http://git-wip-us.apache.org/repos/asf/lucene-solr/blob/4a0b9b53/solr/solr-ref-guide/src/the-dismax-query-parser.adoc
----------------------------------------------------------------------
diff --git a/solr/solr-ref-guide/src/the-dismax-query-parser.adoc b/solr/solr-ref-guide/src/the-dismax-query-parser.adoc
index f10bd4d..585e222 100644
--- a/solr/solr-ref-guide/src/the-dismax-query-parser.adoc
+++ b/solr/solr-ref-guide/src/the-dismax-query-parser.adoc
@@ -58,7 +58,6 @@ The `q` parameter does not support wildcard characters such as *.
If specified, the `q.alt` parameter defines a query (which by default will be parsed using standard query parsing syntax) when the main q parameter is not specified or is blank. The `q.alt` parameter comes in handy when you need something like a query to match all documents (don't forget `&rows=0` for that one!) in order to get collection-wide faceting counts.
-// OLD_CONFLUENCE_ID: TheDisMaxQueryParser-Theqf(QueryFields)Parameter
[[TheDisMaxQueryParser-Theqf_QueryFields_Parameter]]
=== The `qf` (Query Fields) Parameter
@@ -69,7 +68,6 @@ The `qf` parameter introduces a list of fields, each of which is assigned a boos
assigns `fieldOne` a boost of 2.3, leaves `fieldTwo` with the default boost (because no boost factor is specified), and `fieldThree` a boost of 0.4. These boost factors make matches in `fieldOne` much more significant than matches in `fieldTwo`, which in turn are much more significant than matches in `fieldThree`.
-// OLD_CONFLUENCE_ID: TheDisMaxQueryParser-Themm(MinimumShouldMatch)Parameter
[[TheDisMaxQueryParser-Themm_MinimumShouldMatch_Parameter]]
=== The `mm` (Minimum Should Match) Parameter
@@ -100,7 +98,6 @@ When specifying `mm` values, keep in mind the following:
The default value of `mm` is 100% (meaning that all clauses must match).
-// OLD_CONFLUENCE_ID: TheDisMaxQueryParser-Thepf(PhraseFields)Parameter
[[TheDisMaxQueryParser-Thepf_PhraseFields_Parameter]]
=== The `pf` (Phrase Fields) Parameter
@@ -109,21 +106,18 @@ Once the list of matching documents has been identified using the `fq` and `qf`
The format is the same as that used by the `qf` parameter: a list of fields and "boosts" to associate with each of them when making phrase queries out of the entire q parameter.
-// OLD_CONFLUENCE_ID: TheDisMaxQueryParser-Theps(PhraseSlop)Parameter
[[TheDisMaxQueryParser-Theps_PhraseSlop_Parameter]]
=== The `ps` (Phrase Slop) Parameter
The `ps` parameter specifies the amount of "phrase slop" to apply to queries specified with the pf parameter. Phrase slop is the number of positions one token needs to be moved in relation to another token in order to match a phrase specified in a query.
-// OLD_CONFLUENCE_ID: TheDisMaxQueryParser-Theqs(QueryPhraseSlop)Parameter
[[TheDisMaxQueryParser-Theqs_QueryPhraseSlop_Parameter]]
=== The `qs` (Query Phrase Slop) Parameter
The `qs` parameter specifies the amount of slop permitted on phrase queries explicitly included in the user's query string with the `qf` parameter. As explained above, slop refers to the number of positions one token needs to be moved in relation to another token in order to match a phrase specified in a query.
-// OLD_CONFLUENCE_ID: TheDisMaxQueryParser-Thetie(TieBreaker)Parameter
[[TheDisMaxQueryParser-Thetie_TieBreaker_Parameter]]
=== The `tie` (Tie Breaker) Parameter
@@ -134,7 +128,6 @@ When a term from the user's input is tested against multiple fields, more than o
A value of "0.0" - the default - makes the query a pure "disjunction max query": that is, only the maximum scoring subquery contributes to the final score. A value of "1.0" makes the query a pure "disjunction sum query" where it doesn't matter what the maximum scoring sub query is, because the final score will be the sum of the subquery scores. Typically a low value, such as 0.1, is useful.
-// OLD_CONFLUENCE_ID: TheDisMaxQueryParser-Thebq(BoostQuery)Parameter
[[TheDisMaxQueryParser-Thebq_BoostQuery_Parameter]]
=== The `bq` (Boost Query) Parameter
@@ -149,7 +142,6 @@ bq=date:[NOW/DAY-1YEAR TO NOW/DAY]
You can specify multiple `bq` parameters. If you want your query to be parsed as separate clauses with separate boosts, use multiple `bq` parameters.
-// OLD_CONFLUENCE_ID: TheDisMaxQueryParser-Thebf(BoostFunctions)Parameter
[[TheDisMaxQueryParser-Thebf_BoostFunctions_Parameter]]
=== The `bf` (Boost Functions) Parameter
http://git-wip-us.apache.org/repos/asf/lucene-solr/blob/4a0b9b53/solr/solr-ref-guide/src/the-extended-dismax-query-parser.adoc
----------------------------------------------------------------------
diff --git a/solr/solr-ref-guide/src/the-extended-dismax-query-parser.adoc b/solr/solr-ref-guide/src/the-extended-dismax-query-parser.adoc
index b13287d..3a9481b 100644
--- a/solr/solr-ref-guide/src/the-extended-dismax-query-parser.adoc
+++ b/solr/solr-ref-guide/src/the-extended-dismax-query-parser.adoc
@@ -145,7 +145,6 @@ f.name.qf=last_name first_name
Negative query boosts have been supported at the "Query" object level for a long time (resulting in negative scores for matching documents). Now the QueryParsers have been updated to handle this too.
-// OLD_CONFLUENCE_ID: TheExtendedDisMaxQueryParser-Using'slop'
[[TheExtendedDisMaxQueryParser-Using_slop_]]
== Using 'slop'
@@ -205,7 +204,6 @@ A document that contains "Hans Anderson" will match, but a document that contain
Finally, in addition to the phrase fields (`pf`) parameter, `edismax` also supports the `pf2` and `pf3` parameters, for fields over which to create bigram and trigram phrase queries. The phrase slop for these parameters' queries can be specified using the `ps2` and `ps3` parameters, respectively. If you use `pf2`/`pf3` but `ps2`/`ps3`, then the phrase slop for these parameters' queries will be taken from the `ps` parameter, if any.
-// OLD_CONFLUENCE_ID: TheExtendedDisMaxQueryParser-Usingthe'magicfields'_val_and_query_
[[TheExtendedDisMaxQueryParser-Usingthe_magicfields__val_and_query_]]
== Using the 'magic fields' `\_val_` and `\_query_`
http://git-wip-us.apache.org/repos/asf/lucene-solr/blob/4a0b9b53/solr/solr-ref-guide/src/the-standard-query-parser.adoc
----------------------------------------------------------------------
diff --git a/solr/solr-ref-guide/src/the-standard-query-parser.adoc b/solr/solr-ref-guide/src/the-standard-query-parser.adoc
index 11ff935..3f67c4a 100644
--- a/solr/solr-ref-guide/src/the-standard-query-parser.adoc
+++ b/solr/solr-ref-guide/src/the-standard-query-parser.adoc
@@ -24,7 +24,6 @@ In addition to the <<common-query-parameters.adoc#common-query-parameters,Common
Default parameter values are specified in `solrconfig.xml`, or overridden by query-time values in the request.
-// OLD_CONFLUENCE_ID: TheStandardQueryParser-TheStandardQueryParser'sResponse
[[TheStandardQueryParser-TheStandardQueryParser_sResponse]]
== The Standard Query Parser's Response
@@ -170,7 +169,6 @@ The brackets around a query determine its inclusiveness.
* Curly brackets `{` & `}` denote an exclusive range query that matches values between the upper and lower bounds, but excluding the upper and lower bounds themselves.
* You can mix these types so one end of the range is inclusive and the other is exclusive. Here's an example: `count:{1 TO 10]`
-// OLD_CONFLUENCE_ID: TheStandardQueryParser-BoostingaTermwith^
[[TheStandardQueryParser-BoostingaTermwith_]]
=== Boosting a Term with `^`
@@ -189,7 +187,6 @@ This will make documents with the term jakarta appear more relevant. You can als
By default, the boost factor is 1. Although the boost factor must be positive, it can be less than 1 (for example, it could be 0.2).
-// OLD_CONFLUENCE_ID: TheStandardQueryParser-ConstantScorewith^=
[[TheStandardQueryParser-ConstantScorewith_]]
=== Constant Score with `^=`
@@ -264,7 +261,6 @@ or
`"jakarta apache" OR jakarta`
-// OLD_CONFLUENCE_ID: TheStandardQueryParser-TheBooleanOperator+
[[TheStandardQueryParser-TheBooleanOperator_]]
=== The Boolean Operator `+`
@@ -282,7 +278,6 @@ This operator is supported by both the standard query parser and the DisMax quer
====
-// OLD_CONFLUENCE_ID: TheStandardQueryParser-TheBooleanOperatorAND(&&)
[[TheStandardQueryParser-TheBooleanOperatorAND_]]
=== The Boolean Operator AND (`&&`)
@@ -295,7 +290,6 @@ To search for documents that contain "jakarta apache" and "Apache Lucene," use e
`"jakarta apache" && "Apache Lucene"`
-// OLD_CONFLUENCE_ID: TheStandardQueryParser-TheBooleanOperatorNOT(!)
[[TheStandardQueryParser-TheBooleanOperatorNOT_]]
=== The Boolean Operator NOT (`!`)
http://git-wip-us.apache.org/repos/asf/lucene-solr/blob/4a0b9b53/solr/solr-ref-guide/src/the-terms-component.adoc
----------------------------------------------------------------------
diff --git a/solr/solr-ref-guide/src/the-terms-component.adoc b/solr/solr-ref-guide/src/the-terms-component.adoc
index 3a8b79e..1625be2 100644
--- a/solr/solr-ref-guide/src/the-terms-component.adoc
+++ b/solr/solr-ref-guide/src/the-terms-component.adoc
@@ -182,7 +182,6 @@ Results:
</response>
----
-// OLD_CONFLUENCE_ID: TheTermsComponent-GetFirst10TermsStartingwithLetter'a'
[[TheTermsComponent-GetFirst10TermsStartingwithLetter_a_]]
=== Get First 10 Terms Starting with Letter 'a'
http://git-wip-us.apache.org/repos/asf/lucene-solr/blob/4a0b9b53/solr/solr-ref-guide/src/transforming-result-documents.adoc
----------------------------------------------------------------------
diff --git a/solr/solr-ref-guide/src/transforming-result-documents.adoc b/solr/solr-ref-guide/src/transforming-result-documents.adoc
index 47a7177..33bb88e 100644
--- a/solr/solr-ref-guide/src/transforming-result-documents.adoc
+++ b/solr/solr-ref-guide/src/transforming-result-documents.adoc
@@ -33,7 +33,6 @@ The sections below discuss exactly what these various transformers do.
[[TransformingResultDocuments-AvailableTransformers]]
== Available Transformers
-// OLD_CONFLUENCE_ID: TransformingResultDocuments-[value]-ValueAugmenterFactory
[[TransformingResultDocuments-_value_-ValueAugmenterFactory]]
=== `[value]` - ValueAugmenterFactory
@@ -78,7 +77,6 @@ In addition to using these request parameters, you can configure additional name
The "```value```" option forces an explicit value to always be used, while the "```defaultValue```" option provides a default that can still be overridden using the "```v```" and "```t```" local parameters.
-// OLD_CONFLUENCE_ID: TransformingResultDocuments-[explain]-ExplainAugmenterFactory
[[TransformingResultDocuments-_explain_-ExplainAugmenterFactory]]
=== `[explain]` - ExplainAugmenterFactory
@@ -114,7 +112,6 @@ A default style can be configured by specifying an "args" parameter in your conf
</transformer>
----
-// OLD_CONFLUENCE_ID: TransformingResultDocuments-[child]-ChildDocTransformerFactory
[[TransformingResultDocuments-_child_-ChildDocTransformerFactory]]
=== `[child]` - ChildDocTransformerFactory
@@ -133,7 +130,6 @@ When using this transformer, the `parentFilter` parameter must be specified, and
* `childFilter` - query to filter which child documents should be included, this can be particularly useful when you have multiple levels of hierarchical documents (default: all children)
* `limit` - the maximum number of child documents to be returned per parent document (default: 10)
-// OLD_CONFLUENCE_ID: TransformingResultDocuments-[shard]-ShardAugmenterFactory
[[TransformingResultDocuments-_shard_-ShardAugmenterFactory]]
=== `[shard]` - ShardAugmenterFactory
@@ -142,7 +138,6 @@ This transformer adds information about what shard each individual document came
ShardAugmenterFactory does not support any request parameters, or configuration options.
-// OLD_CONFLUENCE_ID: TransformingResultDocuments-[docid]-DocIdAugmenterFactory
[[TransformingResultDocuments-_docid_-DocIdAugmenterFactory]]
=== `[docid]` - DocIdAugmenterFactory
@@ -151,7 +146,6 @@ This transformer adds the internal Lucene document id to each document – this
DocIdAugmenterFactory does not support any request parameters, or configuration options.
-// OLD_CONFLUENCE_ID: TransformingResultDocuments-[elevated]and[excluded]
[[TransformingResultDocuments-_elevated_and_excluded_]]
=== `[elevated]` and `[excluded]`
@@ -184,7 +178,6 @@ fl=id,[elevated],[excluded]&excludeIds=GB18030TEST&elevateIds=6H500F0&markExclud
...
----
-// OLD_CONFLUENCE_ID: TransformingResultDocuments-[json]/[xml]
[[TransformingResultDocuments-_json_xml_]]
=== `[json]` / `[xml]`
@@ -196,7 +189,6 @@ These transformers replace field value containing a string representation of a v
fl=id,source_s:[json]&wt=json
----
-// OLD_CONFLUENCE_ID: TransformingResultDocuments-[subquery]
[[TransformingResultDocuments-_subquery_]]
=== `[subquery]`
@@ -301,7 +293,6 @@ If subquery collection has a different unique key field name (let's say `foo_id`
====
-// OLD_CONFLUENCE_ID: TransformingResultDocuments-[geo]-Geospatialformatter
[[TransformingResultDocuments-_geo_-Geospatialformatter]]
=== `[geo]` - Geospatial formatter
@@ -312,7 +303,6 @@ Normally you'll simply be consistent in choosing the format type you want by set
In addition, this feature is very useful with the `RptWithGeometrySpatialField` to avoid double-storage of the potentially large vector geometry. This transformer will detect that field type and fetch the geometry from an internal compact binary representation on disk (in docValues), and then format it as desired. As such, you needn't mark the field as stored, which would be redundant. In a sense this double-storage between docValues and stored-value storage isn't unique to spatial but with polygonal geometry it can be a lot of data, and furthermore you'd like to avoid storing it in a verbose format (like GeoJSON or WKT).
-// OLD_CONFLUENCE_ID: TransformingResultDocuments-[features]-LTRFeatureLoggerTransformerFactory
[[TransformingResultDocuments-_features_-LTRFeatureLoggerTransformerFactory]]
=== `[features]` - LTRFeatureLoggerTransformerFactory
http://git-wip-us.apache.org/repos/asf/lucene-solr/blob/4a0b9b53/solr/solr-ref-guide/src/understanding-analyzers-tokenizers-and-filters.adoc
----------------------------------------------------------------------
diff --git a/solr/solr-ref-guide/src/understanding-analyzers-tokenizers-and-filters.adoc b/solr/solr-ref-guide/src/understanding-analyzers-tokenizers-and-filters.adoc
index b84afa0..e3e8aea 100644
--- a/solr/solr-ref-guide/src/understanding-analyzers-tokenizers-and-filters.adoc
+++ b/solr/solr-ref-guide/src/understanding-analyzers-tokenizers-and-filters.adoc
@@ -9,7 +9,6 @@ The following sections describe how Solr breaks down and works with textual data
* <<about-tokenizers.adoc#about-tokenizers,Tokenizers>> break field data into lexical units, or __tokens__.
* <<about-filters.adoc#about-filters,Filters>> examine a stream of tokens and keep them, transform or discard them, or create new ones. Tokenizers and filters may be combined to form pipelines, or __chains__, where the output of one is input to the next. Such a sequence of tokenizers and filters is called an _analyzer_ and the resulting output of an analyzer is used to match query results or build indices.
-// OLD_CONFLUENCE_ID: UnderstandingAnalyzers,Tokenizers,andFilters-UsingAnalyzers,Tokenizers,andFilters
[[UnderstandingAnalyzers_Tokenizers_andFilters-UsingAnalyzers_Tokenizers_andFilters]]
== Using Analyzers, Tokenizers, and Filters
@@ -18,7 +17,6 @@ Although the analysis process is used for both indexing and querying, the same a
The tokens output by the analysis process define the values, or __terms__, of that field and are used either to build an index of those terms when a new document is added, or to identify which documents contain the terms you are querying for.
-// OLD_CONFLUENCE_ID: UnderstandingAnalyzers,Tokenizers,andFilters-ForMoreInformation
[[UnderstandingAnalyzers_Tokenizers_andFilters-ForMoreInformation]]
== For More Information
http://git-wip-us.apache.org/repos/asf/lucene-solr/blob/4a0b9b53/solr/solr-ref-guide/src/update-request-processors.adoc
----------------------------------------------------------------------
diff --git a/solr/solr-ref-guide/src/update-request-processors.adoc b/solr/solr-ref-guide/src/update-request-processors.adoc
index 3a0cc49..e69adbb 100644
--- a/solr/solr-ref-guide/src/update-request-processors.adoc
+++ b/solr/solr-ref-guide/src/update-request-processors.adoc
@@ -178,7 +178,6 @@ curl "http://localhost:8983/solr/gettingstarted/update/json?update.chain=dedupe&
The above should dedupe the two identical documents and index only one of them.
-// OLD_CONFLUENCE_ID: UpdateRequestProcessors-Processor&Post-ProcessorRequestParameters
[[UpdateRequestProcessors-Processor_Post-ProcessorRequestParameters]]
=== Processor & Post-Processor Request Parameters
http://git-wip-us.apache.org/repos/asf/lucene-solr/blob/4a0b9b53/solr/solr-ref-guide/src/upgrading-a-solr-cluster.adoc
----------------------------------------------------------------------
diff --git a/solr/solr-ref-guide/src/upgrading-a-solr-cluster.adoc b/solr/solr-ref-guide/src/upgrading-a-solr-cluster.adoc
index b520633..c51b55d 100644
--- a/solr/solr-ref-guide/src/upgrading-a-solr-cluster.adoc
+++ b/solr/solr-ref-guide/src/upgrading-a-solr-cluster.adoc
@@ -38,14 +38,12 @@ You should now be ready to upgrade your cluster. Please verify this process in a
The approach we recommend is to perform the upgrade of each Solr node, one-by-one. In other words, you will need to stop a node, upgrade it to the new version of Solr, and restart it before moving on to the next node. This means that for a short period of time, there will be a mix of "Old Solr" and "New Solr" nodes running in your cluster. We also assume that you will point the new Solr node to your existing Solr home directory where the Lucene index files are managed for each collection on the node. This means that you won't need to move any index files around to perform the upgrade.
-// OLD_CONFLUENCE_ID: UpgradingaSolrCluster-Step1:StopSolr
[[UpgradingaSolrCluster-Step1_StopSolr]]
=== Step 1: Stop Solr
Begin by stopping the Solr node you want to upgrade. After stopping the node, if using a replication, (ie: collections with replicationFactor > 1) verify that all leaders hosted on the downed node have successfully migrated to other replicas; you can do this by visiting the <<cloud-screens.adoc#cloud-screens,Cloud panel in the Solr Admin UI>>. If not using replication, then any collections with shards hosted on the downed node will be temporarily off-line.
-// OLD_CONFLUENCE_ID: UpgradingaSolrCluster-Step2:InstallSolrasaService
[[UpgradingaSolrCluster-Step2_InstallSolrasaService]]
=== Step 2: Install Solr as a Service
@@ -59,7 +57,6 @@ If you have a `/var/solr/solr.in.sh` file for your existing Solr install, runnin
====
-// OLD_CONFLUENCE_ID: UpgradingaSolrCluster-Step3:SetEnvironmentVariableOverrides
[[UpgradingaSolrCluster-Step3_SetEnvironmentVariableOverrides]]
=== Step 3: Set Environment Variable Overrides
@@ -70,14 +67,12 @@ Open `/etc/default/solr.in.sh` with a text editor and verify that the following
Make sure the user you plan to own the Solr process is the owner of the `SOLR_HOME` directory. For instance, if you plan to run Solr as the "solr" user and `SOLR_HOME` is `/var/solr/data`, then you would do: `sudo chown -R solr: /var/solr/data`
-// OLD_CONFLUENCE_ID: UpgradingaSolrCluster-Step4:StartSolr
[[UpgradingaSolrCluster-Step4_StartSolr]]
=== Step 4: Start Solr
You are now ready to start the upgraded Solr node by doing: `sudo service solr start`. The upgraded instance will join the existing cluster because you're using the same `SOLR_HOME`, `SOLR_PORT`, and `SOLR_HOST` settings used by the old Solr node; thus, the new server will look like the old node to the running cluster. Be sure to look in `/var/solr/logs/solr.log` for errors during startup.
-// OLD_CONFLUENCE_ID: UpgradingaSolrCluster-Step5:RunHealthcheck
[[UpgradingaSolrCluster-Step5_RunHealthcheck]]
=== Step 5: Run Healthcheck
http://git-wip-us.apache.org/repos/asf/lucene-solr/blob/4a0b9b53/solr/solr-ref-guide/src/uploading-data-with-solr-cell-using-apache-tika.adoc
----------------------------------------------------------------------
diff --git a/solr/solr-ref-guide/src/uploading-data-with-solr-cell-using-apache-tika.adoc b/solr/solr-ref-guide/src/uploading-data-with-solr-cell-using-apache-tika.adoc
index fc678d6..0247e98 100644
--- a/solr/solr-ref-guide/src/uploading-data-with-solr-cell-using-apache-tika.adoc
+++ b/solr/solr-ref-guide/src/uploading-data-with-solr-cell-using-apache-tika.adoc
@@ -256,7 +256,6 @@ The command below captures `<div>` tags separately, and then maps all the instan
bin/post -c techproducts example/exampledocs/sample.html -params "literal.id=doc2&captureAttr=true&defaultField=_text_&fmap.div=foo_t&capture=div"
----
-// OLD_CONFLUENCE_ID: UploadingDatawithSolrCellusingApacheTika-Capture&Mapping
[[UploadingDatawithSolrCellusingApacheTika-Capture_Mapping]]
==== Capture & Mapping
http://git-wip-us.apache.org/repos/asf/lucene-solr/blob/4a0b9b53/solr/solr-ref-guide/src/using-zookeeper-to-manage-configuration-files.adoc
----------------------------------------------------------------------
diff --git a/solr/solr-ref-guide/src/using-zookeeper-to-manage-configuration-files.adoc b/solr/solr-ref-guide/src/using-zookeeper-to-manage-configuration-files.adoc
index 77bc78f..53cdbc3 100644
--- a/solr/solr-ref-guide/src/using-zookeeper-to-manage-configuration-files.adoc
+++ b/solr/solr-ref-guide/src/using-zookeeper-to-manage-configuration-files.adoc
@@ -40,7 +40,6 @@ It's a good idea to keep these files under version control.
====
-// OLD_CONFLUENCE_ID: UsingZooKeepertoManageConfigurationFiles-UploadingConfigurationFilesusingbin/solrorSolrJ
[[UsingZooKeepertoManageConfigurationFiles-UploadingConfigurationFilesusingbin_solrorSolrJ]]
== Uploading Configuration Files using `bin/solr` or SolrJ
http://git-wip-us.apache.org/repos/asf/lucene-solr/blob/4a0b9b53/solr/solr-ref-guide/src/zookeeper-access-control.adoc
----------------------------------------------------------------------
diff --git a/solr/solr-ref-guide/src/zookeeper-access-control.adoc b/solr/solr-ref-guide/src/zookeeper-access-control.adoc
index c5befa6..ef17062 100644
--- a/solr/solr-ref-guide/src/zookeeper-access-control.adoc
+++ b/solr/solr-ref-guide/src/zookeeper-access-control.adoc
@@ -81,7 +81,6 @@ Notice the overlap in system property names with credentials provider `VMParamsS
You can give the readonly credentials to "clients" of your SolrCloud cluster - e.g. to be used by SolrJ clients. They will be able to read whatever is necessary to run a functioning SolrJ client, but they will not be able to modify any content in ZooKeeper.
-// OLD_CONFLUENCE_ID: ZooKeeperAccessControl-bin/solr&solr.cmd,server/scripts/cloud-scripts/zkcli.sh&zkcli.bat
[[ZooKeeperAccessControl-bin_solr_solr.cmd_server_scripts_cloud-scripts_zkcli.sh_zkcli.bat]]
=== `bin/solr` & `solr.cmd`, `server/scripts/cloud-scripts/zkcli.sh` & `zkcli.bat`