/select` resource and
-protocol buffer query messages from legacy Riak Search to new Search
+protocol buffer query messages from legacy Riak search to new Search
(Yokozuna).
## services
diff --git a/content/riak/kv/2.1.3/using/cluster-operations/active-anti-entropy.md b/content/riak/kv/2.1.3/using/cluster-operations/active-anti-entropy.md
index c262cc7164..62c80485fb 100644
--- a/content/riak/kv/2.1.3/using/cluster-operations/active-anti-entropy.md
+++ b/content/riak/kv/2.1.3/using/cluster-operations/active-anti-entropy.md
@@ -262,9 +262,9 @@ AAE-related background tasks, analogous to [open files limit](../../performance/
## AAE and Riak Search
Riak's AAE subsystem works to repair object inconsistencies both with
-for normal key/value objects as well as data related to [Riak Search](../../../developing/usage/search). In particular, AAE acts on indexes stored in
+for normal key/value objects as well as data related to [Riak search](../../../developing/usage/search). In particular, AAE acts on indexes stored in
[Solr](http://lucene.apache.org/solr/), the search platform that drives
-Riak Search. Implementation details for AAE and Search can be found in
+Riak search. Implementation details for AAE and Search can be found in
the [Search Details](../../reference/search/#active-anti-entropy-aae)
documentation.
diff --git a/content/riak/kv/2.1.3/using/cluster-operations/inspecting-node.md b/content/riak/kv/2.1.3/using/cluster-operations/inspecting-node.md
index ab99a21e04..b13b788056 100644
--- a/content/riak/kv/2.1.3/using/cluster-operations/inspecting-node.md
+++ b/content/riak/kv/2.1.3/using/cluster-operations/inspecting-node.md
@@ -297,7 +297,7 @@ Stat | Description
`erlydtl_version` | [ErlyDTL](http://github.com/erlydtl/erlydtl)
`riak_control_version` | [Riak Control](http://github.com/basho/riak_control)
`cluster_info_version` | [Cluster Information](http://github.com/basho/cluster_info)
-`riak_search_version` | [Riak Search](http://github.com/basho/riak_search)
+`riak_search_version` | [Riak search](http://github.com/basho/riak_search)
`merge_index_version` | [Merge Index](http://github.com/basho/merge_index)
`riak_kv_version` | [Riak KV](http://github.com/basho/riak_kv)
`sidejob_version` | [Sidejob](http://github.com/basho/sidejob)
@@ -326,17 +326,17 @@ Stat | Description
### Riak Search Statistics
-The following statistics related to Riak Search message queues are
+The following statistics related to Riak search message queues are
available.
Stat | Description
-----------------------------|---------------------------------------------------
-`riak_search_vnodeq_max` | Maximum number of unprocessed messages all virtual node (vnode) message queues in the Riak Search subsystem have received on this node in the last minute
-`riak_search_vnodeq_mean` | Mean number of unprocessed messages all vnode message queues in the Riak Search subsystem have received on this node in the last minute
-`riak_search_vnodeq_median` | Median number of unprocessed messages all vnode message queues in the Riak Search subsystem have received on this node in the last minute
-`riak_search_vnodeq_min` | Minimum number of unprocessed messages all vnode message queues in the Riak Search subsystem have received on this node in the last minute
-`riak_search_vnodeq_total` | Total number of unprocessed messages all vnode message queues in the Riak Search subsystem have received on this node since it was started
-`riak_search_vnodes_running` | Total number of vnodes currently running in the Riak Search subsystem
+`riak_search_vnodeq_max` | Maximum number of unprocessed messages all virtual node (vnode) message queues in the Riak search subsystem have received on this node in the last minute
+`riak_search_vnodeq_mean` | Mean number of unprocessed messages all vnode message queues in the Riak search subsystem have received on this node in the last minute
+`riak_search_vnodeq_median` | Median number of unprocessed messages all vnode message queues in the Riak search subsystem have received on this node in the last minute
+`riak_search_vnodeq_min` | Minimum number of unprocessed messages all vnode message queues in the Riak search subsystem have received on this node in the last minute
+`riak_search_vnodeq_total` | Total number of unprocessed messages all vnode message queues in the Riak search subsystem have received on this node since it was started
+`riak_search_vnodes_running` | Total number of vnodes currently running in the Riak search subsystem
Note that under ideal operation and with the exception of
`riak_search_vnodes_running` these statistics should contain low values
@@ -449,7 +449,7 @@ Check | Description
`ring_membership` | Cluster membership validity
`ring_preflists` | Check if the ring satisfies `n_val`
`ring_size` | Check if the ring size valid
-`search` | Check whether Riak Search is enabled on all nodes
+`search` | Check whether Riak search is enabled on all nodes
The `--level` flag enables you to specify the log level and thus to
filter messages based on type. You can pass in any of the message types
diff --git a/content/riak/kv/2.1.3/using/cluster-operations/strong-consistency.md b/content/riak/kv/2.1.3/using/cluster-operations/strong-consistency.md
index f3533afbff..1542d5c9f7 100644
--- a/content/riak/kv/2.1.3/using/cluster-operations/strong-consistency.md
+++ b/content/riak/kv/2.1.3/using/cluster-operations/strong-consistency.md
@@ -14,7 +14,7 @@ toc: true
Please Note:
-Riak KV's strong consistency is an experimental feature and may be removed from the product in the future. Strong consistency is not commercially supported or production-ready. Strong consistency is incompatible with Multi-Datacenter Replication, Riak Search, Bitcask Expiration, LevelDB Secondary Indexes, Riak Data Types and Commit Hooks. We do not recommend its usage in any production environment.
+Riak KV's strong consistency is an experimental feature and may be removed from the product in the future. Strong consistency is not commercially supported or production-ready. Strong consistency is incompatible with Multi-Datacenter Replication, Riak search, Bitcask Expiration, LevelDB Secondary Indexes, Riak Data Types and Commit Hooks. We do not recommend its usage in any production environment.
## Monitoring Strong Consistency
diff --git a/content/riak/kv/2.1.3/using/reference/handoff.md b/content/riak/kv/2.1.3/using/reference/handoff.md
index 5d2aa0f04d..afb6608eeb 100644
--- a/content/riak/kv/2.1.3/using/reference/handoff.md
+++ b/content/riak/kv/2.1.3/using/reference/handoff.md
@@ -121,7 +121,7 @@ handoff.use_background_manager = on
### Maximum Rejects
-If you're using Riak features such as [Riak Search](/riak/kv/2.1.3/developing/usage/search/),
+If you're using Riak features such as [Riak search](/riak/kv/2.1.3/developing/usage/search/),
those subsystems can block handoff of primary key/value data, i.e. data
that you interact with via normal reads and writes.
diff --git a/content/riak/kv/2.1.3/using/reference/search.md b/content/riak/kv/2.1.3/using/reference/search.md
index 9c67db4b59..5ef21b03f0 100644
--- a/content/riak/kv/2.1.3/using/reference/search.md
+++ b/content/riak/kv/2.1.3/using/reference/search.md
@@ -19,14 +19,14 @@ aliases:
> **Note on Search 2.0 vs. Legacy Search**
>
-> This document refers to the new Riak Search 2.0 with
+> This document refers to the new Riak search 2.0 with
[Solr](http://lucene.apache.org/solr/) integration (codenamed
-Yokozuna). For information about the deprecated Riak Search, visit [the old Using Riak Search docs](http://docs.basho.com/riak/1.4.10/dev/using/search/).
+Yokozuna). For information about the deprecated Riak search, visit [the old Using Riak search docs](http://docs.basho.com/riak/1.4.10/dev/using/search/).
-The project that implements Riak Search is codenamed Yokozuna. This is a
+The project that implements Riak search is codenamed Yokozuna. This is a
more detailed overview of the concepts and reasons behind the design of
Yokozuna, for those interested. If you're simply looking to use Riak
-Search, you should check out the [Using Search](/riak/kv/2.1.3/developing/usage/search) document.
+search, you should check out the [Using Search](/riak/kv/2.1.3/developing/usage/search) document.
@@ -35,30 +35,30 @@ Search, you should check out the [Using Search](/riak/kv/2.1.3/developing/usage/
In Erlang OTP, an "application" is a group of modules and Erlang
processes which together perform a specific task. The word application
is confusing because most people think of an application as an entire
-program such as Emacs or Photoshop. But Riak Search is just a sub-system
+program such as Emacs or Photoshop. But Riak search is just a sub-system
in Riak itself. Erlang applications are often stand-alone, but Riak
-Search is more like an appendage of Riak. It requires other subsystems
+search is more like an appendage of Riak. It requires other subsystems
like Riak Core and KV, but also extends their functionality by providing
search capabilities for KV data.
-The purpose of Riak Search is to bring more sophisticated and robust
+The purpose of Riak search is to bring more sophisticated and robust
query and search support to Riak. Many people consider Lucene and
programs built on top of it, such as Solr, as the standard for
open-source search. There are many successful applications built on
Lucene/Solr, and it sets the standard for the feature set that
developers and users expect. Meanwhile, Riak has a great story as a
-highly-available, distributed key/value store. Riak Search takes
+highly-available, distributed key/value store. Riak search takes
advantage of the fact that Riak already knows how to do the distributed
bits, combining its feature set with that of Solr, taking advantage of
the strengths of each.
-Riak Search is a mediator between Riak and Solr. There is nothing
+Riak search is a mediator between Riak and Solr. There is nothing
stopping a user from deploying these two programs separately, but this
would leave the user responsible for the glue between them. That glue
can be tricky to write. It requires dealing with monitoring, querying,
indexing, and dissemination of information.
-Unlike Solr by itself, Riak Search knows how to do all of the following:
+Unlike Solr by itself, Riak search knows how to do all of the following:
* Listen for changes in key/value (KV) data and to make the appropriate
changes to indexes that live in Solr. It also knows how to take a user
@@ -75,13 +75,13 @@ system (OS) process running a JVM which hosts Solr on the Jetty
application server. This OS process is a child of the Erlang OS process
running Riak.
-Riak Search has a `gen_server` process which monitors the JVM OS
+Riak search has a `gen_server` process which monitors the JVM OS
process. The code for this server is in `yz_solr_proc`. When the JVM
process crashes, this server crashes, causing its supervisor to restart
it.
If there is more than 1 restart in 45 seconds, the entire Riak node will
-be shut down. If Riak Search is enabled and Solr cannot function for
+be shut down. If Riak search is enabled and Solr cannot function for
some reason, the Riak node needs to go down so that the user will notice
and take corrective action.
@@ -91,7 +91,7 @@ This double monitoring along with the crash semantics means that neither
process may exist without the other. They are either both up or both
down.
-All other communication between Riak Search and Solr is performed via
+All other communication between Riak search and Solr is performed via
HTTP, including querying, indexing, and administration commands. The
ibrowse Erlang HTTP client is used to manage these communications as
both it and the Jetty container hosting Solr pool HTTP connections,
@@ -105,11 +105,11 @@ contains index entries for objects. Each such index maintains its own
set of files on disk---a critical difference from Riak KV, in which a
bucket is a purely logical entity and not physically disjoint at all. A
Solr index requires significantly less disk space than the corresponding
-legacy Riak Search index, depending on the Solr schema used.
+legacy Riak search index, depending on the Solr schema used.
Indexes may be associated with zero or more buckets. At creation time,
however, each index has no associated buckets---unlike the legacy Riak
-Search, indexes in the new Riak Search do not implicitly create bucket
+search, indexes in the new Riak search do not implicitly create bucket
associations, meaning that this must be done as a separate configuration
step.
@@ -141,7 +141,7 @@ flat collection of field-value pairs. "Flat" here means that a field's
value cannot be a nested structure of field-value pairs; the values are
treated as-is (non-composite is another way to say it).
-Because of this mismatch between KV and Solr, Riak Search must act as a
+Because of this mismatch between KV and Solr, Riak search must act as a
mediator between the two, meaning it must have a way to inspect a KV
object and create a structure which Solr can ingest for indexing. In
Solr this structure is called a **document**. This task of creating a
diff --git a/content/riak/kv/2.1.3/using/reference/secondary-indexes.md b/content/riak/kv/2.1.3/using/reference/secondary-indexes.md
index 1bbd238051..c0658e64e7 100644
--- a/content/riak/kv/2.1.3/using/reference/secondary-indexes.md
+++ b/content/riak/kv/2.1.3/using/reference/secondary-indexes.md
@@ -18,11 +18,11 @@ aliases:
[usage bucket types]: /riak/kv/2.1.3/developing/usage/bucket-types
[use ref strong consistency]: /riak/2.1.3/using/reference/strong-consistency
-> **Note: Riak Search preferred for querying**
+> **Note: Riak search preferred for querying**
>
> If you're interested in non-primary-key-based querying in Riak, i.e. if
you're looking to go beyond straightforward K/V operations, we now
-recommend [Riak Search](/riak/kv/2.1.3/developing/usage/search/) rather than secondary indexes for a variety of reasons. Riak Search has a far more capacious querying API and can be used with all of Riak's storage backends.
+recommend [Riak search](/riak/kv/2.1.3/developing/usage/search/) rather than secondary indexes for a variety of reasons. Riak search has a far more capacious querying API and can be used with all of Riak's storage backends.
This document provides implementation and other details for Riak's
[secondary indexes](/riak/kv/2.1.3/developing/usage/secondary-indexes/) \(2i) feature.
diff --git a/content/riak/kv/2.1.3/using/reference/statistics-monitoring.md b/content/riak/kv/2.1.3/using/reference/statistics-monitoring.md
index d7f52bf607..73adcb7fe7 100644
--- a/content/riak/kv/2.1.3/using/reference/statistics-monitoring.md
+++ b/content/riak/kv/2.1.3/using/reference/statistics-monitoring.md
@@ -134,7 +134,7 @@ Metric | Also | Notes
:------|:-----|:------------------
```node_get_fsm_siblings_mean``` | ```_median```, ```_95```, ```_99```, ```_100``` | Number of siblings encountered during all GET operations by this node within the last minute. Watch for abnormally high sibling counts, especially max ones.
```node_get_fsm_objsize_mean``` | ```_median```, ```_95```, ```_99```, ```_100``` | Object size encountered by this node within the last minute. Abnormally large objects (especially paired with high sibling counts) can indicate sibling explosion.
-```riak_search_vnodeq_mean``` | ```_median```, ```_95```, ```_99```, ```_100``` | Number of unprocessed messages in the vnode message queues of the Riak Search subsystem on this node in the last minute. The queues give you an idea of how backed up Solr is getting.
+```riak_search_vnodeq_mean``` | ```_median```, ```_95```, ```_99```, ```_100``` | Number of unprocessed messages in the vnode message queues of the Riak search subsystem on this node in the last minute. The queues give you an idea of how backed up Solr is getting.
```search_index_fail_one``` | | Number of "Failed to index document" errors Search encountered for the last minute
```pbc_active``` | | Number of currently active protocol buffer connections
```pbc_connects``` | | Number of new protocol buffer connections established during the last minute
diff --git a/content/riak/kv/2.1.3/using/reference/strong-consistency.md b/content/riak/kv/2.1.3/using/reference/strong-consistency.md
index 069dc335a6..6ac1ec5f79 100644
--- a/content/riak/kv/2.1.3/using/reference/strong-consistency.md
+++ b/content/riak/kv/2.1.3/using/reference/strong-consistency.md
@@ -17,7 +17,7 @@ toc: true
Please Note:
-Riak KV's strong consistency is an experimental feature and may be removed from the product in the future. Strong consistency is not commercially supported or production-ready. Strong consistency is incompatible with Multi-Datacenter Replication, Riak Search, Bitcask Expiration, LevelDB Secondary Indexes, Riak Data Types and Commit Hooks. We do not recommend its usage in any production environment.
+Riak KV's strong consistency is an experimental feature and may be removed from the product in the future. Strong consistency is not commercially supported or production-ready. Strong consistency is incompatible with Multi-Datacenter Replication, Riak search, Bitcask Expiration, LevelDB Secondary Indexes, Riak Data Types and Commit Hooks. We do not recommend its usage in any production environment.
Riak was originally designed as an [eventually consistent](/riak/kv/2.1.3/learn/concepts/eventual-consistency) system, fundamentally geared toward providing partition
diff --git a/content/riak/kv/2.1.3/using/repair-recovery/errors.md b/content/riak/kv/2.1.3/using/repair-recovery/errors.md
index 865181ab2f..baa85978ad 100644
--- a/content/riak/kv/2.1.3/using/repair-recovery/errors.md
+++ b/content/riak/kv/2.1.3/using/repair-recovery/errors.md
@@ -328,7 +328,7 @@ exit with reason bad return value: {error,eaddrinuse} in context start_error | A
exited with reason: eaddrnotavail in gen_server:init_it/6 line 320 | An error like this example can result when Riak cannot bind to the addresses specified in the configuration. In this case, you should verify HTTP and Protocol Buffers addresses in `app.config` and ensure that the ports being used are not in the privileged (1-1024) range as the `riak` user will not have access to such ports.
gen_server riak_core_capability terminated with reason: no function clause matching orddict:fetch('riak@192.168.2.2', []) line 72 | Error output like this example can indicate that a previously running Riak node with an original `-name` value in `vm.args` has been modified by simply changing the value in `vm.args` and not properly through `riak-admin cluster replace`.
** Configuration error: [FRAMEWORK-MIB]: missing context.conf file => generating a default file | This error is commonly encountered when starting Riak Enterprise without prior [SNMP](/riak/kv/2.1.3/using/reference/snmp) configuration.
-RPC to 'node@example.com' failed: {'EXIT', {badarg, [{ets,lookup, [schema_table,<<"search-example">>], []} {riak_search_config,get_schema,1, [{file,"src/riak_search_config.erl"}, {line,69}]} ...| This error can be caused when attempting to use Riak Search without first enabling it in each node's `app.config`. See the [configuration files][config reference] documentation for more information on enabling Riak Search.
+RPC to 'node@example.com' failed: {'EXIT', {badarg, [{ets,lookup, [schema_table,<<"search-example">>], []} {riak_search_config,get_schema,1, [{file,"src/riak_search_config.erl"}, {line,69}]} ...| This error can be caused when attempting to use Riak search without first enabling it in each node's `app.config`. See the [configuration files][config reference] documentation for more information on enabling Riak search.
### More
diff --git a/content/riak/kv/2.1.3/using/repair-recovery/repairs.md b/content/riak/kv/2.1.3/using/repair-recovery/repairs.md
index 762031baa7..aea63265a6 100644
--- a/content/riak/kv/2.1.3/using/repair-recovery/repairs.md
+++ b/content/riak/kv/2.1.3/using/repair-recovery/repairs.md
@@ -57,7 +57,7 @@ riak-admin repair-2i kill
## Repairing Search Indexes
-Riak Search indexes currently have no form of anti-entropy (such as read-repair). Furthermore, for performance and load balancing reasons, Search reads from one random node. This means that when a replica loss has occurred, inconsistent results may be returned.
+Riak search indexes currently have no form of anti-entropy (such as read-repair). Furthermore, for performance and load balancing reasons, Search reads from one random node. This means that when a replica loss has occurred, inconsistent results may be returned.
### Running a Repair
diff --git a/content/riak/kv/2.1.3/using/repair-recovery/secondary-indexes.md b/content/riak/kv/2.1.3/using/repair-recovery/secondary-indexes.md
index 6f650199ae..16830b70d0 100644
--- a/content/riak/kv/2.1.3/using/repair-recovery/secondary-indexes.md
+++ b/content/riak/kv/2.1.3/using/repair-recovery/secondary-indexes.md
@@ -51,7 +51,7 @@ riak-admin repair-2i kill
## Repairing Search Indexes
-Riak Search indexes currently have no form of anti-entropy (such as read-repair). Furthermore, for performance and load balancing reasons, Search reads from one random node. This means that when a replica loss has occurred, inconsistent results may be returned.
+Riak search indexes currently have no form of anti-entropy (such as read-repair). Furthermore, for performance and load balancing reasons, Search reads from one random node. This means that when a replica loss has occurred, inconsistent results may be returned.
### Running a Repair
diff --git a/content/riak/kv/2.1.3/using/security/basics.md b/content/riak/kv/2.1.3/using/security/basics.md
index 3b596811bd..42abf489f5 100644
--- a/content/riak/kv/2.1.3/using/security/basics.md
+++ b/content/riak/kv/2.1.3/using/security/basics.md
@@ -44,7 +44,7 @@ when turning on Riak security. Missing one of these steps will almost
certainly break your application, so make sure that you have done each
of the following **before** enabling security:
-1. Make certain that the original Riak Search (version 1) and link
+1. Make certain that the original Riak search (version 1) and link
walking are not required. Enabling security will break this
functionality. If you wish to use security and Search together, you
will need to use the [new Search feature](/riak/kv/2.1.3/developing/usage/search/).
@@ -487,11 +487,11 @@ Permission | Operation
### Search Query Permission (Riak Search version 1)
Security is incompatible with the original (and now deprecated) Riak
-Search. Riak Search version 1 will stop working if security is enabled.
+search. Riak search version 1 will stop working if security is enabled.
### Search Query Permissions (Riak Search version 2, aka Yokozuna)
-If you are using the new Riak Search, i.e. the Solr-compatible search
+If you are using the new Riak search, i.e. the Solr-compatible search
capabilities included with Riak versions 2.0 and greater, the following
search-related permissions can be granted/revoked:
@@ -508,8 +508,8 @@ disabled, you will get the following error:
>
> `{error,{unknown_permission,"search.query"}}`
>
-> More information on Riak Search and how to enable it can be found in the
-[Riak Search Settings](/riak/kv/2.1.3/configuring/search/) document.
+> More information on Riak search and how to enable it can be found in the
+[Riak search Settings](/riak/kv/2.1.3/configuring/search/) document.
#### Usage Examples
diff --git a/content/riak/kv/2.1.4/configuring/reference.md b/content/riak/kv/2.1.4/configuring/reference.md
index e1a7e52836..172216d141 100644
--- a/content/riak/kv/2.1.4/configuring/reference.md
+++ b/content/riak/kv/2.1.4/configuring/reference.md
@@ -273,7 +273,7 @@ stored
search.root_dir |
-The root directory for Riak Search, under which index data and
+ | The root directory for Riak search, under which index data and
configuration is stored. |
./data/yz |
@@ -1386,7 +1386,7 @@ Configurable parameters for intra-cluster, i.e. inter-node, [handoff][cluster op
handoff.max_rejects |
The maximum number of times that a secondary system within Riak,
-such as Riak Search, can block handoff
+such as Riak search, can block handoff
of primary key/value data. The approximate maximum duration that a vnode
can be blocked can be determined by multiplying this setting by
vnode_management_timer. If you want to prevent handoff from
@@ -1630,7 +1630,7 @@ if the JMX server crashes. |
> **Please Note:**
>
-> Riak KV's strong consistency is an experimental feature and may be removed from the product in the future. Strong consistency is not commercially supported or production-ready. Strong consistency is incompatible with Multi-Datacenter Replication, Riak Search, Bitcask Expiration, LevelDB Secondary Indexes, Riak Data Types and Commit Hooks. We do not recommend its usage in any production environment.
+> Riak KV's strong consistency is an experimental feature and may be removed from the product in the future. Strong consistency is not commercially supported or production-ready. Strong consistency is incompatible with Multi-Datacenter Replication, Riak search, Bitcask Expiration, LevelDB Secondary Indexes, Riak Data Types and Commit Hooks. We do not recommend its usage in any production environment.
Riak's strong consistency feature has a variety of tunable parameters
that allow you to enable and disable strong consistency, modify the
@@ -2053,7 +2053,7 @@ only in Riak Enterprise 2.0 and later.
#### Upgrading Riak Search with `advanced.config`
-If you are upgrading to Riak 2.x and wish to upgrade to the new [Riak Search][use ref search]\(codename Yokozuna), you will need to enable
+If you are upgrading to Riak 2.x and wish to upgrade to the new [Riak search][use ref search]\(codename Yokozuna), you will need to enable
legacy Search while the upgrade is underway. You can add the following
snippet to your `advanced.config` configuration to do so:
diff --git a/content/riak/kv/2.1.4/configuring/search.md b/content/riak/kv/2.1.4/configuring/search.md
index 56e9501113..733e0dfdd6 100644
--- a/content/riak/kv/2.1.4/configuring/search.md
+++ b/content/riak/kv/2.1.4/configuring/search.md
@@ -26,9 +26,9 @@ aliases:
> **Note on Search 2.0 vs. Legacy Search**
>
-> This document refers to the new Riak Search 2.0 with
+> This document refers to the new Riak search 2.0 with
[Solr](http://lucene.apache.org/solr/) integration (codenamed
-Yokozuna). For information about the deprecated Riak Search, visit [the old Riak Search Settings](http://docs.basho.com/riak/1.4.8/ops/advanced/configs/search/).
+Yokozuna). For information about the deprecated Riak search, visit [the old Riak search Settings](http://docs.basho.com/riak/1.4.8/ops/advanced/configs/search/).
This document covers Riak's Search subsystem from an
operational perspective. If you are looking for more developer-focused
@@ -41,7 +41,7 @@ docs, we recommend the following:
## Enabling Riak Search
-Although Riak Search is integrated into Riak and requires no special
+Although Riak search is integrated into Riak and requires no special
installation, it is not enabled by default. You must enable it in every
node's [configuration files][config reference] as follows:
@@ -68,7 +68,7 @@ optional. A list of these parameters can also be found in our
Field | Default | Valid values | Description
:-----|:--------|:-------------|:-----------
`search` | `off` | `on` or `off` | Enable or disable Search
-`search.anti_entropy.data_dir` | `./data/yz_anti_entropy` | Directory | The directory in which Riak Search stores files related to [active anti-entropy][glossary aae]
+`search.anti_entropy.data_dir` | `./data/yz_anti_entropy` | Directory | The directory in which Riak search stores files related to [active anti-entropy][glossary aae]
`search.root_dir` | `./data/yz` | Directory | The root directory in which index data and configuration is stored
`search.solr.start_timeout` | `30s` | Integer with time units (eg. 2m) | How long Riak will wait for Solr to start (attempts twice before shutdown). Values lower than 1s will be rounded up to 1s.
`search.solr.port` | `8093` | Integer | The port number to which Solr binds (note: binds on every interface)
@@ -81,7 +81,7 @@ cause Solr to require more time to start.
## Solr JVM and Ports
-Riak Search runs one Solr process per node to manage its indexing and
+Riak search runs one Solr process per node to manage its indexing and
search functionality. While the underlying project, Yokozuna, manages
index distribution, node coverage for queries, active anti-entropy
(AAE), and JVM process management, you should provide plenty of RAM and diskspace for running both Riak and the JVM running Solr. We recommend a minimum of 6GB of RAM per node.
diff --git a/content/riak/kv/2.1.4/configuring/strong-consistency.md b/content/riak/kv/2.1.4/configuring/strong-consistency.md
index aee7d66d70..eb5f507e08 100644
--- a/content/riak/kv/2.1.4/configuring/strong-consistency.md
+++ b/content/riak/kv/2.1.4/configuring/strong-consistency.md
@@ -41,7 +41,7 @@ aliases:
> **Please Note:**
>
-> Riak KV's strong consistency is an experimental feature and may be removed from the product in the future. Strong consistency is not commercially supported or production-ready. Strong consistency is incompatible with Multi-Datacenter Replication, Riak Search, Bitcask Expiration, LevelDB Secondary Indexes, Riak Data Types and Commit Hooks. We do not recommend its usage in any production environment.
+> Riak KV's strong consistency is an experimental feature and may be removed from the product in the future. Strong consistency is not commercially supported or production-ready. Strong consistency is incompatible with Multi-Datacenter Replication, Riak search, Bitcask Expiration, LevelDB Secondary Indexes, Riak Data Types and Commit Hooks. We do not recommend its usage in any production environment.
This document provides information on configuring and monitoring a Riak
cluster's optional strong consistency subsystem. Documentation for
diff --git a/content/riak/kv/2.1.4/developing/api/http/delete-search-index.md b/content/riak/kv/2.1.4/developing/api/http/delete-search-index.md
index 3816e01b01..fe902fa7ef 100644
--- a/content/riak/kv/2.1.4/developing/api/http/delete-search-index.md
+++ b/content/riak/kv/2.1.4/developing/api/http/delete-search-index.md
@@ -15,7 +15,7 @@ aliases:
- /riak/kv/2.1.4/dev/references/http/delete-search-index
---
-Deletes a Riak Search index.
+Deletes a Riak search index.
## Request
diff --git a/content/riak/kv/2.1.4/developing/api/http/fetch-search-index.md b/content/riak/kv/2.1.4/developing/api/http/fetch-search-index.md
index 3535292070..02ede5da7a 100644
--- a/content/riak/kv/2.1.4/developing/api/http/fetch-search-index.md
+++ b/content/riak/kv/2.1.4/developing/api/http/fetch-search-index.md
@@ -15,7 +15,7 @@ aliases:
- /riak/kv/2.1.4/dev/references/http/fetch-search-index
---
-Retrieves information about a Riak Search [index](/riak/kv/2.1.4/developing/usage/search/#simple-setup).
+Retrieves information about a Riak search [index](/riak/kv/2.1.4/developing/usage/search/#simple-setup).
## Request
diff --git a/content/riak/kv/2.1.4/developing/api/http/fetch-search-schema.md b/content/riak/kv/2.1.4/developing/api/http/fetch-search-schema.md
index e73c81d86c..c499149818 100644
--- a/content/riak/kv/2.1.4/developing/api/http/fetch-search-schema.md
+++ b/content/riak/kv/2.1.4/developing/api/http/fetch-search-schema.md
@@ -35,4 +35,4 @@ GET /search/schema/
## Response
If the schema is found, Riak will return the contents of the schema as
-XML (all Riak Search schemas are XML).
+XML (all Riak search schemas are XML).
diff --git a/content/riak/kv/2.1.4/developing/api/http/search-index-info.md b/content/riak/kv/2.1.4/developing/api/http/search-index-info.md
index 68899d541a..71580f4361 100644
--- a/content/riak/kv/2.1.4/developing/api/http/search-index-info.md
+++ b/content/riak/kv/2.1.4/developing/api/http/search-index-info.md
@@ -47,6 +47,6 @@ Below is the example output if there is one Search index, called
#### Typical Error Codes
-* `404 Object Not Found` --- Typically returned if Riak Search is not
+* `404 Object Not Found` --- Typically returned if Riak search is not
currently enabled on the node
* `503 Service Unavailable` --- The request timed out internally
diff --git a/content/riak/kv/2.1.4/developing/api/http/store-search-index.md b/content/riak/kv/2.1.4/developing/api/http/store-search-index.md
index 9ee1933341..82dbcb724f 100644
--- a/content/riak/kv/2.1.4/developing/api/http/store-search-index.md
+++ b/content/riak/kv/2.1.4/developing/api/http/store-search-index.md
@@ -15,7 +15,7 @@ aliases:
- /riak/kv/2.1.4/dev/references/http/store-search-index
---
-Creates a new Riak Search [index](/riak/kv/2.1.4/developing/usage/search/#simple-setup).
+Creates a new Riak search [index](/riak/kv/2.1.4/developing/usage/search/#simple-setup).
## Request
diff --git a/content/riak/kv/2.1.4/developing/api/http/store-search-schema.md b/content/riak/kv/2.1.4/developing/api/http/store-search-schema.md
index 3adbae063b..88caba661f 100644
--- a/content/riak/kv/2.1.4/developing/api/http/store-search-schema.md
+++ b/content/riak/kv/2.1.4/developing/api/http/store-search-schema.md
@@ -44,7 +44,7 @@ curl -XPUT http://localhost:8098/search/schema/my_custom_schema \
* `400 Bad Request` --- The schema cannot be created because there is
something wrong with the schema itself, e.g. an XML formatting error
- that makes Riak Search unable to parse the schema
+ that makes Riak search unable to parse the schema
* `409 Conflict` --- The schema cannot be created because there is
already a schema with that name
* `503 Service Unavailable` --- The request timed out internally
diff --git a/content/riak/kv/2.1.4/developing/api/protocol-buffers/yz-index-get.md b/content/riak/kv/2.1.4/developing/api/protocol-buffers/yz-index-get.md
index 3b8b3a92c1..41cfdf70ee 100644
--- a/content/riak/kv/2.1.4/developing/api/protocol-buffers/yz-index-get.md
+++ b/content/riak/kv/2.1.4/developing/api/protocol-buffers/yz-index-get.md
@@ -15,7 +15,7 @@ aliases:
- /riak/kv/2.1.4/dev/references/protocol-buffers/yz-index-get
---
-Retrieve a search index from Riak Search.
+Retrieve a search index from Riak search.
## Request
diff --git a/content/riak/kv/2.1.4/developing/api/protocol-buffers/yz-schema-get.md b/content/riak/kv/2.1.4/developing/api/protocol-buffers/yz-schema-get.md
index 3dd8bf545d..70940ea5c6 100644
--- a/content/riak/kv/2.1.4/developing/api/protocol-buffers/yz-schema-get.md
+++ b/content/riak/kv/2.1.4/developing/api/protocol-buffers/yz-schema-get.md
@@ -15,7 +15,7 @@ aliases:
- /riak/kv/2.1.4/dev/references/protocol-buffers/yz-schema-get
---
-Fetch a [search schema](/riak/kv/2.1.4/developing/usage/search-schemas) from Riak Search.
+Fetch a [search schema](/riak/kv/2.1.4/developing/usage/search-schemas) from Riak search.
## Request
diff --git a/content/riak/kv/2.1.4/developing/app-guide.md b/content/riak/kv/2.1.4/developing/app-guide.md
index 20b684cc34..766ab42b57 100644
--- a/content/riak/kv/2.1.4/developing/app-guide.md
+++ b/content/riak/kv/2.1.4/developing/app-guide.md
@@ -149,22 +149,22 @@ well as relevant links to Basho documentation.
## Search
-Riak Search provides you with [Apache
+Riak search provides you with [Apache
Solr](http://lucene.apache.org/solr/)-powered full-text indexing and
querying on top of the scalability, fault tolerance, and operational
-simplicity of Riak. Our motto for Riak Search: **Write it like Riak.
+simplicity of Riak. Our motto for Riak search: **Write it like Riak.
Query it like Solr**. That is, you can store objects in Riak [like normal][usage create objects] and run full-text queries on those objects later on
using the Solr API.
-* [Using Search][usage search] --- Getting started with Riak Search
+* [Using Search][usage search] --- Getting started with Riak search
* [Search Details][use ref search] --- A detailed overview of the concepts and design
- consideration behind Riak Search
+ consideration behind Riak search
* [Search Schema][usage search schema] --- How to create custom schemas for extracting data
- from Riak Search
+ from Riak search
### When to Use Search
-* **When you need a rich querying API** --- Riak Search gives you access
+* **When you need a rich querying API** --- Riak search gives you access
to the entirety of [Solr](http://lucene.apache.org/solr/)'s extremely
broad API, which enables you to query on the basis of wildcards,
strings, booleans, geolocation, ranges, language-specific fulltext,
@@ -216,7 +216,7 @@ own.
> **Note**:
>
-> Riak Data Types can be used in conjunction with Riak Search,
+> Riak Data Types can be used in conjunction with Riak search,
meaning that the data stored in counters, sets, and maps can be indexed
and searched just like any other data in Riak. Documentation on Data
Types and Search is coming soon.
@@ -284,13 +284,13 @@ or you can write and run your own MapReduce jobs in
### When Not to Use MapReduce
* **When another Riak feature will do** --- Before even considering
- using MapReduce, you should thoroughly investigate [Riak Search][usage search] or [secondary indexes][usage 2i] as possible
+ using MapReduce, you should thoroughly investigate [Riak search][usage search] or [secondary indexes][usage 2i] as possible
solutions to your needs.
In general, you should not think of MapReduce as, for example, Hadoop
within Riak. While it can be useful for certain types of
non-primary-key-based queries, it is neither a "Big Data" processing
-tool nor an indexing mechanism nor a replacement for [Riak Search][usage search]. If you do need a tool like Hadoop or Apache Spark, you should
+tool nor an indexing mechanism nor a replacement for [Riak search][usage search]. If you do need a tool like Hadoop or Apache Spark, you should
consider using Riak in conjunction with a more suitable data processing
tool.
@@ -301,7 +301,7 @@ following problem: how do I know which keys I should look for? Secondary
indexes (2i) provide a solution to this problem, enabling you to tag
objects with either binary or integer metadata and then query Riak for
all of the keys that share specific tags. 2i is especially useful if
-you're storing binary data that is opaque to features like [Riak Search][usage search].
+you're storing binary data that is opaque to features like [Riak search][usage search].
* [Using Secondary Indexes][usage 2i] --- A general guide to using 2i, along
with code samples and information on 2i features like pagination,
@@ -329,7 +329,7 @@ you're storing binary data that is opaque to features like [Riak Search][usage s
One thing to always bear in mind is that Riak enables you to mix and
match a wide variety of approaches in a single cluster. You can use
basic CRUD operations for some of your data, index some of your data to
-be queried by Riak Search, use Riak Data Types for another subset, etc.
+be queried by Riak search, use Riak Data Types for another subset, etc.
You are always free to use a wide array of Riak features---or you can
use none at all and stick to key/value operations.
diff --git a/content/riak/kv/2.1.4/developing/app-guide/advanced-mapreduce.md b/content/riak/kv/2.1.4/developing/app-guide/advanced-mapreduce.md
index bbd4fe9694..26a573a421 100644
--- a/content/riak/kv/2.1.4/developing/app-guide/advanced-mapreduce.md
+++ b/content/riak/kv/2.1.4/developing/app-guide/advanced-mapreduce.md
@@ -74,7 +74,7 @@ MapReduce should generally be treated as a fallback rather than a
standard part of an application. There are often ways to model data
such that dynamic queries become single key retrievals, which are
dramatically faster and more reliable in Riak, and tools such as Riak
-Search and 2i are simpler to use and may place less strain on a
+search and 2i are simpler to use and may place less strain on a
cluster.
### R=1
diff --git a/content/riak/kv/2.1.4/developing/app-guide/strong-consistency.md b/content/riak/kv/2.1.4/developing/app-guide/strong-consistency.md
index c75871a46d..d0b1392d5e 100644
--- a/content/riak/kv/2.1.4/developing/app-guide/strong-consistency.md
+++ b/content/riak/kv/2.1.4/developing/app-guide/strong-consistency.md
@@ -37,7 +37,7 @@ aliases:
> **Please Note:**
>
-> Riak KV's strong consistency is an experimental feature and may be removed from the product in the future. Strong consistency is not commercially supported or production-ready. Strong consistency is incompatible with Multi-Datacenter Replication, Riak Search, Bitcask Expiration, LevelDB Secondary Indexes, Riak Data Types and Commit Hooks. We do not recommend its usage in any production environment.
+> Riak KV's strong consistency is an experimental feature and may be removed from the product in the future. Strong consistency is not commercially supported or production-ready. Strong consistency is incompatible with Multi-Datacenter Replication, Riak search, Bitcask Expiration, LevelDB Secondary Indexes, Riak Data Types and Commit Hooks. We do not recommend its usage in any production environment.
In versions 2.0 and later, Riak allows you to create buckets that
provide [strong consistency][use ref strong consistency] guarantees for the data stored within
diff --git a/content/riak/kv/2.1.4/developing/data-modeling.md b/content/riak/kv/2.1.4/developing/data-modeling.md
index 75de20b928..67278de26c 100644
--- a/content/riak/kv/2.1.4/developing/data-modeling.md
+++ b/content/riak/kv/2.1.4/developing/data-modeling.md
@@ -141,7 +141,7 @@ For storing log data from different systems, you could use unique
buckets for each system (e.g. `system1_log_data`, `system2_log_data`,
etc.) and write associated logs to the corresponding buckets. To
analyze that data, you could use Riak's MapReduce system for aggregation
-tasks, such as summing the counts of records for a date or Riak Search
+tasks, such as summing the counts of records for a date or Riak search
for a more robust, text-based queries.
### Log Data Complex Case
@@ -225,7 +225,7 @@ For simple retrieval of a specific account, a user ID (plus perhaps a
secondary index on a username or email) is enough. If you foresee the
need to make queries on additional user attributes (e.g. creation time,
user type, or region), plan ahead and either set up additional secondary
-indexes or consider using [Riak Search](/riak/kv/2.1.4/developing/usage/search/) to index the JSON
+indexes or consider using [Riak search](/riak/kv/2.1.4/developing/usage/search/) to index the JSON
contents of the user account.
### User Accounts Community Examples
@@ -311,7 +311,7 @@ In Riak, you can store content of any kind, from HTML files to plain
text to JSON or XML or another document type entirely. Keep in mind that
data in Riak is opaque, with the exception of [Riak Data Types](/riak/kv/2.1.4/developing/data-types),
and so Riak won't "know" about the object unless it is indexed
-[using Riak Search](/riak/kv/2.1.4/developing/usage/search/) or [using secondary indexes](/riak/kv/2.1.4/developing/usage/secondary-indexes/).
+[using Riak search](/riak/kv/2.1.4/developing/usage/search/) or [using secondary indexes](/riak/kv/2.1.4/developing/usage/secondary-indexes/).
### Articles et al Complex Case
@@ -330,7 +330,7 @@ with comments would require your application to call from the posts
and comments buckets to assemble the view.
Other possible cases may involve performing operations on content beyond
-key/value pairs. [Riak Search](/riak/kv/2.1.4/developing/usage/search/) is recommended for use cases
+key/value pairs. [Riak search](/riak/kv/2.1.4/developing/usage/search/) is recommended for use cases
involving full-text search. For lighter-weight querying,
[using secondary indexes](/riak/kv/2.1.4/developing/usage/secondary-indexes/) \(2i) enables you to add metadata to objects to
either query for exact matches or to perform range queries. 2i also
diff --git a/content/riak/kv/2.1.4/developing/data-types.md b/content/riak/kv/2.1.4/developing/data-types.md
index f700a7ef9f..0e932af963 100644
--- a/content/riak/kv/2.1.4/developing/data-types.md
+++ b/content/riak/kv/2.1.4/developing/data-types.md
@@ -259,7 +259,7 @@ All the examples use the bucket type names from above (`counters`, `sets`, and `
Riak data types can be searched like any other object, but with the
added benefit that your data type is indexed as a different type by Solr,
-the search platform behind Riak Search.
+the search platform behind Riak search.
In our Search documentation we offer a [full tutorial](../usage/searching-data-types) as well as a variety of [examples](../usage/search/#data-types-and-search-examples), including code
samples from each of our official client libraries.
diff --git a/content/riak/kv/2.1.4/developing/usage.md b/content/riak/kv/2.1.4/developing/usage.md
index 2a0a210814..4876bacfca 100644
--- a/content/riak/kv/2.1.4/developing/usage.md
+++ b/content/riak/kv/2.1.4/developing/usage.md
@@ -111,7 +111,7 @@ Tutorial on using Riak KV as a document store.
#### [Custom Extractors](./custom-extractors)
-Details on creating and registering custom extractors with Riak Search.
+Details on creating and registering custom extractors with Riak search.
[Learn More >>](./custom-extractors)
diff --git a/content/riak/kv/2.1.4/developing/usage/custom-extractors.md b/content/riak/kv/2.1.4/developing/usage/custom-extractors.md
index b94127dbb5..39e1b01f12 100644
--- a/content/riak/kv/2.1.4/developing/usage/custom-extractors.md
+++ b/content/riak/kv/2.1.4/developing/usage/custom-extractors.md
@@ -15,8 +15,8 @@ aliases:
- /riak/kv/2.1.4/dev/search/custom-extractors
---
-Solr, and by extension Riak Search, has default extractors for a wide
-variety of data types, including JSON, XML, and plaintext. Riak Search
+Solr, and by extension Riak search, has default extractors for a wide
+variety of data types, including JSON, XML, and plaintext. Riak search
ships with the following extractors:
Content Type | Erlang Module
@@ -30,7 +30,7 @@ No specified type | `yz_noop_extractor`
There are also built-in extractors for [Riak Data Types](/riak/kv/2.1.4/developing/usage/searching-data-types).
If you're working with a data format that does not have a default Solr
-extractor, you can create your own and register it with Riak Search.
+extractor, you can create your own and register it with Riak search.
We'll show you how to do so by way of example.
## The Extractor Interface
@@ -195,7 +195,7 @@ extractor has been successfully registered.
## Verifying Our Custom Extractor
-Now that Riak Search knows how to decode and extract HTTP header packet
+Now that Riak search knows how to decode and extract HTTP header packet
data, let's store some in Riak and then query it. We'll put the example
packet data from above in a `google_packet.bin` file. Then, we'll `PUT`
that binary to Riak's `/search/extract` endpoint:
diff --git a/content/riak/kv/2.1.4/developing/usage/document-store.md b/content/riak/kv/2.1.4/developing/usage/document-store.md
index 8f97c8b798..663f0cafeb 100644
--- a/content/riak/kv/2.1.4/developing/usage/document-store.md
+++ b/content/riak/kv/2.1.4/developing/usage/document-store.md
@@ -16,18 +16,18 @@ aliases:
---
Although Riak wasn't explicitly created as a document store, two
-features recently added to Riak---[Riak Search](/riak/kv/2.1.4/developing/usage/search/) and [Riak Data Types](/riak/kv/2.1.4/developing/data-types/)---make it possible to use Riak as a
+features recently added to Riak---[Riak search](/riak/kv/2.1.4/developing/usage/search/) and [Riak Data Types](/riak/kv/2.1.4/developing/data-types/)---make it possible to use Riak as a
highly scalable document store with rich querying capabilities. In this
tutorial, we'll build a basic implementation of a document store using
[Riak maps](/riak/kv/2.1.4/developing/data-types/maps).
## Basic Approach
-Riak Search enables you to implement a document store in Riak in a
+Riak search enables you to implement a document store in Riak in a
variety of ways. You could, for example, store and query JSON objects or
XML and then retrieve them later via Solr queries. In this tutorial,
however, we will store data in [Riak maps](/riak/kv/2.1.4/developing/data-types/maps),
-index that data using Riak Search, and then run Solr queries against
+index that data using Riak search, and then run Solr queries against
those stored objects.
You can think of these Search indexes as **collections**. Each indexed
@@ -65,7 +65,7 @@ Date posted | Register | Datetime
Whether the post is currently in draft form | Flag | Boolean
Before we start actually creating and storing blog posts, let's set up
-Riak Search with an appropriate index and schema.
+Riak search with an appropriate index and schema.
## Creating a Schema and Index
@@ -209,7 +209,7 @@ curl -XPUT $RIAK_HOST/search/index/blog_posts \
Collections are not a concept that is native to Riak but we can easily
mimic collections by thinking of a bucket type as a collection. When we
-associate a bucket type with a Riak Search index, all of the objects
+associate a bucket type with a Riak search index, all of the objects
stored in any bucket of that bucket type will be queryable on the basis
of that one index. For this tutorial, we'll create a bucket type called
`cms` and think of that as a collection. We could also restrict our
diff --git a/content/riak/kv/2.1.4/developing/usage/search-schemas.md b/content/riak/kv/2.1.4/developing/usage/search-schemas.md
index f8f949b9a3..7391660523 100644
--- a/content/riak/kv/2.1.4/developing/usage/search-schemas.md
+++ b/content/riak/kv/2.1.4/developing/usage/search-schemas.md
@@ -19,21 +19,21 @@ aliases:
> **Note on Search 2.0 vs. Legacy Search**
>
-> This document refers to the new Riak Search 2.0 with
+> This document refers to the new Riak search 2.0 with
[Solr](http://lucene.apache.org/solr/) integration (codenamed
-Yokozuna). For information about the deprecated Riak Search, visit [the old Using Riak Search docs](http://docs.basho.com/riak/1.4.10/dev/using/search/).
+Yokozuna). For information about the deprecated Riak search, visit [the old Using Riak search docs](http://docs.basho.com/riak/1.4.10/dev/using/search/).
-Riak Search is built for ease of use, allowing you to write values into
-Riak and query for values using Solr. Riak Search does a lot of work
+Riak search is built for ease of use, allowing you to write values into
+Riak and query for values using Solr. Riak search does a lot of work
under the hood to convert your values---plain text, JSON, XML, [Riak Data Types](/riak/kv/2.1.4/developing/data-types/), and [more](/riak/kv/2.1.4/developing/usage/custom-extractors)---into something that can be indexed and searched later.
Nonetheless, you must still instruct Riak/Solr how to index a value. Are
you providing and array of strings? An integer? A date? Is your text in
-English or Russian? You can provide such instructions to Riak Search by
+English or Russian? You can provide such instructions to Riak search by
defining a Solr **schema**.
## The Default Schema
-Riak Search comes bundled with a default schema named `_yz_default`. The
+Riak search comes bundled with a default schema named `_yz_default`. The
default schema covers a wide range of possible field types. You can find
the default schema [on
GitHub](https://raw.github.com/basho/yokozuna/develop/priv/default_schema.xml).
@@ -48,7 +48,7 @@ amounts of disk space, so pay special attention to those indexes.
We'll show you how you can create custom schemas by way of example.
Let's say that you have already created a schema named `cartoons` in a
file named `cartoons.xml`. This would register the custom schema in Riak
-Search:
+search:
```java
import org.apache.commons.io.FileUtils;
@@ -124,11 +124,11 @@ curl -XPUT http://localhost:8098/search/schema/cartoons \
The first step in creating a custom schema is to define exactly what
fields you must index. Part of that step is understanding how Riak
-Search extractors function.
+search extractors function.
### Extractors
-In Riak Search, extractors are modules responsible for pulling out a
+In Riak search, extractors are modules responsible for pulling out a
list of fields and values from a Riak object. How this is achieved
depends on the object's content type, but the two common cases are JSON
and XML, which operate similarly. Our examples here will use JSON.
@@ -176,21 +176,21 @@ Solr schemas can be very complex, containing many types and analyzers.
Refer to the [Solr 4.7 reference
guide](http://archive.apache.org/dist/lucene/solr/ref-guide/apache-solr-ref-guide-4.7.pdf)
for a complete list. You should be aware, however, that there are a few
-fields that are required by Riak Search in order to properly distribute
+fields that are required by Riak search in order to properly distribute
an object across a [cluster][concept clusters]. These fields are all prefixed
with `_yz`, which stands for
[Yokozuna](https://github.com/basho/yokozuna), the original code name
-for Riak Search.
+for Riak search.
Below is a bare minimum skeleton Solr Schema. It won't do much for you
-other than allow Riak Search to properly manage your stored objects.
+other than allow Riak search to properly manage your stored objects.
```xml
-
+
@@ -211,14 +211,14 @@ other than allow Riak Search to properly manage your stored objects.
```
-If you're missing any of the above fields, Riak Search will reject your
+If you're missing any of the above fields, Riak search will reject your
custom schema. The value for `` _must_ be `_yz_id`.
In the table below, you'll find a description of the various required
fields. You'll rarely need to use any fields other than `_yz_rt` (bucket
type), `_yz_rb` (bucket) and `_yz_rk` (Riak key). On occasion, `_yz_err`
can be helpful if you suspect that your extractors are failing.
-Malformed JSON or XML will cause Riak Search to index a key and set
+Malformed JSON or XML will cause Riak search to index a key and set
`_yz_err` to 1, allowing you to reindex with proper values later.
Field | Name | Description
@@ -263,7 +263,7 @@ field, you also must set `multiValued` to `true`.
-
+
diff --git a/content/riak/kv/2.1.4/developing/usage/search.md b/content/riak/kv/2.1.4/developing/usage/search.md
index 1453b3a16d..05835fc76d 100644
--- a/content/riak/kv/2.1.4/developing/usage/search.md
+++ b/content/riak/kv/2.1.4/developing/usage/search.md
@@ -19,9 +19,9 @@ aliases:
## Setup
-Riak Search 2.0 is an integration of Solr (for indexing and querying)
+Riak search 2.0 is an integration of Solr (for indexing and querying)
and Riak (for storage and distribution). There are a few points of
-interest that a user of Riak Search will have to keep in mind in order
+interest that a user of Riak search will have to keep in mind in order
to properly store and later query for values.
1. **Schemas** explain to Solr how to index fields
@@ -29,7 +29,7 @@ to properly store and later query for values.
3. **Bucket-index association** signals to Riak *when* to index values
(this also includes bucket type-index association)
-Riak Search must first be configured with a Solr schema so that Solr
+Riak search must first be configured with a Solr schema so that Solr
knows how to index value fields. If you don't define one, you're
provided with a default schema named `_yz_default`, which can be found
[on
@@ -38,7 +38,7 @@ GitHub](https://raw.githubusercontent.com/basho/yokozuna/develop/priv/default_sc
The examples in this document will presume the default. You can read
more about creating custom schemas in [Search Schema][usage search schema], which you'll likely want to use in a production environment.
-Next, you must create a named Solr index through Riak Search. This index
+Next, you must create a named Solr index through Riak search. This index
represents a collection of similar data that you connect with to perform
queries. When creating an index, you can optionally provide a schema. If
you do not, the default schema will be used. Here we'll `curl` create an
@@ -246,7 +246,7 @@ More information can be found in the [Solr
documentation](http://wiki.apache.org/solr/SolrPerformanceFactors).
With a Solr schema, index, and association in place (and possibly a
-security setup as well), we're ready to start using Riak Search. First,
+security setup as well), we're ready to start using Riak search. First,
populate the `cat` bucket with values, in this case information about
four cats: Liono, Cheetara, Snarf, and Panthro.
@@ -495,12 +495,12 @@ curl -XPUT $RIAK_HOST/types/animals/buckets/cats/keys/panthro \
```
If you've used Riak before, you may have noticed that this is no
-different from storing values without Riak Search. That's because we
-designed Riak Search with the following design goal in mind:
+different from storing values without Riak search. That's because we
+designed Riak search with the following design goal in mind:
#### Write it like Riak, query it like Solr
-But how does Riak Search know how to index values, given that you can
+But how does Riak search know how to index values, given that you can
store opaque values in Riak? For that, we employ extractors.
## Extractors
@@ -510,7 +510,7 @@ content type and convert it into a list of fields that can be indexed by
Solr. This is done transparently and automatically as part of the
indexing process. You can even create your own [custom extractors](/riak/kv/2.1.4/developing/usage/custom-extractors).
-Our current example uses the JSON extractor, but Riak Search also
+Our current example uses the JSON extractor, but Riak search also
extracts indexable fields from the following content types:
* JSON (`application/json`)
@@ -560,7 +560,7 @@ one of the default types. A full tutorial can be found in [Custom Search Extract
### Automatic Fields
-When a Riak object is indexed, Riak Search automatically inserts a few
+When a Riak object is indexed, Riak search automatically inserts a few
extra fields as well. These are necessary for a variety of technical
reasons, and for the most part you don't need to think about them.
However, there are a few fields which you may find useful:
@@ -1248,7 +1248,7 @@ curl "$RIAK_HOST/search/query/famous?wt=json&q=*:*&start=$START&rows=$ROWS_PER_P
### Pagination Warning
-Distributed pagination in Riak Search cannot be used reliably when
+Distributed pagination in Riak search cannot be used reliably when
sorting on fields that can have different values per replica of the same
object, namely `score` and `_yz_id`. In the case of sorting by these
fields, you may receive redundant objects. In the case of `score`, the
@@ -1272,14 +1272,14 @@ fix this shortcoming in a future version of Riak.
### MapReduce
-Riak Search allows for piping search results as inputs for
+Riak search allows for piping search results as inputs for
[MapReduce](/riak/kv/2.1.4/developing/usage/mapreduce/) jobs. This is a useful cross-section for
performing post-calculations of results or aggregations of ad-hoc
-queries. The Riak Search MapReduce integration works similarly to
+queries. The Riak search MapReduce integration works similarly to
regular MapReduce, with the notable exception that your input is not a
bucket, but rather index and query arguments to the `yokozuna` module
and `mapred_search` function (an Erlang `module:function` pair that adds
-the Riak Search hook to MapReduce).
+the Riak search hook to MapReduce).
```json
{
diff --git a/content/riak/kv/2.1.4/developing/usage/secondary-indexes.md b/content/riak/kv/2.1.4/developing/usage/secondary-indexes.md
index 474bcdef7c..fbf6c607b5 100644
--- a/content/riak/kv/2.1.4/developing/usage/secondary-indexes.md
+++ b/content/riak/kv/2.1.4/developing/usage/secondary-indexes.md
@@ -19,12 +19,12 @@ aliases:
[plan backend memory]: /riak/kv/2.1.4/setup/planning/backend/memory
[use ref strong consistency]: /riak/kv/2.1.4/using/reference/strong-consistency
-> **Note: Riak Search preferred for querying**
+> **Note: Riak search preferred for querying**
>
> If you're interested in non-primary-key-based querying in Riak, i.e. if
you're looking to go beyond straightforward K/V operations, we now
-recommend [Riak Search](/riak/kv/2.1.4/developing/usage/search/) rather than secondary indexes for
-a variety of reasons. Most importantly, Riak Search has a far more
+recommend [Riak search](/riak/kv/2.1.4/developing/usage/search/) rather than secondary indexes for
+a variety of reasons. Most importantly, Riak search has a far more
capacious querying API and can be used with all of Riak's storage
backends.
@@ -37,7 +37,7 @@ Secondary indexes can be either a binary or string, such as
`sensor_1_data` or `admin_user` or `click_event`, or an integer, such as
`99` or `141121`.
-[Riak Search](/riak/kv/2.1.4/developing/usage/search/) serves analogous purposes but is quite
+[Riak search](/riak/kv/2.1.4/developing/usage/search/) serves analogous purposes but is quite
different because it parses key/value data itself and builds indexes on
the basis of Solr schemas.
@@ -75,7 +75,7 @@ you to discover them later. Indexing enables you to tag those objects
and find all objects with the same tag in a specified bucket later on.
2i is thus recommended when your use case requires an easy-to-use search
-mechanism that does not require a schema (as does [Riak Search](/riak/kv/2.1.4/using/reference/search/#schemas)) and a basic query interface, i.e. an interface that
+mechanism that does not require a schema (as does [Riak search](/riak/kv/2.1.4/using/reference/search/#schemas)) and a basic query interface, i.e. an interface that
enables an application to tell Riak things like "fetch all objects
tagged with the string `Milwaukee_Bucks`" or "fetch all objects tagged
with numbers between 1500 and 1509."
@@ -89,7 +89,7 @@ piggybacks off of read-repair.
* If your ring size exceeds 512 partitions, 2i can cause performance
issues in large clusters.
* When you need more than the exact match and range searches that 2i
- supports. If that's the case, we recommend checking out [Riak Search](/riak/kv/2.1.4/developing/usage/search/).
+ supports. If that's the case, we recommend checking out [Riak search](/riak/kv/2.1.4/developing/usage/search/).
* When you want to use composite queries. A query like
`last_name=zezeski AND state=MD` would have to be split into two
queries and the results merged (or it would need to involve
diff --git a/content/riak/kv/2.1.4/introduction.md b/content/riak/kv/2.1.4/introduction.md
index 22a4d6175d..20d5d1b19d 100644
--- a/content/riak/kv/2.1.4/introduction.md
+++ b/content/riak/kv/2.1.4/introduction.md
@@ -30,10 +30,10 @@ that all of the new features listed below are optional:
* **Riak Data Types** --- Riak's new CRDT-based [Data Types](/riak/kv/2.1.4/developing/data-types) can
simplify modeling data in Riak, but are only used in buckets
explicitly configured to use them.
-* **Strong Consistency, Riak Security, and the New Riak Search** ---
+* **Strong Consistency, Riak Security, and the New Riak search** ---
These are subsystems in Riak that must be explicitly turned on to
work. If not turned on, they will have no impact on performance.
- Furthermore, the older Riak Search will continue to be included with
+ Furthermore, the older Riak search will continue to be included with
Riak.
* **Security** --- [Authentication and authorization](/riak/kv/2.1.4/using/security/basics) can be enabled
or disabled at any time.
@@ -98,21 +98,21 @@ Brown](https://github.com/russelldb).
## Riak Search 2.0 (codename: Yokozuna)
-Riak Search 2.0 is a complete, top-to-bottom replacement for Riak
-Search, integrating Riak with [Apache Solr](https://lucene.apache.org/solr/)'s full-text search capabilities and supporting Solr's client query APIs.
+Riak search 2.0 is a complete, top-to-bottom replacement for Riak
+search, integrating Riak with [Apache Solr](https://lucene.apache.org/solr/)'s full-text search capabilities and supporting Solr's client query APIs.
#### Relevant Docs
* [Using Search](/riak/kv/2.1.4/developing/usage/search) provides an overview of how to use the new
- Riak Search.
+ Riak search.
* [Search Schema](/riak/kv/2.1.4/developing/usage/search-schemas) shows you how to create and manage custom search
schemas.
* [Search Details](/riak/kv/2.1.4/using/reference/search) provides an in-depth look at the design
- considerations that went into the new Riak Search.
+ considerations that went into the new Riak search.
#### Video
-[Riak Search 2.0](https://www.youtube.com/watch?v=-c1eynVLNMo) by Basho
+[Riak search 2.0](https://www.youtube.com/watch?v=-c1eynVLNMo) by Basho
engineer and documentarian [Eric Redmond](https://github.com/coderoshi).
## Strong Consistency
@@ -145,7 +145,7 @@ check out [part 2](https://www.youtube.com/watch?v=gXJxbhca5Xg).
Riak 2.0 enables you to manage:
* **Authorization** to perform specific tasks, from GETs and PUTs to
-running MapReduce jobs to administering Riak Search.
+running MapReduce jobs to administering Riak search.
* **Authentication** of Riak clients seeking access to Riak.
@@ -317,7 +317,7 @@ another. Incompatibilities are marked with a
-**†** The data indexed by Riak Search can be
+**†** The data indexed by Riak search can be
stored in a strongly consistent fashion, but indexes themselves are
eventually consistent
**‡** If secondary indexes are attached to an
diff --git a/content/riak/kv/2.1.4/learn/concepts/strong-consistency.md b/content/riak/kv/2.1.4/learn/concepts/strong-consistency.md
index 323e9959ec..bf7942d0a3 100644
--- a/content/riak/kv/2.1.4/learn/concepts/strong-consistency.md
+++ b/content/riak/kv/2.1.4/learn/concepts/strong-consistency.md
@@ -20,7 +20,7 @@ aliases:
Please Note:
-Riak KV's strong consistency is an experimental feature and may be removed from the product in the future. Strong consistency is not commercially supported or production-ready. Strong consistency is incompatible with Multi-Datacenter Replication, Riak Search, Bitcask Expiration, LevelDB Secondary Indexes, Riak Data Types and Commit Hooks. We do not recommend its usage in any production environment.
+Riak KV's strong consistency is an experimental feature and may be removed from the product in the future. Strong consistency is not commercially supported or production-ready. Strong consistency is incompatible with Multi-Datacenter Replication, Riak search, Bitcask Expiration, LevelDB Secondary Indexes, Riak Data Types and Commit Hooks. We do not recommend its usage in any production environment.
Riak was originally designed as an [eventually consistent](/riak/kv/2.1.4/learn/concepts/eventual-consistency) system, fundamentally geared toward providing partition
diff --git a/content/riak/kv/2.1.4/learn/glossary.md b/content/riak/kv/2.1.4/learn/glossary.md
index 2cf117b736..7f6e233e05 100644
--- a/content/riak/kv/2.1.4/learn/glossary.md
+++ b/content/riak/kv/2.1.4/learn/glossary.md
@@ -278,7 +278,7 @@ best described as "UNIX pipes for Riak."
## Riak Search
-Riak Search is a distributed, scalable, failure-tolerant, realtime,
+Riak search is a distributed, scalable, failure-tolerant, realtime,
full-text search engine integrating [Apache
Solr](https://lucene.apache.org/solr/) with Riak KV.
diff --git a/content/riak/kv/2.1.4/learn/use-cases.md b/content/riak/kv/2.1.4/learn/use-cases.md
index fc6353b8f6..47cf8f2698 100644
--- a/content/riak/kv/2.1.4/learn/use-cases.md
+++ b/content/riak/kv/2.1.4/learn/use-cases.md
@@ -153,7 +153,7 @@ For storing log data from different systems, you could use unique
buckets for each system (e.g. `system1_log_data`, `system2_log_data`,
etc.) and write associated logs to the corresponding buckets. To
analyze that data, you could use Riak's MapReduce system for aggregation
-tasks, such as summing the counts of records for a date or Riak Search
+tasks, such as summing the counts of records for a date or Riak search
for a more robust, text-based queries.
### Log Data Complex Case
@@ -237,7 +237,7 @@ For simple retrieval of a specific account, a user ID (plus perhaps a
secondary index on a username or email) is enough. If you foresee the
need to make queries on additional user attributes (e.g. creation time,
user type, or region), plan ahead and either set up additional secondary
-indexes or consider using [Riak Search][usage search] to index the JSON
+indexes or consider using [Riak search][usage search] to index the JSON
contents of the user account.
### User Accounts Community Examples
@@ -323,7 +323,7 @@ In Riak, you can store content of any kind, from HTML files to plain
text to JSON or XML or another document type entirely. Keep in mind that
data in Riak is opaque, with the exception of [Riak Data Types](/riak/kv/2.1.4/developing/data-types),
and so Riak won't "know" about the object unless it is indexed
-[using Riak Search][usage search] or [using secondary indexes][usage secondary-indexes].
+[using Riak search][usage search] or [using secondary indexes][usage secondary-indexes].
### Articles et al Complex Case
@@ -342,7 +342,7 @@ with comments would require your application to call from the posts
and comments buckets to assemble the view.
Other possible cases may involve performing operations on content beyond
-key/value pairs. [Riak Search][usage search] is recommended for use cases
+key/value pairs. [Riak search][usage search] is recommended for use cases
involving full-text search. For lighter-weight querying,
[using secondary indexes][usage secondary-indexes] \(2i) enables you to add metadata to objects to
either query for exact matches or to perform range queries. 2i also
diff --git a/content/riak/kv/2.1.4/setup/installing/source/jvm.md b/content/riak/kv/2.1.4/setup/installing/source/jvm.md
index 9554c697f9..db8d33ced9 100644
--- a/content/riak/kv/2.1.4/setup/installing/source/jvm.md
+++ b/content/riak/kv/2.1.4/setup/installing/source/jvm.md
@@ -21,10 +21,10 @@ aliases:
[usage search]: /riak/kv/2.1.4/developing/usage/search
-If you are using [Riak Search 2.0][usage search], codename Yokozuna,
+If you are using [Riak search 2.0][usage search], codename Yokozuna,
you will need to install **Java 1.6 or later** to run [Apache
Solr](https://lucene.apache.org/solr/), the search platform that powers
-Riak Search.
+Riak search.
We recommend using Oracle's [JDK
7u25](http://www.oracle.com/technetwork/java/javase/7u25-relnotes-1955741.html).
@@ -35,7 +35,7 @@ page](http://www.oracle.com/technetwork/java/javase/documentation/index.html).
## Installing Solr on OS X
-If you're using Riak Search on Mac OS X, you may see the following
+If you're using Riak search on Mac OS X, you may see the following
error:
```java
diff --git a/content/riak/kv/2.1.4/setup/planning/backend/bitcask.md b/content/riak/kv/2.1.4/setup/planning/backend/bitcask.md
index 9e036fc31a..1dd1b79fb1 100644
--- a/content/riak/kv/2.1.4/setup/planning/backend/bitcask.md
+++ b/content/riak/kv/2.1.4/setup/planning/backend/bitcask.md
@@ -750,7 +750,7 @@ bitcask.expiry.grace_time = 1h
#### Automatic expiration and Riak Search
-If you are using [Riak Search][usage search] in conjunction with
+If you are using [Riak search][usage search] in conjunction with
Bitcask, please be aware that automatic expiry does not apply to [Search Indexes](../../../../developing/usage/search). If objects are indexed using Search,
those objects can be expired by Bitcask yet still registered in Search
indexes, which means that Search queries may return keys that no longer
diff --git a/content/riak/kv/2.1.4/setup/upgrading/checklist.md b/content/riak/kv/2.1.4/setup/upgrading/checklist.md
index ea0bd4a4ab..4160d7ddbe 100644
--- a/content/riak/kv/2.1.4/setup/upgrading/checklist.md
+++ b/content/riak/kv/2.1.4/setup/upgrading/checklist.md
@@ -89,7 +89,7 @@ We have compiled these considerations and questions into separate categories for
place if `allow_mult` is set to `true`?
- Have you carefully weighed the [consistency trade-offs][concept eventual consistency] that must be made if `allow_mult` is set to `false`?
- Are all of your [apps replication properties][apps replication properties] configured correctly and uniformly across the cluster?
- - If you are using [Riak Search][usage search], is it enabled on all
+ - If you are using [Riak search][usage search], is it enabled on all
nodes? If you are not, has it been disabled on all nodes?
- If you are using [strong consistency][concept strong consistency] for some or all of your
data:
diff --git a/content/riak/kv/2.1.4/setup/upgrading/search.md b/content/riak/kv/2.1.4/setup/upgrading/search.md
index 1ad8219f26..82e2321ac2 100644
--- a/content/riak/kv/2.1.4/setup/upgrading/search.md
+++ b/content/riak/kv/2.1.4/setup/upgrading/search.md
@@ -19,7 +19,7 @@ aliases:
If you're using Search in a version of Riak prior to 2.0 (1.3.0 to
1.4.x), you should follow these steps to migrate your search indexes
-from the legacy `merge_index` to the new Solr-backed ([Yokozuna](../../../using/reference/search) indexes. The legacy version of Riak Search is now deprecated
+from the legacy `merge_index` to the new Solr-backed ([Yokozuna](../../../using/reference/search) indexes. The legacy version of Riak search is now deprecated
and does not support most new 2.0 features, i.e. no [Riak Data Types](../../../developing/data-types), [bucket types](../../../using/reference/bucket-types), [strong consistency](../../../using/reference/strong-consistency), or [security](../../../using/security/)), so we highly recommend that you migrate.
And please note that the legacy `merge_index`-based search (aka legacy
@@ -35,7 +35,7 @@ these steps at a time when your cluster is relatively light on traffic,
i.e. _not_ the week before Christmas.
The main goal of a live migration is to stand up indexes in the new Riak
-Search that parallel the existing ones in legacy. New writes add entries
+search that parallel the existing ones in legacy. New writes add entries
to both indexes while AAE adds entries in the new indexes for existing
data.
@@ -75,7 +75,7 @@ algorithm is bad at getting rid of large index files.
## Steps to Upgrading
1. First, you'll perform a normal [rolling upgrade](../cluster).
- As you upgrade, enable `yokozuna` (the new Riak Search library) on
+ As you upgrade, enable `yokozuna` (the new Riak search library) on
each node. If you're still using `app.config` it's called `yokozuna`.
If you've chosen to upgrade to the new `riak.conf` config option, it's
called `search`.
@@ -223,7 +223,7 @@ have occurred on every node.
node you know that AAE has brought all new indexes up to date.
7. Next, call the following command that will give HTTP and PB query
-control to the new Riak Search.
+control to the new Riak search.
```curl
riak-admin search switch-to-new-search
@@ -247,7 +247,7 @@ buckets. This deactivates legacy Search.
-d '{"props":{"search": false}}'
```
-9. Disable the Riak Search process on each node by setting `riak_search`
+9. Disable the Riak search process on each node by setting `riak_search`
`enabled` to `false`.
```appconfig
diff --git a/content/riak/kv/2.1.4/setup/upgrading/version.md b/content/riak/kv/2.1.4/setup/upgrading/version.md
index 98fd745619..b34cfc7853 100644
--- a/content/riak/kv/2.1.4/setup/upgrading/version.md
+++ b/content/riak/kv/2.1.4/setup/upgrading/version.md
@@ -37,7 +37,7 @@ was built with those features in mind. There are official
While we strongly recommend using the newest versions of these clients,
older versions will still work with Riak 2.0, with the drawback that
-those older clients will not able to take advantage of [new features](/riak/kv/2.1.4/introduction) like [data types](/riak/kv/2.1.4/developing/data-types) or the new [Riak Search](/riak/kv/2.1.4/using/reference/search).
+those older clients will not able to take advantage of [new features](/riak/kv/2.1.4/introduction) like [data types](/riak/kv/2.1.4/developing/data-types) or the new [Riak search](/riak/kv/2.1.4/using/reference/search).
## Bucket Types
@@ -141,7 +141,7 @@ If you decide to upgrade to version 2.0, you can still downgrade your
cluster to an earlier version of Riak if you wish, _unless_ you perform
one of the following actions in your cluster:
-* Index data to be used in conjunction with the new [Riak Search](/riak/kv/2.1.4/using/reference/search).
+* Index data to be used in conjunction with the new [Riak search](/riak/kv/2.1.4/using/reference/search).
* Create _and_ activate one or more [bucket types](/riak/kv/2.1.4/using/reference/bucket-types/). By extension, you will not be able to downgrade your cluster if you have used the following features, both of which rely on bucket types:
- [Strong consistency](/riak/kv/2.1.4/using/reference/strong-consistency)
- [Riak Data Types](/riak/kv/2.1.4/developing/data-types)
@@ -209,7 +209,7 @@ default to a value of `15`, which can cause problems in some clusters.
## Upgrading Search
-Information on upgrading Riak Search to 2.0 can be found in our
+Information on upgrading Riak search to 2.0 can be found in our
[Search upgrade guide](/riak/kv/2.1.4/setup/upgrading/search).
## Migrating from Short Names
diff --git a/content/riak/kv/2.1.4/using/admin/riak-admin.md b/content/riak/kv/2.1.4/using/admin/riak-admin.md
index e6288396ba..6ce74ae421 100644
--- a/content/riak/kv/2.1.4/using/admin/riak-admin.md
+++ b/content/riak/kv/2.1.4/using/admin/riak-admin.md
@@ -590,7 +590,7 @@ riak-admin repair-2i kill
## search
The search command provides sub-commands for various administrative
-work related to the new Riak Search.
+work related to the new Riak search.
```bash
riak-admin search
@@ -639,7 +639,7 @@ riak-admin search switch-to-new-search
```
Switch handling of the HTTP `/solr//select` resource and
-protocol buffer query messages from legacy Riak Search to new Search
+protocol buffer query messages from legacy Riak search to new Search
(Yokozuna).
## services
diff --git a/content/riak/kv/2.1.4/using/cluster-operations/active-anti-entropy.md b/content/riak/kv/2.1.4/using/cluster-operations/active-anti-entropy.md
index f85eac31e1..96edcc22b8 100644
--- a/content/riak/kv/2.1.4/using/cluster-operations/active-anti-entropy.md
+++ b/content/riak/kv/2.1.4/using/cluster-operations/active-anti-entropy.md
@@ -262,9 +262,9 @@ AAE-related background tasks, analogous to [open files limit](../../performance/
## AAE and Riak Search
Riak's AAE subsystem works to repair object inconsistencies both with
-for normal key/value objects as well as data related to [Riak Search](../../../developing/usage/search). In particular, AAE acts on indexes stored in
+for normal key/value objects as well as data related to [Riak search](../../../developing/usage/search). In particular, AAE acts on indexes stored in
[Solr](http://lucene.apache.org/solr/), the search platform that drives
-Riak Search. Implementation details for AAE and Search can be found in
+Riak search. Implementation details for AAE and Search can be found in
the [Search Details](../../reference/search/#active-anti-entropy-aae)
documentation.
diff --git a/content/riak/kv/2.1.4/using/cluster-operations/inspecting-node.md b/content/riak/kv/2.1.4/using/cluster-operations/inspecting-node.md
index 251b5c1328..52933316ca 100644
--- a/content/riak/kv/2.1.4/using/cluster-operations/inspecting-node.md
+++ b/content/riak/kv/2.1.4/using/cluster-operations/inspecting-node.md
@@ -297,7 +297,7 @@ Stat | Description
`erlydtl_version` | [ErlyDTL](http://github.com/erlydtl/erlydtl)
`riak_control_version` | [Riak Control](http://github.com/basho/riak_control)
`cluster_info_version` | [Cluster Information](http://github.com/basho/cluster_info)
-`riak_search_version` | [Riak Search](http://github.com/basho/riak_search)
+`riak_search_version` | [Riak search](http://github.com/basho/riak_search)
`merge_index_version` | [Merge Index](http://github.com/basho/merge_index)
`riak_kv_version` | [Riak KV](http://github.com/basho/riak_kv)
`sidejob_version` | [Sidejob](http://github.com/basho/sidejob)
@@ -326,17 +326,17 @@ Stat | Description
### Riak Search Statistics
-The following statistics related to Riak Search message queues are
+The following statistics related to Riak search message queues are
available.
Stat | Description
-----------------------------|---------------------------------------------------
-`riak_search_vnodeq_max` | Maximum number of unprocessed messages all virtual node (vnode) message queues in the Riak Search subsystem have received on this node in the last minute
-`riak_search_vnodeq_mean` | Mean number of unprocessed messages all vnode message queues in the Riak Search subsystem have received on this node in the last minute
-`riak_search_vnodeq_median` | Median number of unprocessed messages all vnode message queues in the Riak Search subsystem have received on this node in the last minute
-`riak_search_vnodeq_min` | Minimum number of unprocessed messages all vnode message queues in the Riak Search subsystem have received on this node in the last minute
-`riak_search_vnodeq_total` | Total number of unprocessed messages all vnode message queues in the Riak Search subsystem have received on this node since it was started
-`riak_search_vnodes_running` | Total number of vnodes currently running in the Riak Search subsystem
+`riak_search_vnodeq_max` | Maximum number of unprocessed messages all virtual node (vnode) message queues in the Riak search subsystem have received on this node in the last minute
+`riak_search_vnodeq_mean` | Mean number of unprocessed messages all vnode message queues in the Riak search subsystem have received on this node in the last minute
+`riak_search_vnodeq_median` | Median number of unprocessed messages all vnode message queues in the Riak search subsystem have received on this node in the last minute
+`riak_search_vnodeq_min` | Minimum number of unprocessed messages all vnode message queues in the Riak search subsystem have received on this node in the last minute
+`riak_search_vnodeq_total` | Total number of unprocessed messages all vnode message queues in the Riak search subsystem have received on this node since it was started
+`riak_search_vnodes_running` | Total number of vnodes currently running in the Riak search subsystem
Note that under ideal operation and with the exception of
`riak_search_vnodes_running` these statistics should contain low values
@@ -449,7 +449,7 @@ Check | Description
`ring_membership` | Cluster membership validity
`ring_preflists` | Check if the ring satisfies `n_val`
`ring_size` | Check if the ring size valid
-`search` | Check whether Riak Search is enabled on all nodes
+`search` | Check whether Riak search is enabled on all nodes
The `--level` flag enables you to specify the log level and thus to
filter messages based on type. You can pass in any of the message types
diff --git a/content/riak/kv/2.1.4/using/cluster-operations/strong-consistency.md b/content/riak/kv/2.1.4/using/cluster-operations/strong-consistency.md
index 622b214fe9..be444683f1 100644
--- a/content/riak/kv/2.1.4/using/cluster-operations/strong-consistency.md
+++ b/content/riak/kv/2.1.4/using/cluster-operations/strong-consistency.md
@@ -14,7 +14,7 @@ toc: true
Please Note:
-Riak KV's strong consistency is an experimental feature and may be removed from the product in the future. Strong consistency is not commercially supported or production-ready. Strong consistency is incompatible with Multi-Datacenter Replication, Riak Search, Bitcask Expiration, LevelDB Secondary Indexes, Riak Data Types and Commit Hooks. We do not recommend its usage in any production environment.
+Riak KV's strong consistency is an experimental feature and may be removed from the product in the future. Strong consistency is not commercially supported or production-ready. Strong consistency is incompatible with Multi-Datacenter Replication, Riak search, Bitcask Expiration, LevelDB Secondary Indexes, Riak Data Types and Commit Hooks. We do not recommend its usage in any production environment.
## Monitoring Strong Consistency
diff --git a/content/riak/kv/2.1.4/using/reference/handoff.md b/content/riak/kv/2.1.4/using/reference/handoff.md
index 33a013c360..723fc41325 100644
--- a/content/riak/kv/2.1.4/using/reference/handoff.md
+++ b/content/riak/kv/2.1.4/using/reference/handoff.md
@@ -121,7 +121,7 @@ handoff.use_background_manager = on
### Maximum Rejects
-If you're using Riak features such as [Riak Search](/riak/kv/2.1.4/developing/usage/search/),
+If you're using Riak features such as [Riak search](/riak/kv/2.1.4/developing/usage/search/),
those subsystems can block handoff of primary key/value data, i.e. data
that you interact with via normal reads and writes.
diff --git a/content/riak/kv/2.1.4/using/reference/search.md b/content/riak/kv/2.1.4/using/reference/search.md
index 2c833220ca..2651c12b77 100644
--- a/content/riak/kv/2.1.4/using/reference/search.md
+++ b/content/riak/kv/2.1.4/using/reference/search.md
@@ -19,14 +19,14 @@ aliases:
> **Note on Search 2.0 vs. Legacy Search**
>
-> This document refers to the new Riak Search 2.0 with
+> This document refers to the new Riak search 2.0 with
[Solr](http://lucene.apache.org/solr/) integration (codenamed
-Yokozuna). For information about the deprecated Riak Search, visit [the old Using Riak Search docs](http://docs.basho.com/riak/1.4.10/dev/using/search/).
+Yokozuna). For information about the deprecated Riak search, visit [the old Using Riak search docs](http://docs.basho.com/riak/1.4.10/dev/using/search/).
-The project that implements Riak Search is codenamed Yokozuna. This is a
+The project that implements Riak search is codenamed Yokozuna. This is a
more detailed overview of the concepts and reasons behind the design of
Yokozuna, for those interested. If you're simply looking to use Riak
-Search, you should check out the [Using Search](/riak/kv/2.1.4/developing/usage/search) document.
+search, you should check out the [Using Search](/riak/kv/2.1.4/developing/usage/search) document.
@@ -35,30 +35,30 @@ Search, you should check out the [Using Search](/riak/kv/2.1.4/developing/usage/
In Erlang OTP, an "application" is a group of modules and Erlang
processes which together perform a specific task. The word application
is confusing because most people think of an application as an entire
-program such as Emacs or Photoshop. But Riak Search is just a sub-system
+program such as Emacs or Photoshop. But Riak search is just a sub-system
in Riak itself. Erlang applications are often stand-alone, but Riak
-Search is more like an appendage of Riak. It requires other subsystems
+search is more like an appendage of Riak. It requires other subsystems
like Riak Core and KV, but also extends their functionality by providing
search capabilities for KV data.
-The purpose of Riak Search is to bring more sophisticated and robust
+The purpose of Riak search is to bring more sophisticated and robust
query and search support to Riak. Many people consider Lucene and
programs built on top of it, such as Solr, as the standard for
open-source search. There are many successful applications built on
Lucene/Solr, and it sets the standard for the feature set that
developers and users expect. Meanwhile, Riak has a great story as a
-highly-available, distributed key/value store. Riak Search takes
+highly-available, distributed key/value store. Riak search takes
advantage of the fact that Riak already knows how to do the distributed
bits, combining its feature set with that of Solr, taking advantage of
the strengths of each.
-Riak Search is a mediator between Riak and Solr. There is nothing
+Riak search is a mediator between Riak and Solr. There is nothing
stopping a user from deploying these two programs separately, but this
would leave the user responsible for the glue between them. That glue
can be tricky to write. It requires dealing with monitoring, querying,
indexing, and dissemination of information.
-Unlike Solr by itself, Riak Search knows how to do all of the following:
+Unlike Solr by itself, Riak search knows how to do all of the following:
* Listen for changes in key/value (KV) data and to make the appropriate
changes to indexes that live in Solr. It also knows how to take a user
@@ -75,13 +75,13 @@ system (OS) process running a JVM which hosts Solr on the Jetty
application server. This OS process is a child of the Erlang OS process
running Riak.
-Riak Search has a `gen_server` process which monitors the JVM OS
+Riak search has a `gen_server` process which monitors the JVM OS
process. The code for this server is in `yz_solr_proc`. When the JVM
process crashes, this server crashes, causing its supervisor to restart
it.
If there is more than 1 restart in 45 seconds, the entire Riak node will
-be shut down. If Riak Search is enabled and Solr cannot function for
+be shut down. If Riak search is enabled and Solr cannot function for
some reason, the Riak node needs to go down so that the user will notice
and take corrective action.
@@ -91,7 +91,7 @@ This double monitoring along with the crash semantics means that neither
process may exist without the other. They are either both up or both
down.
-All other communication between Riak Search and Solr is performed via
+All other communication between Riak search and Solr is performed via
HTTP, including querying, indexing, and administration commands. The
ibrowse Erlang HTTP client is used to manage these communications as
both it and the Jetty container hosting Solr pool HTTP connections,
@@ -105,11 +105,11 @@ contains index entries for objects. Each such index maintains its own
set of files on disk---a critical difference from Riak KV, in which a
bucket is a purely logical entity and not physically disjoint at all. A
Solr index requires significantly less disk space than the corresponding
-legacy Riak Search index, depending on the Solr schema used.
+legacy Riak search index, depending on the Solr schema used.
Indexes may be associated with zero or more buckets. At creation time,
however, each index has no associated buckets---unlike the legacy Riak
-Search, indexes in the new Riak Search do not implicitly create bucket
+search, indexes in the new Riak search do not implicitly create bucket
associations, meaning that this must be done as a separate configuration
step.
@@ -141,7 +141,7 @@ flat collection of field-value pairs. "Flat" here means that a field's
value cannot be a nested structure of field-value pairs; the values are
treated as-is (non-composite is another way to say it).
-Because of this mismatch between KV and Solr, Riak Search must act as a
+Because of this mismatch between KV and Solr, Riak search must act as a
mediator between the two, meaning it must have a way to inspect a KV
object and create a structure which Solr can ingest for indexing. In
Solr this structure is called a **document**. This task of creating a
diff --git a/content/riak/kv/2.1.4/using/reference/secondary-indexes.md b/content/riak/kv/2.1.4/using/reference/secondary-indexes.md
index 92e47757bd..b79d979cdd 100644
--- a/content/riak/kv/2.1.4/using/reference/secondary-indexes.md
+++ b/content/riak/kv/2.1.4/using/reference/secondary-indexes.md
@@ -18,11 +18,11 @@ aliases:
[usage bucket types]: /riak/kv/2.1.4/developing/usage/bucket-types
[use ref strong consistency]: /riak/kv/2.1.4/using/reference/strong-consistency
-> **Note: Riak Search preferred for querying**
+> **Note: Riak search preferred for querying**
>
> If you're interested in non-primary-key-based querying in Riak, i.e. if
you're looking to go beyond straightforward K/V operations, we now
-recommend [Riak Search](/riak/kv/2.1.4/developing/usage/search/) rather than secondary indexes for a variety of reasons. Riak Search has a far more capacious querying API and can be used with all of Riak's storage backends.
+recommend [Riak search](/riak/kv/2.1.4/developing/usage/search/) rather than secondary indexes for a variety of reasons. Riak search has a far more capacious querying API and can be used with all of Riak's storage backends.
This document provides implementation and other details for Riak's
[secondary indexes](/riak/kv/2.1.4/developing/usage/secondary-indexes/) \(2i) feature.
diff --git a/content/riak/kv/2.1.4/using/reference/statistics-monitoring.md b/content/riak/kv/2.1.4/using/reference/statistics-monitoring.md
index 0d4505870e..9fb1cb5d17 100644
--- a/content/riak/kv/2.1.4/using/reference/statistics-monitoring.md
+++ b/content/riak/kv/2.1.4/using/reference/statistics-monitoring.md
@@ -134,7 +134,7 @@ Metric | Also | Notes
:------|:-----|:------------------
```node_get_fsm_siblings_mean``` | ```_median```, ```_95```, ```_99```, ```_100``` | Number of siblings encountered during all GET operations by this node within the last minute. Watch for abnormally high sibling counts, especially max ones.
```node_get_fsm_objsize_mean``` | ```_median```, ```_95```, ```_99```, ```_100``` | Object size encountered by this node within the last minute. Abnormally large objects (especially paired with high sibling counts) can indicate sibling explosion.
-```riak_search_vnodeq_mean``` | ```_median```, ```_95```, ```_99```, ```_100``` | Number of unprocessed messages in the vnode message queues of the Riak Search subsystem on this node in the last minute. The queues give you an idea of how backed up Solr is getting.
+```riak_search_vnodeq_mean``` | ```_median```, ```_95```, ```_99```, ```_100``` | Number of unprocessed messages in the vnode message queues of the Riak search subsystem on this node in the last minute. The queues give you an idea of how backed up Solr is getting.
```search_index_fail_one``` | | Number of "Failed to index document" errors Search encountered for the last minute
```pbc_active``` | | Number of currently active protocol buffer connections
```pbc_connects``` | | Number of new protocol buffer connections established during the last minute
diff --git a/content/riak/kv/2.1.4/using/reference/strong-consistency.md b/content/riak/kv/2.1.4/using/reference/strong-consistency.md
index 29e1bf3083..f5eb8e73e6 100644
--- a/content/riak/kv/2.1.4/using/reference/strong-consistency.md
+++ b/content/riak/kv/2.1.4/using/reference/strong-consistency.md
@@ -17,7 +17,7 @@ toc: true
Please Note:
-Riak KV's strong consistency is an experimental feature and may be removed from the product in the future. Strong consistency is not commercially supported or production-ready. Strong consistency is incompatible with Multi-Datacenter Replication, Riak Search, Bitcask Expiration, LevelDB Secondary Indexes, Riak Data Types and Commit Hooks. We do not recommend its usage in any production environment.
+Riak KV's strong consistency is an experimental feature and may be removed from the product in the future. Strong consistency is not commercially supported or production-ready. Strong consistency is incompatible with Multi-Datacenter Replication, Riak search, Bitcask Expiration, LevelDB Secondary Indexes, Riak Data Types and Commit Hooks. We do not recommend its usage in any production environment.
Riak was originally designed as an [eventually consistent](/riak/kv/2.1.4/learn/concepts/eventual-consistency) system, fundamentally geared toward providing partition
diff --git a/content/riak/kv/2.1.4/using/repair-recovery/errors.md b/content/riak/kv/2.1.4/using/repair-recovery/errors.md
index 9523753414..5642ee6e8b 100644
--- a/content/riak/kv/2.1.4/using/repair-recovery/errors.md
+++ b/content/riak/kv/2.1.4/using/repair-recovery/errors.md
@@ -328,7 +328,7 @@ exit with reason bad return value: {error,eaddrinuse} in context start_error | A
exited with reason: eaddrnotavail in gen_server:init_it/6 line 320 | An error like this example can result when Riak cannot bind to the addresses specified in the configuration. In this case, you should verify HTTP and Protocol Buffers addresses in `app.config` and ensure that the ports being used are not in the privileged (1-1024) range as the `riak` user will not have access to such ports.
gen_server riak_core_capability terminated with reason: no function clause matching orddict:fetch('riak@192.168.2.2', []) line 72 | Error output like this example can indicate that a previously running Riak node with an original `-name` value in `vm.args` has been modified by simply changing the value in `vm.args` and not properly through `riak-admin cluster replace`.
** Configuration error: [FRAMEWORK-MIB]: missing context.conf file => generating a default file | This error is commonly encountered when starting Riak Enterprise without prior [SNMP](/riak/kv/2.1.4/using/reference/snmp) configuration.
-RPC to 'node@example.com' failed: {'EXIT', {badarg, [{ets,lookup, [schema_table,<<"search-example">>], []} {riak_search_config,get_schema,1, [{file,"src/riak_search_config.erl"}, {line,69}]} ...| This error can be caused when attempting to use Riak Search without first enabling it in each node's `app.config`. See the [configuration files][config reference] documentation for more information on enabling Riak Search.
+RPC to 'node@example.com' failed: {'EXIT', {badarg, [{ets,lookup, [schema_table,<<"search-example">>], []} {riak_search_config,get_schema,1, [{file,"src/riak_search_config.erl"}, {line,69}]} ...| This error can be caused when attempting to use Riak search without first enabling it in each node's `app.config`. See the [configuration files][config reference] documentation for more information on enabling Riak search.
### More
diff --git a/content/riak/kv/2.1.4/using/repair-recovery/repairs.md b/content/riak/kv/2.1.4/using/repair-recovery/repairs.md
index 74609b55a2..619924e4c1 100644
--- a/content/riak/kv/2.1.4/using/repair-recovery/repairs.md
+++ b/content/riak/kv/2.1.4/using/repair-recovery/repairs.md
@@ -57,7 +57,7 @@ riak-admin repair-2i kill
## Repairing Search Indexes
-Riak Search indexes currently have no form of anti-entropy (such as read-repair). Furthermore, for performance and load balancing reasons, Search reads from one random node. This means that when a replica loss has occurred, inconsistent results may be returned.
+Riak search indexes currently have no form of anti-entropy (such as read-repair). Furthermore, for performance and load balancing reasons, Search reads from one random node. This means that when a replica loss has occurred, inconsistent results may be returned.
### Running a Repair
diff --git a/content/riak/kv/2.1.4/using/repair-recovery/secondary-indexes.md b/content/riak/kv/2.1.4/using/repair-recovery/secondary-indexes.md
index 9184a47c7b..30f98c1cae 100644
--- a/content/riak/kv/2.1.4/using/repair-recovery/secondary-indexes.md
+++ b/content/riak/kv/2.1.4/using/repair-recovery/secondary-indexes.md
@@ -51,7 +51,7 @@ riak-admin repair-2i kill
## Repairing Search Indexes
-Riak Search indexes currently have no form of anti-entropy (such as read-repair). Furthermore, for performance and load balancing reasons, Search reads from one random node. This means that when a replica loss has occurred, inconsistent results may be returned.
+Riak search indexes currently have no form of anti-entropy (such as read-repair). Furthermore, for performance and load balancing reasons, Search reads from one random node. This means that when a replica loss has occurred, inconsistent results may be returned.
### Running a Repair
diff --git a/content/riak/kv/2.1.4/using/security/basics.md b/content/riak/kv/2.1.4/using/security/basics.md
index 07a6e52e9a..7b71ddab58 100644
--- a/content/riak/kv/2.1.4/using/security/basics.md
+++ b/content/riak/kv/2.1.4/using/security/basics.md
@@ -44,7 +44,7 @@ when turning on Riak security. Missing one of these steps will almost
certainly break your application, so make sure that you have done each
of the following **before** enabling security:
-1. Make certain that the original Riak Search (version 1) and link
+1. Make certain that the original Riak search (version 1) and link
walking are not required. Enabling security will break this
functionality. If you wish to use security and Search together, you
will need to use the [new Search feature](/riak/kv/2.1.4/developing/usage/search/).
@@ -487,11 +487,11 @@ Permission | Operation
### Search Query Permission (Riak Search version 1)
Security is incompatible with the original (and now deprecated) Riak
-Search. Riak Search version 1 will stop working if security is enabled.
+search. Riak search version 1 will stop working if security is enabled.
### Search Query Permissions (Riak Search version 2, aka Yokozuna)
-If you are using the new Riak Search, i.e. the Solr-compatible search
+If you are using the new Riak search, i.e. the Solr-compatible search
capabilities included with Riak versions 2.0 and greater, the following
search-related permissions can be granted/revoked:
@@ -508,8 +508,8 @@ disabled, you will get the following error:
>
> `{error,{unknown_permission,"search.query"}}`
>
-> More information on Riak Search and how to enable it can be found in the
-[Riak Search Settings](/riak/kv/2.1.4/configuring/search/) document.
+> More information on Riak search and how to enable it can be found in the
+[Riak search Settings](/riak/kv/2.1.4/configuring/search/) document.
#### Usage Examples
diff --git a/content/riak/kv/2.2.0/configuring/reference.md b/content/riak/kv/2.2.0/configuring/reference.md
index 61024540f8..aefc4c13b7 100644
--- a/content/riak/kv/2.2.0/configuring/reference.md
+++ b/content/riak/kv/2.2.0/configuring/reference.md
@@ -1343,7 +1343,7 @@ Configurable parameters for intra-cluster, i.e. inter-node, [handoff][cluster op
handoff.max_rejects |
The maximum number of times that a secondary system within Riak,
-such as Riak Search, can block handoff
+such as Riak search, can block handoff
of primary key/value data. The approximate maximum duration that a vnode
can be blocked can be determined by multiplying this setting by
vnode_management_timer. If you want to prevent handoff from
@@ -1587,7 +1587,7 @@ if the JMX server crashes. |
> **Please Note:**
>
-> Riak KV's strong consistency is an experimental feature and may be removed from the product in the future. Strong consistency is not commercially supported or production-ready. Strong consistency is incompatible with Multi-Datacenter Replication, Riak Search, Bitcask Expiration, LevelDB Secondary Indexes, Riak Data Types and Commit Hooks. We do not recommend its usage in any production environment.
+> Riak KV's strong consistency is an experimental feature and may be removed from the product in the future. Strong consistency is not commercially supported or production-ready. Strong consistency is incompatible with Multi-Datacenter Replication, Riak search, Bitcask Expiration, LevelDB Secondary Indexes, Riak Data Types and Commit Hooks. We do not recommend its usage in any production environment.
Riak's strong consistency feature has a variety of tunable parameters
that allow you to enable and disable strong consistency, modify the
@@ -2010,7 +2010,7 @@ only in Riak Enterprise 2.0 and later.
#### Upgrading Riak Search with `advanced.config`
-If you are upgrading to Riak 2.x and wish to upgrade to the new [Riak Search][use ref search]\(codename Yokozuna), you will need to enable
+If you are upgrading to Riak 2.x and wish to upgrade to the new [Riak search][use ref search]\(codename Yokozuna), you will need to enable
legacy Search while the upgrade is underway. You can add the following
snippet to your `advanced.config` configuration to do so:
diff --git a/content/riak/kv/2.2.0/configuring/search.md b/content/riak/kv/2.2.0/configuring/search.md
index fe77bf94d2..41ce2216c2 100644
--- a/content/riak/kv/2.2.0/configuring/search.md
+++ b/content/riak/kv/2.2.0/configuring/search.md
@@ -26,12 +26,12 @@ aliases:
[security index]: /riak/kv/2.2.0/using/security/
-This page covers how to use Riak Search (with
+This page covers how to use Riak search (with
[Solr](http://lucene.apache.org/solr/) integration).
For a simple reference of the available configs and their defaults, see the [configuration reference][config reference#search].
-If you are looking to develop on or with Riak Search, take a look at:
+If you are looking to develop on or with Riak search, take a look at:
* [Using Search][usage search]
* [Search Schema][usage search schema]
@@ -43,7 +43,7 @@ If you are looking to develop on or with Riak Search, take a look at:
We'll be walking through:
1. [Prequisites](#prerequisites)
-2. [Enable Riak Search](#enabling-riak-search)
+2. [Enable Riak search](#enabling-riak-search)
3. [Search Configuration Settings](#search-config-settings)
4. [Additional Solr Information](#more-on-solr)
@@ -60,7 +60,7 @@ page](http://www.oracle.com/technetwork/java/javase/documentation/index.html).
## Enabling Riak Search
-Riak Search is not enabled by default, so you must enable it in every
+Riak search is not enabled by default, so you must enable it in every
node's [configuration file][config reference] as follows:
```riak.conf
@@ -70,7 +70,7 @@ search = on
## Search Config Settings
-You will find all the Riak Search configuration settings in riak.conf. Setting `search` to `on` is required, but other search settings are optional. A handy reference list of these parameters can be found in our [configuration files][config reference#search] documentation.
+You will find all the Riak search configuration settings in riak.conf. Setting `search` to `on` is required, but other search settings are optional. A handy reference list of these parameters can be found in our [configuration files][config reference#search] documentation.
### `search`
@@ -80,7 +80,7 @@ Valid values: `on` or `off`
### `search.anti_entropy.data_dir`
-The directory in which Riak Search stores files related to [active anti-entropy][glossary aae]; defaults to `./data/yz_anti_entropy`.
+The directory in which Riak search stores files related to [active anti-entropy][glossary aae]; defaults to `./data/yz_anti_entropy`.
Valid values: a directory
@@ -198,7 +198,7 @@ Valid valus: Integer
The queue high water mark; defaults to `1000`.
-If the total number of queued messages in a Solrq worker instance exceed this limit, then the calling vnode will be blocked until the total number falls below this limit. This parameter exercises flow control between Riak KV and the Riak Search batching subsystem, if writes into Solr start to fall behind.
+If the total number of queued messages in a Solrq worker instance exceed this limit, then the calling vnode will be blocked until the total number falls below this limit. This parameter exercises flow control between Riak KV and the Riak search batching subsystem, if writes into Solr start to fall behind.
Valid values: Integer
@@ -250,7 +250,7 @@ Valid values: Integer with time units (e.g. 2m)
## More on Solr
### Solr JVM and Ports
-Riak Search runs one Solr process per node to manage its indexing and
+Riak search runs one Solr process per node to manage its indexing and
search functionality. While the underlying project manages
index distribution, node coverage for queries, active anti-entropy
(AAE), and JVM process management, you should provide plenty of RAM and diskspace for running both Riak and the JVM running Solr. We recommend a minimum of 6GB of RAM per node.
diff --git a/content/riak/kv/2.2.0/configuring/strong-consistency.md b/content/riak/kv/2.2.0/configuring/strong-consistency.md
index 3c58a254e2..79754743be 100644
--- a/content/riak/kv/2.2.0/configuring/strong-consistency.md
+++ b/content/riak/kv/2.2.0/configuring/strong-consistency.md
@@ -38,7 +38,7 @@ toc: true
> **Please Note:**
>
-> Riak KV's strong consistency is an experimental feature and may be removed from the product in the future. Strong consistency is not commercially supported or production-ready. Strong consistency is incompatible with Multi-Datacenter Replication, Riak Search, Bitcask Expiration, LevelDB Secondary Indexes, Riak Data Types and Commit Hooks. We do not recommend its usage in any production environment.
+> Riak KV's strong consistency is an experimental feature and may be removed from the product in the future. Strong consistency is not commercially supported or production-ready. Strong consistency is incompatible with Multi-Datacenter Replication, Riak search, Bitcask Expiration, LevelDB Secondary Indexes, Riak Data Types and Commit Hooks. We do not recommend its usage in any production environment.
This document provides information on configuring and monitoring a Riak
cluster's optional strong consistency subsystem. Documentation for
diff --git a/content/riak/kv/2.2.0/developing/api/http/delete-search-index.md b/content/riak/kv/2.2.0/developing/api/http/delete-search-index.md
index f9832889b8..0cb63d0b43 100644
--- a/content/riak/kv/2.2.0/developing/api/http/delete-search-index.md
+++ b/content/riak/kv/2.2.0/developing/api/http/delete-search-index.md
@@ -15,7 +15,7 @@ aliases:
- /riak/kv/2.2.0/dev/references/http/delete-search-index
---
-Deletes a Riak Search index.
+Deletes a Riak search index.
## Request
diff --git a/content/riak/kv/2.2.0/developing/api/http/fetch-search-index.md b/content/riak/kv/2.2.0/developing/api/http/fetch-search-index.md
index c78df42599..95d23b4209 100644
--- a/content/riak/kv/2.2.0/developing/api/http/fetch-search-index.md
+++ b/content/riak/kv/2.2.0/developing/api/http/fetch-search-index.md
@@ -15,7 +15,7 @@ aliases:
- /riak/kv/2.2.0/dev/references/http/fetch-search-index
---
-Retrieves information about a Riak Search [index](/riak/kv/2.2.0/developing/usage/search/#simple-setup).
+Retrieves information about a Riak search [index](/riak/kv/2.2.0/developing/usage/search/#simple-setup).
## Request
diff --git a/content/riak/kv/2.2.0/developing/api/http/fetch-search-schema.md b/content/riak/kv/2.2.0/developing/api/http/fetch-search-schema.md
index ecd2fc74f6..06e19c89f0 100644
--- a/content/riak/kv/2.2.0/developing/api/http/fetch-search-schema.md
+++ b/content/riak/kv/2.2.0/developing/api/http/fetch-search-schema.md
@@ -35,4 +35,4 @@ GET /search/schema/
## Response
If the schema is found, Riak will return the contents of the schema as
-XML (all Riak Search schemas are XML).
+XML (all Riak search schemas are XML).
diff --git a/content/riak/kv/2.2.0/developing/api/http/search-index-info.md b/content/riak/kv/2.2.0/developing/api/http/search-index-info.md
index f0f7daf45b..74480d7c4d 100644
--- a/content/riak/kv/2.2.0/developing/api/http/search-index-info.md
+++ b/content/riak/kv/2.2.0/developing/api/http/search-index-info.md
@@ -47,6 +47,6 @@ Below is the example output if there is one Search index, called
#### Typical Error Codes
-* `404 Object Not Found` --- Typically returned if Riak Search is not
+* `404 Object Not Found` --- Typically returned if Riak search is not
currently enabled on the node
* `503 Service Unavailable` --- The request timed out internally
diff --git a/content/riak/kv/2.2.0/developing/api/http/store-search-index.md b/content/riak/kv/2.2.0/developing/api/http/store-search-index.md
index 0355647835..46783e5f12 100644
--- a/content/riak/kv/2.2.0/developing/api/http/store-search-index.md
+++ b/content/riak/kv/2.2.0/developing/api/http/store-search-index.md
@@ -15,7 +15,7 @@ aliases:
- /riak/kv/2.2.0/dev/references/http/store-search-index
---
-Creates a new Riak Search [index](/riak/kv/2.2.0/developing/usage/search/#simple-setup).
+Creates a new Riak search [index](/riak/kv/2.2.0/developing/usage/search/#simple-setup).
## Request
diff --git a/content/riak/kv/2.2.0/developing/api/http/store-search-schema.md b/content/riak/kv/2.2.0/developing/api/http/store-search-schema.md
index ef7db5d322..f9251920d2 100644
--- a/content/riak/kv/2.2.0/developing/api/http/store-search-schema.md
+++ b/content/riak/kv/2.2.0/developing/api/http/store-search-schema.md
@@ -44,7 +44,7 @@ curl -XPUT http://localhost:8098/search/schema/my_custom_schema \
* `400 Bad Request` --- The schema cannot be created because there is
something wrong with the schema itself, e.g. an XML formatting error
- that makes Riak Search unable to parse the schema
+ that makes Riak search unable to parse the schema
* `409 Conflict` --- The schema cannot be created because there is
already a schema with that name
* `503 Service Unavailable` --- The request timed out internally
diff --git a/content/riak/kv/2.2.0/developing/api/protocol-buffers/yz-index-get.md b/content/riak/kv/2.2.0/developing/api/protocol-buffers/yz-index-get.md
index 835504409d..e36be501da 100644
--- a/content/riak/kv/2.2.0/developing/api/protocol-buffers/yz-index-get.md
+++ b/content/riak/kv/2.2.0/developing/api/protocol-buffers/yz-index-get.md
@@ -15,7 +15,7 @@ aliases:
- /riak/kv/2.2.0/dev/references/protocol-buffers/yz-index-get
---
-Retrieve a search index from Riak Search.
+Retrieve a search index from Riak search.
## Request
diff --git a/content/riak/kv/2.2.0/developing/api/protocol-buffers/yz-schema-get.md b/content/riak/kv/2.2.0/developing/api/protocol-buffers/yz-schema-get.md
index 032322a718..532846820b 100644
--- a/content/riak/kv/2.2.0/developing/api/protocol-buffers/yz-schema-get.md
+++ b/content/riak/kv/2.2.0/developing/api/protocol-buffers/yz-schema-get.md
@@ -15,7 +15,7 @@ aliases:
- /riak/kv/2.2.0/dev/references/protocol-buffers/yz-schema-get
---
-Fetch a [search schema](/riak/kv/2.2.0/developing/usage/search-schemas) from Riak Search.
+Fetch a [search schema](/riak/kv/2.2.0/developing/usage/search-schemas) from Riak search.
## Request
diff --git a/content/riak/kv/2.2.0/developing/app-guide.md b/content/riak/kv/2.2.0/developing/app-guide.md
index 36d0eba99c..49540769a6 100644
--- a/content/riak/kv/2.2.0/developing/app-guide.md
+++ b/content/riak/kv/2.2.0/developing/app-guide.md
@@ -147,22 +147,22 @@ well as relevant links to Basho documentation.
## Search
-Riak Search provides you with [Apache
+Riak search provides you with [Apache
Solr](http://lucene.apache.org/solr/)-powered full-text indexing and
querying on top of the scalability, fault tolerance, and operational
-simplicity of Riak. Our motto for Riak Search: **Write it like Riak.
+simplicity of Riak. Our motto for Riak search: **Write it like Riak.
Query it like Solr**. That is, you can store objects in Riak [like normal][usage create objects] and run full-text queries on those objects later on
using the Solr API.
-* [Using Search][usage search] --- Getting started with Riak Search
+* [Using Search][usage search] --- Getting started with Riak search
* [Search Details][use ref search] --- A detailed overview of the concepts and design
- consideration behind Riak Search
+ consideration behind Riak search
* [Search Schema][usage search schema] --- How to create custom schemas for extracting data
- from Riak Search
+ from Riak search
### When to Use Search
-* **When you need a rich querying API** --- Riak Search gives you access
+* **When you need a rich querying API** --- Riak search gives you access
to the entirety of [Solr](http://lucene.apache.org/solr/)'s extremely
broad API, which enables you to query on the basis of wildcards,
strings, booleans, geolocation, ranges, language-specific fulltext,
@@ -214,7 +214,7 @@ own.
> **Note**:
>
-> Riak Data Types can be used in conjunction with Riak Search,
+> Riak Data Types can be used in conjunction with Riak search,
meaning that the data stored in counters, sets, and maps can be indexed
and searched just like any other data in Riak. Documentation on Data
Types and Search is coming soon.
@@ -278,13 +278,13 @@ or you can write and run your own MapReduce jobs in
### When Not to Use MapReduce
* **When another Riak feature will do** --- Before even considering
- using MapReduce, you should thoroughly investigate [Riak Search][usage search] or [secondary indexes][usage 2i] as possible
+ using MapReduce, you should thoroughly investigate [Riak search][usage search] or [secondary indexes][usage 2i] as possible
solutions to your needs.
In general, you should not think of MapReduce as, for example, Hadoop
within Riak. While it can be useful for certain types of
non-primary-key-based queries, it is neither a "Big Data" processing
-tool nor an indexing mechanism nor a replacement for [Riak Search][usage search]. If you do need a tool like Hadoop or Apache Spark, you should
+tool nor an indexing mechanism nor a replacement for [Riak search][usage search]. If you do need a tool like Hadoop or Apache Spark, you should
consider using Riak in conjunction with a more suitable data processing
tool.
@@ -295,7 +295,7 @@ following problem: how do I know which keys I should look for? Secondary
indexes (2i) provide a solution to this problem, enabling you to tag
objects with either binary or integer metadata and then query Riak for
all of the keys that share specific tags. 2i is especially useful if
-you're storing binary data that is opaque to features like [Riak Search][usage search].
+you're storing binary data that is opaque to features like [Riak search][usage search].
* [Using Secondary Indexes][usage 2i] --- A general guide to using 2i, along
with code samples and information on 2i features like pagination,
@@ -323,7 +323,7 @@ you're storing binary data that is opaque to features like [Riak Search][usage s
One thing to always bear in mind is that Riak enables you to mix and
match a wide variety of approaches in a single cluster. You can use
basic CRUD operations for some of your data, index some of your data to
-be queried by Riak Search, use Riak Data Types for another subset, etc.
+be queried by Riak search, use Riak Data Types for another subset, etc.
You are always free to use a wide array of Riak features---or you can
use none at all and stick to key/value operations.
diff --git a/content/riak/kv/2.2.0/developing/app-guide/advanced-mapreduce.md b/content/riak/kv/2.2.0/developing/app-guide/advanced-mapreduce.md
index 1f5ccd089c..f8e3666b0e 100644
--- a/content/riak/kv/2.2.0/developing/app-guide/advanced-mapreduce.md
+++ b/content/riak/kv/2.2.0/developing/app-guide/advanced-mapreduce.md
@@ -77,7 +77,7 @@ MapReduce should generally be treated as a fallback rather than a
standard part of an application. There are often ways to model data
such that dynamic queries become single key retrievals, which are
dramatically faster and more reliable in Riak, and tools such as Riak
-Search and 2i are simpler to use and may place less strain on a
+search and 2i are simpler to use and may place less strain on a
cluster.
### R=1
diff --git a/content/riak/kv/2.2.0/developing/app-guide/strong-consistency.md b/content/riak/kv/2.2.0/developing/app-guide/strong-consistency.md
index efa696144c..99fc4943ed 100644
--- a/content/riak/kv/2.2.0/developing/app-guide/strong-consistency.md
+++ b/content/riak/kv/2.2.0/developing/app-guide/strong-consistency.md
@@ -37,7 +37,7 @@ aliases:
> **Please Note:**
>
-> Riak KV's strong consistency is an experimental feature and may be removed from the product in the future. Strong consistency is not commercially supported or production-ready. Strong consistency is incompatible with Multi-Datacenter Replication, Riak Search, Bitcask Expiration, LevelDB Secondary Indexes, Riak Data Types and Commit Hooks. We do not recommend its usage in any production environment.
+> Riak KV's strong consistency is an experimental feature and may be removed from the product in the future. Strong consistency is not commercially supported or production-ready. Strong consistency is incompatible with Multi-Datacenter Replication, Riak search, Bitcask Expiration, LevelDB Secondary Indexes, Riak Data Types and Commit Hooks. We do not recommend its usage in any production environment.
In versions 2.0 and later, Riak allows you to create buckets that
provide [strong consistency][use ref strong consistency] guarantees for the data stored within
diff --git a/content/riak/kv/2.2.0/developing/data-modeling.md b/content/riak/kv/2.2.0/developing/data-modeling.md
index 80d92a02e3..e9d25c25f1 100644
--- a/content/riak/kv/2.2.0/developing/data-modeling.md
+++ b/content/riak/kv/2.2.0/developing/data-modeling.md
@@ -140,7 +140,7 @@ For storing log data from different systems, you could use unique
buckets for each system (e.g. `system1_log_data`, `system2_log_data`,
etc.) and write associated logs to the corresponding buckets. To
analyze that data, you could use Riak's MapReduce system for aggregation
-tasks, such as summing the counts of records for a date or Riak Search
+tasks, such as summing the counts of records for a date or Riak search
for a more robust, text-based queries.
### Log Data Complex Case
@@ -224,7 +224,7 @@ For simple retrieval of a specific account, a user ID (plus perhaps a
secondary index on a username or email) is enough. If you foresee the
need to make queries on additional user attributes (e.g. creation time,
user type, or region), plan ahead and either set up additional secondary
-indexes or consider using [Riak Search](/riak/kv/2.2.0/developing/usage/search/) to index the JSON
+indexes or consider using [Riak search](/riak/kv/2.2.0/developing/usage/search/) to index the JSON
contents of the user account.
### User Accounts Community Examples
@@ -310,7 +310,7 @@ In Riak, you can store content of any kind, from HTML files to plain
text to JSON or XML or another document type entirely. Keep in mind that
data in Riak is opaque, with the exception of [Riak Data Types](/riak/kv/2.2.0/developing/data-types),
and so Riak won't "know" about the object unless it is indexed
-[using Riak Search](/riak/kv/2.2.0/developing/usage/search/) or [using secondary indexes](/riak/kv/2.2.0/developing/usage/secondary-indexes/).
+[using Riak search](/riak/kv/2.2.0/developing/usage/search/) or [using secondary indexes](/riak/kv/2.2.0/developing/usage/secondary-indexes/).
### Articles et al Complex Case
@@ -329,7 +329,7 @@ with comments would require your application to call from the posts
and comments buckets to assemble the view.
Other possible cases may involve performing operations on content beyond
-key/value pairs. [Riak Search](/riak/kv/2.2.0/developing/usage/search/) is recommended for use cases
+key/value pairs. [Riak search](/riak/kv/2.2.0/developing/usage/search/) is recommended for use cases
involving full-text search. For lighter-weight querying,
[using secondary indexes](/riak/kv/2.2.0/developing/usage/secondary-indexes/) \(2i) enables you to add metadata to objects to
either query for exact matches or to perform range queries. 2i also
diff --git a/content/riak/kv/2.2.0/developing/data-types.md b/content/riak/kv/2.2.0/developing/data-types.md
index 287e5f7335..630e2be219 100644
--- a/content/riak/kv/2.2.0/developing/data-types.md
+++ b/content/riak/kv/2.2.0/developing/data-types.md
@@ -266,7 +266,7 @@ All the examples use the bucket type names from above (`counters`, `sets`, and `
Riak data types can be searched like any other object, but with the
added benefit that your data type is indexed as a different type by Solr,
-the search platform behind Riak Search.
+the search platform behind Riak search.
In our Search documentation we offer a [full tutorial](../usage/searching-data-types) as well as a variety of [examples](../usage/search/#data-types-and-search-examples), including code
samples from each of our official client libraries.
diff --git a/content/riak/kv/2.2.0/developing/usage.md b/content/riak/kv/2.2.0/developing/usage.md
index fd9b3f187e..5850027431 100644
--- a/content/riak/kv/2.2.0/developing/usage.md
+++ b/content/riak/kv/2.2.0/developing/usage.md
@@ -107,7 +107,7 @@ Tutorial on using Riak KV as a document store.
#### [Custom Extractors](./custom-extractors)
-Details on creating and registering custom extractors with Riak Search.
+Details on creating and registering custom extractors with Riak search.
[Learn More >>](./custom-extractors)
diff --git a/content/riak/kv/2.2.0/developing/usage/custom-extractors.md b/content/riak/kv/2.2.0/developing/usage/custom-extractors.md
index ec279957ed..fdc38e0594 100644
--- a/content/riak/kv/2.2.0/developing/usage/custom-extractors.md
+++ b/content/riak/kv/2.2.0/developing/usage/custom-extractors.md
@@ -15,8 +15,8 @@ aliases:
- /riak/kv/2.2.0/dev/search/custom-extractors
---
-Solr, and by extension Riak Search, has default extractors for a wide
-variety of data types, including JSON, XML, and plaintext. Riak Search
+Solr, and by extension Riak search, has default extractors for a wide
+variety of data types, including JSON, XML, and plaintext. Riak search
ships with the following extractors:
Content Type | Erlang Module
@@ -30,7 +30,7 @@ No specified type | `yz_noop_extractor`
There are also built-in extractors for [Riak Data Types](/riak/kv/2.2.0/developing/usage/searching-data-types).
If you're working with a data format that does not have a default Solr
-extractor, you can create your own and register it with Riak Search.
+extractor, you can create your own and register it with Riak search.
We'll show you how to do so by way of example.
## The Extractor Interface
@@ -195,7 +195,7 @@ extractor has been successfully registered.
## Verifying Our Custom Extractor
-Now that Riak Search knows how to decode and extract HTTP header packet
+Now that Riak search knows how to decode and extract HTTP header packet
data, let's store some in Riak and then query it. We'll put the example
packet data from above in a `google_packet.bin` file. Then, we'll `PUT`
that binary to Riak's `/search/extract` endpoint:
diff --git a/content/riak/kv/2.2.0/developing/usage/document-store.md b/content/riak/kv/2.2.0/developing/usage/document-store.md
index c14a0858e0..578c9a6e4f 100644
--- a/content/riak/kv/2.2.0/developing/usage/document-store.md
+++ b/content/riak/kv/2.2.0/developing/usage/document-store.md
@@ -16,18 +16,18 @@ aliases:
---
Although Riak wasn't explicitly created as a document store, two
-features recently added to Riak---[Riak Search](/riak/kv/2.2.0/developing/usage/search/) and [Riak Data Types](/riak/kv/2.2.0/developing/data-types/)---make it possible to use Riak as a
+features recently added to Riak---[Riak search](/riak/kv/2.2.0/developing/usage/search/) and [Riak Data Types](/riak/kv/2.2.0/developing/data-types/)---make it possible to use Riak as a
highly scalable document store with rich querying capabilities. In this
tutorial, we'll build a basic implementation of a document store using
[Riak maps](/riak/kv/2.2.0/developing/data-types/#maps).
## Basic Approach
-Riak Search enables you to implement a document store in Riak in a
+Riak search enables you to implement a document store in Riak in a
variety of ways. You could, for example, store and query JSON objects or
XML and then retrieve them later via Solr queries. In this tutorial,
however, we will store data in [Riak maps](/riak/kv/2.2.0/developing/data-types/#maps),
-index that data using Riak Search, and then run Solr queries against
+index that data using Riak search, and then run Solr queries against
those stored objects.
You can think of these Search indexes as **collections**. Each indexed
@@ -65,7 +65,7 @@ Date posted | Register | Datetime
Whether the post is currently in draft form | Flag | Boolean
Before we start actually creating and storing blog posts, let's set up
-Riak Search with an appropriate index and schema.
+Riak search with an appropriate index and schema.
## Creating a Schema and Index
@@ -209,7 +209,7 @@ curl -XPUT $RIAK_HOST/search/index/blog_posts \
Collections are not a concept that is native to Riak but we can easily
mimic collections by thinking of a bucket type as a collection. When we
-associate a bucket type with a Riak Search index, all of the objects
+associate a bucket type with a Riak search index, all of the objects
stored in any bucket of that bucket type will be queryable on the basis
of that one index. For this tutorial, we'll create a bucket type called
`cms` and think of that as a collection. We could also restrict our
diff --git a/content/riak/kv/2.2.0/developing/usage/search-schemas.md b/content/riak/kv/2.2.0/developing/usage/search-schemas.md
index 48344c673e..278587c811 100644
--- a/content/riak/kv/2.2.0/developing/usage/search-schemas.md
+++ b/content/riak/kv/2.2.0/developing/usage/search-schemas.md
@@ -19,21 +19,21 @@ aliases:
> **Note on Search 2.0 vs. Legacy Search**
>
-> This document refers to the new Riak Search 2.0 with
+> This document refers to the new Riak search 2.0 with
[Solr](http://lucene.apache.org/solr/) integration (codenamed
-Yokozuna). For information about the deprecated Riak Search, visit [the old Using Riak Search docs](http://docs.basho.com/riak/1.4.10/dev/using/search/).
+Yokozuna). For information about the deprecated Riak search, visit [the old Using Riak search docs](http://docs.basho.com/riak/1.4.10/dev/using/search/).
-Riak Search is built for ease of use, allowing you to write values into
-Riak and query for values using Solr. Riak Search does a lot of work
+Riak search is built for ease of use, allowing you to write values into
+Riak and query for values using Solr. Riak search does a lot of work
under the hood to convert your values---plain text, JSON, XML, [Riak Data Types](/riak/kv/2.2.0/developing/data-types/), and [more](/riak/kv/2.2.0/developing/usage/custom-extractors)---into something that can be indexed and searched later.
Nonetheless, you must still instruct Riak/Solr how to index a value. Are
you providing and array of strings? An integer? A date? Is your text in
-English or Russian? You can provide such instructions to Riak Search by
+English or Russian? You can provide such instructions to Riak search by
defining a Solr **schema**.
## The Default Schema
-Riak Search comes bundled with a default schema named `_yz_default`. The
+Riak search comes bundled with a default schema named `_yz_default`. The
default schema covers a wide range of possible field types. You can find
the default schema [on GitHub](https://raw.github.com/basho/yokozuna/develop/priv/default_schema.xml).
While using the default schema provides an easy path to starting
@@ -47,7 +47,7 @@ amounts of disk space, so pay special attention to those indexes.
We'll show you how you can create custom schemas by way of example.
Let's say that you have already created a schema named `cartoons` in a
file named `cartoons.xml`. This would register the custom schema in Riak
-Search:
+search:
```java
import org.apache.commons.io.FileUtils;
@@ -123,11 +123,11 @@ curl -XPUT http://localhost:8098/search/schema/cartoons \
The first step in creating a custom schema is to define exactly what
fields you must index. Part of that step is understanding how Riak
-Search extractors function.
+search extractors function.
### Extractors
-In Riak Search, extractors are modules responsible for pulling out a
+In Riak search, extractors are modules responsible for pulling out a
list of fields and values from a Riak object. How this is achieved
depends on the object's content type, but the two common cases are JSON
and XML, which operate similarly. Our examples here will use JSON.
@@ -175,21 +175,21 @@ Solr schemas can be very complex, containing many types and analyzers.
Refer to the [Solr 4.7 reference
guide](http://archive.apache.org/dist/lucene/solr/ref-guide/apache-solr-ref-guide-4.7.pdf)
for a complete list. You should be aware, however, that there are a few
-fields that are required by Riak Search in order to properly distribute
+fields that are required by Riak search in order to properly distribute
an object across a [cluster][concept clusters]. These fields are all prefixed
with `_yz`, which stands for
[Yokozuna](https://github.com/basho/yokozuna), the original code name
-for Riak Search.
+for Riak search.
Below is a bare minimum skeleton Solr Schema. It won't do much for you
-other than allow Riak Search to properly manage your stored objects.
+other than allow Riak search to properly manage your stored objects.
```xml
-
+
@@ -210,14 +210,14 @@ other than allow Riak Search to properly manage your stored objects.
```
-If you're missing any of the above fields, Riak Search will reject your
+If you're missing any of the above fields, Riak search will reject your
custom schema. The value for `` _must_ be `_yz_id`.
In the table below, you'll find a description of the various required
fields. You'll rarely need to use any fields other than `_yz_rt` (bucket
type), `_yz_rb` (bucket) and `_yz_rk` (Riak key). On occasion, `_yz_err`
can be helpful if you suspect that your extractors are failing.
-Malformed JSON or XML will cause Riak Search to index a key and set
+Malformed JSON or XML will cause Riak search to index a key and set
`_yz_err` to 1, allowing you to reindex with proper values later.
Field | Name | Description
@@ -262,7 +262,7 @@ field, you also must set `multiValued` to `true`.
-
+
diff --git a/content/riak/kv/2.2.0/developing/usage/search.md b/content/riak/kv/2.2.0/developing/usage/search.md
index 56b1c0f0d2..276f39c01f 100644
--- a/content/riak/kv/2.2.0/developing/usage/search.md
+++ b/content/riak/kv/2.2.0/developing/usage/search.md
@@ -29,7 +29,7 @@ to properly store and later query for values.
3. **Bucket-index association** signals to Riak *when* to index values
(this also includes bucket type-index association)
-Riak Search must first be configured with a Solr schema so that Solr
+Riak search must first be configured with a Solr schema so that Solr
knows how to index value fields. If you don't define one, you're
provided with a default schema named `_yz_default`, which can be found
[on
@@ -38,7 +38,7 @@ GitHub](https://raw.githubusercontent.com/basho/yokozuna/develop/priv/default_sc
The examples in this document will presume the default. You can read
more about creating custom schemas in [Search Schema][usage search schema], which you'll likely want to use in a production environment.
-Next, you must create a named Solr index through Riak Search. This index
+Next, you must create a named Solr index through Riak search. This index
represents a collection of similar data that you connect with to perform
queries. When creating an index, you can optionally provide a schema. If
you do not, the default schema will be used. Here we'll `curl` create an
@@ -246,7 +246,7 @@ More information can be found in the [Solr
documentation](http://wiki.apache.org/solr/SolrPerformanceFactors).
With a Solr schema, index, and association in place (and possibly a
-security setup as well), we're ready to start using Riak Search. First,
+security setup as well), we're ready to start using Riak search. First,
populate the `cat` bucket with values, in this case information about
four cats: Liono, Cheetara, Snarf, and Panthro.
@@ -495,12 +495,12 @@ curl -XPUT $RIAK_HOST/types/animals/buckets/cats/keys/panthro \
```
If you've used Riak before, you may have noticed that this is no
-different from storing values without Riak Search. That's because we
-designed Riak Search with the following design goal in mind:
+different from storing values without Riak search. That's because we
+designed Riak search with the following design goal in mind:
#### Write it like Riak, query it like Solr
-But how does Riak Search know how to index values, given that you can
+But how does Riak search know how to index values, given that you can
store opaque values in Riak? For that, we employ extractors.
## Extractors
@@ -510,7 +510,7 @@ content type and convert it into a list of fields that can be indexed by
Solr. This is done transparently and automatically as part of the
indexing process. You can even create your own [custom extractors](/riak/kv/2.2.0/developing/usage/custom-extractors).
-Our current example uses the JSON extractor, but Riak Search also
+Our current example uses the JSON extractor, but Riak search also
extracts indexable fields from the following content types:
* JSON (`application/json`)
@@ -560,7 +560,7 @@ one of the default types. A full tutorial can be found in [Custom Search Extract
### Automatic Fields
-When a Riak object is indexed, Riak Search automatically inserts a few
+When a Riak object is indexed, Riak search automatically inserts a few
extra fields as well. These are necessary for a variety of technical
reasons, and for the most part you don't need to think about them.
However, there are a few fields which you may find useful:
@@ -1248,7 +1248,7 @@ curl "$RIAK_HOST/search/query/famous?wt=json&q=*:*&start=$START&rows=$ROWS_PER_P
### Pagination Warning
-Distributed pagination in Riak Search cannot be used reliably when
+Distributed pagination in Riak search cannot be used reliably when
sorting on fields that can have different values per replica of the same
object, namely `score` and `_yz_id`. In the case of sorting by these
fields, you may receive redundant objects. In the case of `score`, the
@@ -1272,14 +1272,14 @@ fix this shortcoming in a future version of Riak.
### MapReduce
-Riak Search allows for piping search results as inputs for
+Riak search allows for piping search results as inputs for
[MapReduce](/riak/kv/2.2.0/developing/usage/mapreduce/) jobs. This is a useful cross-section for
performing post-calculations of results or aggregations of ad-hoc
-queries. The Riak Search MapReduce integration works similarly to
+queries. The Riak search MapReduce integration works similarly to
regular MapReduce, with the notable exception that your input is not a
bucket, but rather index and query arguments to the `yokozuna` module
and `mapred_search` function (an Erlang `module:function` pair that adds
-the Riak Search hook to MapReduce).
+the Riak search hook to MapReduce).
```json
{
diff --git a/content/riak/kv/2.2.0/developing/usage/secondary-indexes.md b/content/riak/kv/2.2.0/developing/usage/secondary-indexes.md
index e2c0320056..e61d0576d3 100644
--- a/content/riak/kv/2.2.0/developing/usage/secondary-indexes.md
+++ b/content/riak/kv/2.2.0/developing/usage/secondary-indexes.md
@@ -19,12 +19,12 @@ aliases:
[plan backend memory]: /riak/kv/2.2.0/setup/planning/backend/memory
[use ref strong consistency]: /riak/kv/2.2.0/using/reference/strong-consistency
-> **Note: Riak Search preferred for querying**
+> **Note: Riak search preferred for querying**
>
> If you're interested in non-primary-key-based querying in Riak, i.e. if
you're looking to go beyond straightforward K/V operations, we now
-recommend [Riak Search](/riak/kv/2.2.0/developing/usage/search/) rather than secondary indexes for
-a variety of reasons. Most importantly, Riak Search has a far more
+recommend [Riak search](/riak/kv/2.2.0/developing/usage/search/) rather than secondary indexes for
+a variety of reasons. Most importantly, Riak search has a far more
capacious querying API and can be used with all of Riak's storage
backends.
@@ -37,7 +37,7 @@ Secondary indexes can be either a binary or string, such as
`sensor_1_data` or `admin_user` or `click_event`, or an integer, such as
`99` or `141121`.
-[Riak Search](/riak/kv/2.2.0/developing/usage/search/) serves analogous purposes but is quite
+[Riak search](/riak/kv/2.2.0/developing/usage/search/) serves analogous purposes but is quite
different because it parses key/value data itself and builds indexes on
the basis of Solr schemas.
@@ -75,7 +75,7 @@ you to discover them later. Indexing enables you to tag those objects
and find all objects with the same tag in a specified bucket later on.
2i is thus recommended when your use case requires an easy-to-use search
-mechanism that does not require a schema (as does [Riak Search](/riak/kv/2.2.0/using/reference/search/#schemas)) and a basic query interface, i.e. an interface that
+mechanism that does not require a schema (as does [Riak search](/riak/kv/2.2.0/using/reference/search/#schemas)) and a basic query interface, i.e. an interface that
enables an application to tell Riak things like "fetch all objects
tagged with the string `Milwaukee_Bucks`" or "fetch all objects tagged
with numbers between 1500 and 1509."
@@ -89,7 +89,7 @@ piggybacks off of read-repair.
* If your ring size exceeds 512 partitions, 2i can cause performance
issues in large clusters.
* When you need more than the exact match and range searches that 2i
- supports. If that's the case, we recommend checking out [Riak Search](/riak/kv/2.2.0/developing/usage/search/).
+ supports. If that's the case, we recommend checking out [Riak search](/riak/kv/2.2.0/developing/usage/search/).
* When you want to use composite queries. A query like
`last_name=zezeski AND state=MD` would have to be split into two
queries and the results merged (or it would need to involve
diff --git a/content/riak/kv/2.2.0/learn/concepts/strong-consistency.md b/content/riak/kv/2.2.0/learn/concepts/strong-consistency.md
index 704df76ba4..c85140ebc6 100644
--- a/content/riak/kv/2.2.0/learn/concepts/strong-consistency.md
+++ b/content/riak/kv/2.2.0/learn/concepts/strong-consistency.md
@@ -20,7 +20,7 @@ aliases:
Please Note:
-Riak KV's strong consistency is an experimental feature and may be removed from the product in the future. Strong consistency is not commercially supported or production-ready. Strong consistency is incompatible with Multi-Datacenter Replication, Riak Search, Bitcask Expiration, LevelDB Secondary Indexes, Riak Data Types and Commit Hooks. We do not recommend its usage in any production environment.
+Riak KV's strong consistency is an experimental feature and may be removed from the product in the future. Strong consistency is not commercially supported or production-ready. Strong consistency is incompatible with Multi-Datacenter Replication, Riak search, Bitcask Expiration, LevelDB Secondary Indexes, Riak Data Types and Commit Hooks. We do not recommend its usage in any production environment.
Riak was originally designed as an [eventually consistent](/riak/kv/2.2.0/learn/concepts/eventual-consistency) system, fundamentally geared toward providing partition
diff --git a/content/riak/kv/2.2.0/learn/glossary.md b/content/riak/kv/2.2.0/learn/glossary.md
index 8589eced53..070695dc58 100644
--- a/content/riak/kv/2.2.0/learn/glossary.md
+++ b/content/riak/kv/2.2.0/learn/glossary.md
@@ -275,7 +275,7 @@ best described as "UNIX pipes for Riak."
## Riak Search
-Riak Search is a distributed, scalable, failure-tolerant, realtime,
+Riak search is a distributed, scalable, failure-tolerant, realtime,
full-text search engine integrating [Apache
Solr](https://lucene.apache.org/solr/) with Riak KV.
diff --git a/content/riak/kv/2.2.0/learn/use-cases.md b/content/riak/kv/2.2.0/learn/use-cases.md
index 04b47889b4..861d94c845 100644
--- a/content/riak/kv/2.2.0/learn/use-cases.md
+++ b/content/riak/kv/2.2.0/learn/use-cases.md
@@ -153,7 +153,7 @@ For storing log data from different systems, you could use unique
buckets for each system (e.g. `system1_log_data`, `system2_log_data`,
etc.) and write associated logs to the corresponding buckets. To
analyze that data, you could use Riak's MapReduce system for aggregation
-tasks, such as summing the counts of records for a date or Riak Search
+tasks, such as summing the counts of records for a date or Riak search
for a more robust, text-based queries.
### Log Data Complex Case
@@ -237,7 +237,7 @@ For simple retrieval of a specific account, a user ID (plus perhaps a
secondary index on a username or email) is enough. If you foresee the
need to make queries on additional user attributes (e.g. creation time,
user type, or region), plan ahead and either set up additional secondary
-indexes or consider using [Riak Search][usage search] to index the JSON
+indexes or consider using [Riak search][usage search] to index the JSON
contents of the user account.
### User Accounts Community Examples
@@ -323,7 +323,7 @@ In Riak, you can store content of any kind, from HTML files to plain
text to JSON or XML or another document type entirely. Keep in mind that
data in Riak is opaque, with the exception of [Riak Data Types](/riak/kv/2.2.0/developing/data-types),
and so Riak won't "know" about the object unless it is indexed
-[using Riak Search][usage search] or [using secondary indexes][usage secondary-indexes].
+[using Riak search][usage search] or [using secondary indexes][usage secondary-indexes].
### Articles et al Complex Case
@@ -342,7 +342,7 @@ with comments would require your application to call from the posts
and comments buckets to assemble the view.
Other possible cases may involve performing operations on content beyond
-key/value pairs. [Riak Search][usage search] is recommended for use cases
+key/value pairs. [Riak search][usage search] is recommended for use cases
involving full-text search. For lighter-weight querying,
[using secondary indexes][usage secondary-indexes] \(2i) enables you to add metadata to objects to
either query for exact matches or to perform range queries. 2i also
diff --git a/content/riak/kv/2.2.0/release-notes.md b/content/riak/kv/2.2.0/release-notes.md
index 31ce1fadf4..2810d39d25 100644
--- a/content/riak/kv/2.2.0/release-notes.md
+++ b/content/riak/kv/2.2.0/release-notes.md
@@ -44,7 +44,7 @@ AAE trees are versioned, so if you choose to enable the 2.2.0 AAE improvements,
## Downgrading
-### Riak search users
+### Riak Search users
The upgrade to Solr 4.10.4 causes new data written to the cluster to be written in a format that is incompatible with earlier versions of Solr (and, therefore, earlier versions of Riak KV). The [Upgrade](/riak/kv/2.2.0/setup/upgrading/version/) and [Downgrade](/riak/kv/2.2.0/setup/downgrade/) documentation describes the steps you will need to take to reindex your data in a rolling fashion. Be aware this can make downgrades take a very long time, but will minimize exposure of the downgrading nodes to applications that utilize the Riak search feature.
diff --git a/content/riak/kv/2.2.0/setup/downgrade.md b/content/riak/kv/2.2.0/setup/downgrade.md
index 2aaf6c0679..75ea33492d 100644
--- a/content/riak/kv/2.2.0/setup/downgrade.md
+++ b/content/riak/kv/2.2.0/setup/downgrade.md
@@ -31,7 +31,7 @@ For every node in the cluster:
1. Stop Riak KV.
2. Back up Riak's `etc` and `data` directories.
3. Downgrade the Riak KV.
-4. Remove Riak Search index and temporary data.
+4. Remove Riak search index and temporary data.
5. Reconfigure Solr cores.
6. Start Riak KV and disable Riak search.
7. Monitor the reindex of the data.
@@ -47,7 +47,7 @@ For every node in the cluster:
| Feature | automatic | required | Notes |
|:---|:---:|:---:|:---|
-|Migration to Solr 4.10.4 |✔ | ✔| Applies to all clusters using Riak Search.
+|Migration to Solr 4.10.4 |✔ | ✔| Applies to all clusters using Riak search.
| Active Anti-Entropy file format changes | ✔ | | Can be opted out using a [capability](#aae_tree_capability)
@@ -65,7 +65,7 @@ While the cluster contains mixed version members, if you have not set the cluste
This is benign and similar to the `not_built` and `already_locked` errors which can be seen during normal AAE operation. These events will stop once the downgrade is complete.
{{% /note %}}
-### Stop Riak KV and remove Riak search index & temporary data
+### Stop Riak KV and remove Riak Search index & temporary data
1\. Stop Riak KV:
@@ -133,7 +133,7 @@ riak-admin wait-for-service yokozuna
8\. Run `riak attach`.
- 1. Run the following snippet to prevent this node from participating in distributed Riak Search queries:
+ 1. Run the following snippet to prevent this node from participating in distributed Riak search queries:
```
riak_core_node_watcher:service_down(yokozuna).
diff --git a/content/riak/kv/2.2.0/setup/installing/source/jvm.md b/content/riak/kv/2.2.0/setup/installing/source/jvm.md
index b38756a893..afb2156780 100644
--- a/content/riak/kv/2.2.0/setup/installing/source/jvm.md
+++ b/content/riak/kv/2.2.0/setup/installing/source/jvm.md
@@ -21,10 +21,10 @@ aliases:
[usage search]: /riak/kv/2.2.0/developing/usage/search
-If you are using [Riak Search 2.0][usage search], codename Yokozuna,
+If you are using [Riak search 2.0][usage search], codename Yokozuna,
you will need to install **Java 1.6 or later** to run [Apache
Solr](https://lucene.apache.org/solr/), the search platform that powers
-Riak Search.
+Riak search.
We recommend using Oracle's [JDK
7u25](http://www.oracle.com/technetwork/java/javase/7u25-relnotes-1955741.html).
@@ -35,7 +35,7 @@ page](http://www.oracle.com/technetwork/java/javase/documentation/index.html).
## Installing Solr on OS X
-If you're using Riak Search on Mac OS X, you may see the following
+If you're using Riak search on Mac OS X, you may see the following
error:
```java
diff --git a/content/riak/kv/2.2.0/setup/planning/backend/bitcask.md b/content/riak/kv/2.2.0/setup/planning/backend/bitcask.md
index b4467781d4..6da678c645 100644
--- a/content/riak/kv/2.2.0/setup/planning/backend/bitcask.md
+++ b/content/riak/kv/2.2.0/setup/planning/backend/bitcask.md
@@ -751,7 +751,7 @@ bitcask.expiry.grace_time = 1h
#### Automatic expiration and Riak Search
-If you are using [Riak Search][usage search] in conjunction with
+If you are using [Riak search][usage search] in conjunction with
Bitcask, please be aware that automatic expiry does not apply to [Search Indexes](../../../../developing/usage/search). If objects are indexed using Search,
those objects can be expired by Bitcask yet still registered in Search
indexes, which means that Search queries may return keys that no longer
diff --git a/content/riak/kv/2.2.0/setup/upgrading/checklist.md b/content/riak/kv/2.2.0/setup/upgrading/checklist.md
index 1638650a31..79937f43a0 100644
--- a/content/riak/kv/2.2.0/setup/upgrading/checklist.md
+++ b/content/riak/kv/2.2.0/setup/upgrading/checklist.md
@@ -88,7 +88,7 @@ We've compiled these considerations and questions into separate categories for y
place if `allow_mult` is set to `true`?
- Have you carefully weighed the [consistency trade-offs][concept eventual consistency] that must be made if `allow_mult` is set to `false`?
- Are all of your [apps replication properties][apps replication properties] configured correctly and uniformly across the cluster?
- - If you are using [Riak Search][usage search], is it enabled on all
+ - If you are using [Riak search][usage search], is it enabled on all
nodes? If you are not, has it been disabled on all nodes?
- If you are using [strong consistency][concept strong consistency] for some or all of your
data:
diff --git a/content/riak/kv/2.2.0/using/admin/riak-admin.md b/content/riak/kv/2.2.0/using/admin/riak-admin.md
index 144e773ba1..b88c65471d 100644
--- a/content/riak/kv/2.2.0/using/admin/riak-admin.md
+++ b/content/riak/kv/2.2.0/using/admin/riak-admin.md
@@ -585,7 +585,7 @@ riak-admin repair-2i kill
## search
The search command provides sub-commands for various administrative
-work related to the new Riak Search.
+work related to the new Riak search.
```bash
riak-admin search
@@ -634,7 +634,7 @@ riak-admin search switch-to-new-search
```
Switch handling of the HTTP `/solr//select` resource and
-protocol buffer query messages from legacy Riak Search to new Search
+protocol buffer query messages from legacy Riak search to new Search
(Yokozuna).
## services
diff --git a/content/riak/kv/2.2.0/using/cluster-operations/active-anti-entropy.md b/content/riak/kv/2.2.0/using/cluster-operations/active-anti-entropy.md
index 47dfd4d023..705af76dc3 100644
--- a/content/riak/kv/2.2.0/using/cluster-operations/active-anti-entropy.md
+++ b/content/riak/kv/2.2.0/using/cluster-operations/active-anti-entropy.md
@@ -265,9 +265,9 @@ AAE-related background tasks, analogous to [open files limit](../../performance/
## AAE and Riak Search
Riak's AAE subsystem works to repair object inconsistencies both with
-for normal key/value objects as well as data related to [Riak Search](../../../developing/usage/search). In particular, AAE acts on indexes stored in
+for normal key/value objects as well as data related to [Riak search](../../../developing/usage/search). In particular, AAE acts on indexes stored in
[Solr](http://lucene.apache.org/solr/), the search platform that drives
-Riak Search. Implementation details for AAE and Search can be found in
+Riak search. Implementation details for AAE and Search can be found in
the [Search Details](../../reference/search/#active-anti-entropy-aae)
documentation.
diff --git a/content/riak/kv/2.2.0/using/cluster-operations/inspecting-node.md b/content/riak/kv/2.2.0/using/cluster-operations/inspecting-node.md
index e119f92188..ec097f33a3 100644
--- a/content/riak/kv/2.2.0/using/cluster-operations/inspecting-node.md
+++ b/content/riak/kv/2.2.0/using/cluster-operations/inspecting-node.md
@@ -297,7 +297,7 @@ Stat | Description
`erlydtl_version` | [ErlyDTL](http://github.com/erlydtl/erlydtl)
`riak_control_version` | [Riak Control](http://github.com/basho/riak_control)
`cluster_info_version` | [Cluster Information](http://github.com/basho/cluster_info)
-`riak_search_version` | [Riak Search](http://github.com/basho/riak_search)
+`riak_search_version` | [Riak search](http://github.com/basho/riak_search)
`merge_index_version` | [Merge Index](http://github.com/basho/merge_index)
`riak_kv_version` | [Riak KV](http://github.com/basho/riak_kv)
`sidejob_version` | [Sidejob](http://github.com/basho/sidejob)
@@ -326,17 +326,17 @@ Stat | Description
### Riak Search Statistics
-The following statistics related to Riak Search message queues are
+The following statistics related to Riak search message queues are
available.
Stat | Description
-----------------------------|---------------------------------------------------
-`riak_search_vnodeq_max` | Maximum number of unprocessed messages all virtual node (vnode) message queues in the Riak Search subsystem have received on this node in the last minute
-`riak_search_vnodeq_mean` | Mean number of unprocessed messages all vnode message queues in the Riak Search subsystem have received on this node in the last minute
-`riak_search_vnodeq_median` | Median number of unprocessed messages all vnode message queues in the Riak Search subsystem have received on this node in the last minute
-`riak_search_vnodeq_min` | Minimum number of unprocessed messages all vnode message queues in the Riak Search subsystem have received on this node in the last minute
-`riak_search_vnodeq_total` | Total number of unprocessed messages all vnode message queues in the Riak Search subsystem have received on this node since it was started
-`riak_search_vnodes_running` | Total number of vnodes currently running in the Riak Search subsystem
+`riak_search_vnodeq_max` | Maximum number of unprocessed messages all virtual node (vnode) message queues in the Riak search subsystem have received on this node in the last minute
+`riak_search_vnodeq_mean` | Mean number of unprocessed messages all vnode message queues in the Riak search subsystem have received on this node in the last minute
+`riak_search_vnodeq_median` | Median number of unprocessed messages all vnode message queues in the Riak search subsystem have received on this node in the last minute
+`riak_search_vnodeq_min` | Minimum number of unprocessed messages all vnode message queues in the Riak search subsystem have received on this node in the last minute
+`riak_search_vnodeq_total` | Total number of unprocessed messages all vnode message queues in the Riak search subsystem have received on this node since it was started
+`riak_search_vnodes_running` | Total number of vnodes currently running in the Riak search subsystem
Note that under ideal operation and with the exception of
`riak_search_vnodes_running` these statistics should contain low values
@@ -449,7 +449,7 @@ Check | Description
`ring_membership` | Cluster membership validity
`ring_preflists` | Check if the ring satisfies `n_val`
`ring_size` | Check if the ring size valid
-`search` | Check whether Riak Search is enabled on all nodes
+`search` | Check whether Riak search is enabled on all nodes
The `--level` flag enables you to specify the log level and thus to
filter messages based on type. You can pass in any of the message types
diff --git a/content/riak/kv/2.2.0/using/cluster-operations/strong-consistency.md b/content/riak/kv/2.2.0/using/cluster-operations/strong-consistency.md
index f584539791..4bae97c6e7 100644
--- a/content/riak/kv/2.2.0/using/cluster-operations/strong-consistency.md
+++ b/content/riak/kv/2.2.0/using/cluster-operations/strong-consistency.md
@@ -14,7 +14,7 @@ toc: true
Please Note:
-Riak KV's strong consistency is an experimental feature and may be removed from the product in the future. Strong consistency is not commercially supported or production-ready. Strong consistency is incompatible with Multi-Datacenter Replication, Riak Search, Bitcask Expiration, LevelDB Secondary Indexes, Riak Data Types and Commit Hooks. We do not recommend its usage in any production environment.
+Riak KV's strong consistency is an experimental feature and may be removed from the product in the future. Strong consistency is not commercially supported or production-ready. Strong consistency is incompatible with Multi-Datacenter Replication, Riak search, Bitcask Expiration, LevelDB Secondary Indexes, Riak Data Types and Commit Hooks. We do not recommend its usage in any production environment.
## Monitoring Strong Consistency
diff --git a/content/riak/kv/2.2.0/using/reference/handoff.md b/content/riak/kv/2.2.0/using/reference/handoff.md
index 82e7b4e7cf..4839618e27 100644
--- a/content/riak/kv/2.2.0/using/reference/handoff.md
+++ b/content/riak/kv/2.2.0/using/reference/handoff.md
@@ -121,7 +121,7 @@ handoff.use_background_manager = on
### Maximum Rejects
-If you're using Riak features such as [Riak Search](/riak/kv/2.2.0/developing/usage/search/),
+If you're using Riak features such as [Riak search](/riak/kv/2.2.0/developing/usage/search/),
those subsystems can block handoff of primary key/value data, i.e. data
that you interact with via normal reads and writes.
diff --git a/content/riak/kv/2.2.0/using/reference/search.md b/content/riak/kv/2.2.0/using/reference/search.md
index a6e66351a4..88b154c8b4 100644
--- a/content/riak/kv/2.2.0/using/reference/search.md
+++ b/content/riak/kv/2.2.0/using/reference/search.md
@@ -36,30 +36,30 @@ search, you should check out the [Using Search](/riak/kv/2.2.0/developing/usage/
In Erlang OTP, an "application" is a group of modules and Erlang
processes which together perform a specific task. The word application
is confusing because most people think of an application as an entire
-program such as Emacs or Photoshop. But Riak Search is just a sub-system
+program such as Emacs or Photoshop. But Riak search is just a sub-system
in Riak itself. Erlang applications are often stand-alone, but Riak
-Search is more like an appendage of Riak. It requires other subsystems
+search is more like an appendage of Riak. It requires other subsystems
like Riak Core and KV, but also extends their functionality by providing
search capabilities for KV data.
-The purpose of Riak Search is to bring more sophisticated and robust
+The purpose of Riak search is to bring more sophisticated and robust
query and search support to Riak. Many people consider Lucene and
programs built on top of it, such as Solr, as the standard for
open-source search. There are many successful applications built on
Lucene/Solr, and it sets the standard for the feature set that
developers and users expect. Meanwhile, Riak has a great story as a
-highly-available, distributed key/value store. Riak Search takes
+highly-available, distributed key/value store. Riak search takes
advantage of the fact that Riak already knows how to do the distributed
bits, combining its feature set with that of Solr, taking advantage of
the strengths of each.
-Riak Search is a mediator between Riak and Solr. There is nothing
+Riak search is a mediator between Riak and Solr. There is nothing
stopping a user from deploying these two programs separately, but this
would leave the user responsible for the glue between them. That glue
can be tricky to write. It requires dealing with monitoring, querying,
indexing, and dissemination of information.
-Unlike Solr by itself, Riak Search knows how to do all of the following:
+Unlike Solr by itself, Riak search knows how to do all of the following:
* Listen for changes in key/value (KV) data and to make the appropriate
changes to indexes that live in Solr. It also knows how to take a user
@@ -76,13 +76,13 @@ system (OS) process running a JVM which hosts Solr on the Jetty
application server. This OS process is a child of the Erlang OS process
running Riak.
-Riak Search has a `gen_server` process which monitors the JVM OS
+Riak search has a `gen_server` process which monitors the JVM OS
process. The code for this server is in `yz_solr_proc`. When the JVM
process crashes, this server crashes, causing its supervisor to restart
it.
If there is more than 1 restart in 45 seconds, the entire Riak node will
-be shut down. If Riak Search is enabled and Solr cannot function for
+be shut down. If Riak search is enabled and Solr cannot function for
some reason, the Riak node needs to go down so that the user will notice
and take corrective action.
@@ -92,7 +92,7 @@ This double monitoring along with the crash semantics means that neither
process may exist without the other. They are either both up or both
down.
-All other communication between Riak Search and Solr is performed via
+All other communication between Riak search and Solr is performed via
HTTP, including querying, indexing, and administration commands. The
ibrowse Erlang HTTP client is used to manage these communications as
both it and the Jetty container hosting Solr pool HTTP connections,
@@ -106,11 +106,11 @@ contains index entries for objects. Each such index maintains its own
set of files on disk---a critical difference from Riak KV, in which a
bucket is a purely logical entity and not physically disjoint at all. A
Solr index requires significantly less disk space than the corresponding
-legacy Riak Search index, depending on the Solr schema used.
+legacy Riak search index, depending on the Solr schema used.
Indexes may be associated with zero or more buckets. At creation time,
however, each index has no associated buckets---unlike the legacy Riak
-Search, indexes in the new Riak Search do not implicitly create bucket
+search, indexes in the new Riak search do not implicitly create bucket
associations, meaning that this must be done as a separate configuration
step.
@@ -142,7 +142,7 @@ flat collection of field-value pairs. "Flat" here means that a field's
value cannot be a nested structure of field-value pairs; the values are
treated as-is (non-composite is another way to say it).
-Because of this mismatch between KV and Solr, Riak Search must act as a
+Because of this mismatch between KV and Solr, Riak search must act as a
mediator between the two, meaning it must have a way to inspect a KV
object and create a structure which Solr can ingest for indexing. In
Solr this structure is called a **document**. This task of creating a
@@ -405,7 +405,7 @@ one with a smaller window.
## Statistics
-The Riak Search batching subsystem provides statistics on run-time characteristics of search system components. These statistics are accessible via the standard Riak KV stats interfaces and can be monitored through standard enterprise management tools.
+The Riak search batching subsystem provides statistics on run-time characteristics of search system components. These statistics are accessible via the standard Riak KV stats interfaces and can be monitored through standard enterprise management tools.
* `search_index_throughput_(count|one)` - The total count of objects that have been indexed, per Riak node, and the count of objects that have been indexed within the metric measurement window.
diff --git a/content/riak/kv/2.2.0/using/reference/secondary-indexes.md b/content/riak/kv/2.2.0/using/reference/secondary-indexes.md
index 8d29018d4c..40c5f492c1 100644
--- a/content/riak/kv/2.2.0/using/reference/secondary-indexes.md
+++ b/content/riak/kv/2.2.0/using/reference/secondary-indexes.md
@@ -18,11 +18,11 @@ aliases:
[usage bucket types]: /riak/kv/2.2.0/developing/usage/bucket-types
[use ref strong consistency]: /riak/kv/2.2.0/using/reference/strong-consistency
-> **Note: Riak Search preferred for querying**
+> **Note: Riak search preferred for querying**
>
> If you're interested in non-primary-key-based querying in Riak, i.e. if
you're looking to go beyond straightforward K/V operations, we now
-recommend [Riak Search](/riak/kv/2.2.0/developing/usage/search/) rather than secondary indexes for a variety of reasons. Riak Search has a far more capacious querying API and can be used with all of Riak's storage backends.
+recommend [Riak search](/riak/kv/2.2.0/developing/usage/search/) rather than secondary indexes for a variety of reasons. Riak search has a far more capacious querying API and can be used with all of Riak's storage backends.
This document provides implementation and other details for Riak's
[secondary indexes](/riak/kv/2.2.0/developing/usage/secondary-indexes/) \(2i) feature.
diff --git a/content/riak/kv/2.2.0/using/reference/statistics-monitoring.md b/content/riak/kv/2.2.0/using/reference/statistics-monitoring.md
index a5d337b191..b747e91e85 100644
--- a/content/riak/kv/2.2.0/using/reference/statistics-monitoring.md
+++ b/content/riak/kv/2.2.0/using/reference/statistics-monitoring.md
@@ -134,7 +134,7 @@ Metric | Also | Notes
:------|:-----|:------------------
```node_get_fsm_siblings_mean``` | ```_median```, ```_95```, ```_99```, ```_100``` | Number of siblings encountered during all GET operations by this node within the last minute. Watch for abnormally high sibling counts, especially max ones.
```node_get_fsm_objsize_mean``` | ```_median```, ```_95```, ```_99```, ```_100``` | Object size encountered by this node within the last minute. Abnormally large objects (especially paired with high sibling counts) can indicate sibling explosion.
-```riak_search_vnodeq_mean``` | ```_median```, ```_95```, ```_99```, ```_100``` | Number of unprocessed messages in the vnode message queues of the Riak Search subsystem on this node in the last minute. The queues give you an idea of how backed up Solr is getting.
+```riak_search_vnodeq_mean``` | ```_median```, ```_95```, ```_99```, ```_100``` | Number of unprocessed messages in the vnode message queues of the Riak search subsystem on this node in the last minute. The queues give you an idea of how backed up Solr is getting.
```search_index_fail_one``` | | Number of "Failed to index document" errors Search encountered for the last minute
```pbc_active``` | | Number of currently active protocol buffer connections
```pbc_connects``` | | Number of new protocol buffer connections established during the last minute
diff --git a/content/riak/kv/2.2.0/using/repair-recovery/errors.md b/content/riak/kv/2.2.0/using/repair-recovery/errors.md
index 3380d878d9..db08a36a60 100644
--- a/content/riak/kv/2.2.0/using/repair-recovery/errors.md
+++ b/content/riak/kv/2.2.0/using/repair-recovery/errors.md
@@ -328,7 +328,7 @@ exit with reason bad return value: {error,eaddrinuse} in context start_error | A
exited with reason: eaddrnotavail in gen_server:init_it/6 line 320 | An error like this example can result when Riak cannot bind to the addresses specified in the configuration. In this case, you should verify HTTP and Protocol Buffers addresses in `app.config` and ensure that the ports being used are not in the privileged (1-1024) range as the `riak` user will not have access to such ports.
gen_server riak_core_capability terminated with reason: no function clause matching orddict:fetch('riak@192.168.2.2', []) line 72 | Error output like this example can indicate that a previously running Riak node with an original `-name` value in `vm.args` has been modified by simply changing the value in `vm.args` and not properly through `riak-admin cluster replace`.
** Configuration error: [FRAMEWORK-MIB]: missing context.conf file => generating a default file | This error is commonly encountered when starting Riak Enterprise without prior [SNMP](/riak/kv/2.2.0/using/reference/snmp) configuration.
-RPC to 'node@example.com' failed: {'EXIT', {badarg, [{ets,lookup, [schema_table,<<"search-example">>], []} {riak_search_config,get_schema,1, [{file,"src/riak_search_config.erl"}, {line,69}]} ...| This error can be caused when attempting to use Riak Search without first enabling it in each node's `app.config`. See the [configuration files][config reference] documentation for more information on enabling Riak Search.
+RPC to 'node@example.com' failed: {'EXIT', {badarg, [{ets,lookup, [schema_table,<<"search-example">>], []} {riak_search_config,get_schema,1, [{file,"src/riak_search_config.erl"}, {line,69}]} ...| This error can be caused when attempting to use Riak search without first enabling it in each node's `app.config`. See the [configuration files][config reference] documentation for more information on enabling Riak search.
### More
diff --git a/content/riak/kv/2.2.0/using/repair-recovery/repairs.md b/content/riak/kv/2.2.0/using/repair-recovery/repairs.md
index 48c8d254b5..d920ae2f2e 100644
--- a/content/riak/kv/2.2.0/using/repair-recovery/repairs.md
+++ b/content/riak/kv/2.2.0/using/repair-recovery/repairs.md
@@ -57,7 +57,7 @@ riak-admin repair-2i kill
## Repairing Search Indexes
-Riak Search indexes currently have no form of anti-entropy (such as read-repair). Furthermore, for performance and load balancing reasons, Search reads from one random node. This means that when a replica loss has occurred, inconsistent results may be returned.
+Riak search indexes currently have no form of anti-entropy (such as read-repair). Furthermore, for performance and load balancing reasons, Search reads from one random node. This means that when a replica loss has occurred, inconsistent results may be returned.
### Running a Repair
diff --git a/content/riak/kv/2.2.0/using/repair-recovery/secondary-indexes.md b/content/riak/kv/2.2.0/using/repair-recovery/secondary-indexes.md
index 170cdf9df3..47c251a2ec 100644
--- a/content/riak/kv/2.2.0/using/repair-recovery/secondary-indexes.md
+++ b/content/riak/kv/2.2.0/using/repair-recovery/secondary-indexes.md
@@ -51,7 +51,7 @@ riak-admin repair-2i kill
## Repairing Search Indexes
-Riak Search indexes currently have no form of anti-entropy (such as read-repair). Furthermore, for performance and load balancing reasons, Search reads from one random node. This means that when a replica loss has occurred, inconsistent results may be returned.
+Riak search indexes currently have no form of anti-entropy (such as read-repair). Furthermore, for performance and load balancing reasons, Search reads from one random node. This means that when a replica loss has occurred, inconsistent results may be returned.
### Running a Repair
diff --git a/content/riak/kv/2.2.0/using/security/basics.md b/content/riak/kv/2.2.0/using/security/basics.md
index d5eeed7158..9a9c1da1ed 100644
--- a/content/riak/kv/2.2.0/using/security/basics.md
+++ b/content/riak/kv/2.2.0/using/security/basics.md
@@ -44,7 +44,7 @@ when turning on Riak security. Missing one of these steps will almost
certainly break your application, so make sure that you have done each
of the following **before** enabling security:
-1. Make certain that the original Riak Search (version 1) and link
+1. Make certain that the original Riak search (version 1) and link
walking are not required. Enabling security will break this
functionality. If you wish to use security and Search together, you
will need to use the [new Search feature](/riak/kv/2.2.0/developing/usage/search/).
@@ -487,11 +487,11 @@ Permission | Operation
### Search Query Permission (Riak Search version 1)
Security is incompatible with the original (and now deprecated) Riak
-Search. Riak Search version 1 will stop working if security is enabled.
+search. Riak search version 1 will stop working if security is enabled.
### Search Query Permissions (Riak Search version 2, aka Yokozuna)
-If you are using the new Riak Search, i.e. the Solr-compatible search
+If you are using the new Riak search, i.e. the Solr-compatible search
capabilities included with Riak versions 2.0 and greater, the following
search-related permissions can be granted/revoked:
@@ -508,8 +508,8 @@ disabled, you will get the following error:
>
> `{error,{unknown_permission,"search.query"}}`
>
-> More information on Riak Search and how to enable it can be found in the
-[Riak Search Settings](/riak/kv/2.2.0/configuring/search/) document.
+> More information on Riak search and how to enable it can be found in the
+[Riak search Settings](/riak/kv/2.2.0/configuring/search/) document.
#### Usage Examples
diff --git a/content/riak/ts/1.0.0/releasenotes.md b/content/riak/ts/1.0.0/releasenotes.md
index e9a052a73c..01d14b0bbe 100644
--- a/content/riak/ts/1.0.0/releasenotes.md
+++ b/content/riak/ts/1.0.0/releasenotes.md
@@ -63,7 +63,7 @@ Riak TS is compatible with the following operating systems:
## Known Issues
* AAE must be turned off.
-* Riak Search is not supported.
+* Riak search is not supported.
* Multi-Datacenter Replication is not supported.
* When deleting, a PUT occurs to write the tombstone, then a GET reaps the tombstone. Since PUT and GET are asynchronous, it is possible for the GET to occur before the PUT resulting in the data not actually being deleted. If this occurs, issue the DELETE again.
* It is possible to write incorrect data (data that does not match the schema) into rows other than the first row. For instance, it is possible to input an integer for 'double'. In these cases, the write will succeed but any READ or query that includes the incorrect row will fail.
\ No newline at end of file
diff --git a/content/riak/ts/1.1.0/releasenotes.md b/content/riak/ts/1.1.0/releasenotes.md
index 134e8a6bb5..2cfe917265 100644
--- a/content/riak/ts/1.1.0/releasenotes.md
+++ b/content/riak/ts/1.1.0/releasenotes.md
@@ -116,6 +116,6 @@ Riak TS is compatible with the following operating systems:
## Known Issues
* AAE must be turned off.
-* Riak Search is not supported.
+* Riak search is not supported.
* Multi-Datacenter Replication is not supported.
* Arithmetic operations and aggregates cannot currently be combined.
diff --git a/content/riak/ts/1.2.0/releasenotes.md b/content/riak/ts/1.2.0/releasenotes.md
index fccdd3a4d9..e90684178c 100644
--- a/content/riak/ts/1.2.0/releasenotes.md
+++ b/content/riak/ts/1.2.0/releasenotes.md
@@ -56,5 +56,5 @@ Riak TS is compatible with the following operating systems:
* Negation of an aggregate function returns an error. You can use negation by structuring any aggregate you'd like to negate as follows: `-1*COUNT(...)`.
* Rolling upgrades are not supported.
* AAE must be turned off.
-* Riak Search is not supported.
+* Riak search is not supported.
* Multi-Datacenter Replication is not supported.
\ No newline at end of file
diff --git a/content/riak/ts/1.3.0/releasenotes.md b/content/riak/ts/1.3.0/releasenotes.md
index 173155287c..560867ae27 100644
--- a/content/riak/ts/1.3.0/releasenotes.md
+++ b/content/riak/ts/1.3.0/releasenotes.md
@@ -92,6 +92,6 @@ Riak TS is compatible with the following:
## Known Issues
* AAE must be turned off.
-* Riak Search is not supported for TS data.
+* Riak search is not supported for TS data.
* HTTP API security is not supported. Security checks are included in the code path, but the permissions are not registered with riak_core, so enabling security means disabling any TS functionality. [[code](https://github.com/basho/riak_kv/blob/riak_ts-develop/src/riak_kv_app.erl#L214-L215)]
* Quanta with a '0' or negative integers are not supported and will cause errors.
diff --git a/content/riak/ts/1.3.0/using/querying.md b/content/riak/ts/1.3.0/using/querying.md
index 8a0f83063b..9cd4fa2731 100644
--- a/content/riak/ts/1.3.0/using/querying.md
+++ b/content/riak/ts/1.3.0/using/querying.md
@@ -324,7 +324,7 @@ The following operators are supported for each data type:
* Column to column comparisons are not currently supported.
* Secondary indexing (2i) will not work with Riak TS.
-* Riak Search will not work with Riak TS.
+* Riak search will not work with Riak TS.
* Queries are limited by the number of quanta they can span when specifying the time limits.
diff --git a/content/riak/ts/1.3.1/releasenotes.md b/content/riak/ts/1.3.1/releasenotes.md
index 556f6259c2..00613396d9 100644
--- a/content/riak/ts/1.3.1/releasenotes.md
+++ b/content/riak/ts/1.3.1/releasenotes.md
@@ -111,6 +111,6 @@ Riak TS is compatible with the following:
### Known Issues
* AAE must be turned off.
-* Riak Search is not supported for TS data.
+* Riak search is not supported for TS data.
* HTTP API security is not supported. Security checks are included in the code path, but the permissions are not registered with riak_core, so enabling security means disabling any TS functionality. [[code](https://github.com/basho/riak_kv/blob/riak_ts-develop/src/riak_kv_app.erl#L214-L215)]
* Quanta with a '0' or negative integers are not supported and will cause errors.
diff --git a/content/riak/ts/1.3.1/using/querying.md b/content/riak/ts/1.3.1/using/querying.md
index 7b03162d6e..02ce095a82 100644
--- a/content/riak/ts/1.3.1/using/querying.md
+++ b/content/riak/ts/1.3.1/using/querying.md
@@ -324,7 +324,7 @@ The following operators are supported for each data type:
* Column to column comparisons are not currently supported.
* Secondary indexing (2i) will not work with Riak TS.
-* Riak Search will not work with Riak TS.
+* Riak search will not work with Riak TS.
* Queries are limited by the number of quanta they can span when specifying the time limits.
diff --git a/content/riak/ts/1.4.0/releasenotes.md b/content/riak/ts/1.4.0/releasenotes.md
index 81de75ee7c..13dc616ff7 100644
--- a/content/riak/ts/1.4.0/releasenotes.md
+++ b/content/riak/ts/1.4.0/releasenotes.md
@@ -93,6 +93,6 @@ Riak TS is compatible with the following:
* The list_keys API may be unreliable in clusters containing a mix of TS 1.3.1 and TS 1.4 nodes.
* AAE must be turned off.
-* Riak Search, and subsequently Solr, is not supported for TS.
+* Riak search, and subsequently Solr, is not supported for TS.
* HTTP API security is not supported. Security checks are included in the code path, but the permissions are not registered with riak_core, so enabling security in HTTP means disabling any TS functionality. See the code [here](https://github.com/basho/riak_kv/blob/riak_ts-develop/src/riak_kv_app.erl#L214-L215).
* Bitcask backend must not be used with Riak TS.
diff --git a/content/riak/ts/1.4.0/using/querying/guidelines.md b/content/riak/ts/1.4.0/using/querying/guidelines.md
index 0d6c8cc60b..b361c9b02f 100644
--- a/content/riak/ts/1.4.0/using/querying/guidelines.md
+++ b/content/riak/ts/1.4.0/using/querying/guidelines.md
@@ -136,7 +136,7 @@ The following operators are supported for each data type:
* Column to column comparisons are not currently supported.
* Secondary indexing (2i) will not work with Riak TS.
-* Riak Search will not work with Riak TS.
+* Riak search will not work with Riak TS.
* Queries are limited by the number of quanta they can span when specifying the time limits.
diff --git a/extras/data/blog_post_schema.xml b/extras/data/blog_post_schema.xml
index 5af7f4d986..99fda9a2a3 100644
--- a/extras/data/blog_post_schema.xml
+++ b/extras/data/blog_post_schema.xml
@@ -9,7 +9,7 @@
-
+