Fixes broken links in docs page main branch (#1501)
* Fixed broken link in RPM guide Signed-off-by: JeffH-AWS <jeffhuss@amazon.com> * More fixes Signed-off-by: JeffH-AWS <jeffhuss@amazon.com> * All done Signed-off-by: JeffH-AWS <jeffhuss@amazon.com> Signed-off-by: JeffH-AWS <jeffhuss@amazon.com>
This commit is contained in:
Jeff Huss
GitHub
parent
a35ba16214
commit
6583bfeeff
|
|
@ -11,7 +11,7 @@ The OpenSearch Kubernetes Operator is an open-source kubernetes operator that he
|
|||
|
||||
There are two ways to get started with the operator:
|
||||
|
||||
- [Use a Helm chart](#use-a-helm-chartuse-a-helm).
|
||||
- [Use a Helm chart](#use-a-helm-chart).
|
||||
- [Use a local installation](#use-a-local-installation).
|
||||
|
||||
### Use a Helm chart
|
||||
|
|
|
|||
|
|
@ -56,5 +56,5 @@ You can run OpenSearch Dashboards on a local host after installing OpenSearch. S
|
|||
- [Getting Started with OpenSearch]({{site.url}}{{site.baseurl}}).
|
||||
- [Launch Highlight: OpenSearch Playground](https://www.opensearch.org/blog/community/2022/10/opensearch-playground/)
|
||||
- [Upgrade from Kibana OSS to OpenSearch Dashboards]({{site.url}}{{site.baseurl}}/upgrade-to/dashboards-upgrade-to/)
|
||||
- [OpenSearch Frequently Asked Questions]({{site.url}}{{site.baseurl}}/faq/)
|
||||
- [OpenSearch Frequently Asked Questions]({{site.url}}/faq/)
|
||||
- [OpenSearch Dashboards Developer Guide](https://github.com/opensearch-project/OpenSearch-Dashboards/blob/main/DEVELOPER_GUIDE.md)
|
||||
|
|
@ -140,7 +140,7 @@ Before launching OpenSearch you should review some [important system settings]({
|
|||
|
||||
Before proceeding with any configuration, you should test your installation of OpenSearch. Otherwise, it can be difficult to determine whether future problems are due to installation issues or custom settings you applied after installation.
|
||||
|
||||
When OpenSearch is installed using the RPM package, some demo security settings are automatically applied. This includes self-signed TLS certificates and several users and roles. If you would like to configure these yourself, see [Set up OpenSearch in your environment](#setup-opensearch-in-your-environment).
|
||||
When OpenSearch is installed using the RPM package, some demo security settings are automatically applied. This includes self-signed TLS certificates and several users and roles. If you would like to configure these yourself, see [Set up OpenSearch in your environment]({{site.url}}{{site.baseurl}}/opensearch/install/rpm/#step-4-set-up-opensearch-in-your-environment).
|
||||
|
||||
An OpenSearch node in its default configuration (with demo certificates and users with default passwords) is not suitable for a production environment. If you plan to use the node in a production environment, you should, at a minimum, replace the demo TLS certificates with your own TLS certificates and [update the list of internal users and passwords]({{site.url}}{{site.baseurl}}/security-plugin/configuration/yaml). See [Security configuration]({{site.url}}{{site.baseurl}}/security-plugin/configuration/index/) for additional guidance to ensure that your nodes are configured according to your security requirements.
|
||||
{: .warning}
|
||||
|
|
@ -471,7 +471,6 @@ sudo yum update
|
|||
## Related links
|
||||
|
||||
- [OpenSearch configuration]({{site.url}}{{site.baseurl}}/opensearch/configuration/)
|
||||
- [Configure Performance Analyzer for Tarball Installation]({{site.url}}{{site.baseurl}}/monitoring-plugins/pa/index/#configure-performance-analyzer-for-tarball-installation)
|
||||
- [Install and configure OpenSearch Dashboards]({{site.url}}{{site.baseurl}}/dashboards/install/index/)
|
||||
- [OpenSearch plugin installation]({{site.url}}{{site.baseurl}}/opensearch/install/plugins/)
|
||||
- [About the security plugin]({{site.url}}{{site.baseurl}}/security-plugin/index/)
|
||||
|
|
@ -310,7 +310,7 @@ Parameter | Behavior
|
|||
`lte` | Less than or equal to.
|
||||
`lt` | Less than.
|
||||
|
||||
In addition to the range query parameters, you can provide date formats or relation operators such as "contains" or "within." To see the supported field types for range queries, see [Range query optional parameters]({{site.url}}{{site.baseurl}}/opensearch/supported-field-types/range/#range-query-optional-parameters). To see all date formats, see [Formats]({{site.url}}{{site.baseurl}}/opensearch/supported-field-types/date/#formats).
|
||||
In addition to the range query parameters, you can provide date formats or relation operators such as "contains" or "within." To see the supported field types for range queries, see [Range query optional parameters]({{site.url}}{{site.baseurl}}/opensearch/supported-field-types/range/#range-query). To see all date formats, see [Formats]({{site.url}}{{site.baseurl}}/opensearch/supported-field-types/date/#formats).
|
||||
{: .tip }
|
||||
|
||||
Assume that you have a `products` index and you want to find all the products that were added in the year 2019:
|
||||
|
|
|
|||
|
|
@ -56,7 +56,7 @@ PUT testindex/_doc/1
|
|||
}
|
||||
```
|
||||
|
||||
You can use a [term query](#term-query) or a [range query](#range-query) to search for values within range fields.
|
||||
You can use a [Term query](#term-query) or a [Range query](#range-query) to search for values within range fields.
|
||||
|
||||
### Term query
|
||||
|
||||
|
|
@ -77,7 +77,7 @@ GET testindex/_search
|
|||
}
|
||||
```
|
||||
|
||||
### Range query optional parameters
|
||||
### Range query
|
||||
|
||||
A range query on a range field returns documents within that range. Along with the field to be matched, you can further specify a date format or relational operators with the following optional parameters:
|
||||
|
||||
|
|
|
|||
|
|
@ -59,7 +59,7 @@ GET shakespeare/_search
|
|||
|
||||
Prefix matching doesn’t require any special mappings. It works with your data as-is.
|
||||
However, it’s a fairly resource-intensive operation. A prefix of `a` could match hundreds of thousands of terms and not be useful to your user.
|
||||
To limit the impact of prefix expansion, set `max_expansions` to a reasonable number. To learn about the `max_expansions` option, see [Options]({{site.url}}{{site.baseurl}}/opensearch/query-dsl/full-text#options).
|
||||
To limit the impact of prefix expansion, set `max_expansions` to a reasonable number. To learn about the `max_expansions` option, see [Options]({{site.url}}{{site.baseurl}}/opensearch/query-dsl/full-text#other-optional-query-fields).
|
||||
|
||||
#### Sample Request
|
||||
|
||||
|
|
|
|||
|
|
@ -148,7 +148,7 @@ You can specify the following options for `MULTI_MATCH` in any order:
|
|||
- `zero_terms_query`
|
||||
- `boost`
|
||||
|
||||
Please, refer to `multi_match` query [documentation]({{site.url}}{{site.baseurl}}/opensearch/query-dsl/full-text/#multi-match) for parameter description and supported values.
|
||||
Please, refer to `multi_match` query [documentation](#multi-match) for parameter description and supported values.
|
||||
|
||||
### For example, REST API search for `Dale` in either the `firstname` or `lastname` fields:
|
||||
|
||||
|
|
|
|||
|
|
@ -191,7 +191,7 @@ Specify a condition to filter the results.
|
|||
`>=` | Greater than or equal to.
|
||||
`<=` | Less than or equal to.
|
||||
`IN` | Specify multiple `OR` operators.
|
||||
`BETWEEN` | Similar to a range query. For more information about range queries, see [Range query]({{site.url}}{{site.baseurl}}/opensearch/query-dsl/term#range).
|
||||
`BETWEEN` | Similar to a range query. For more information about range queries, see [Range query]({{site.url}}{{site.baseurl}}/opensearch/query-dsl/term#range-query).
|
||||
`LIKE` | Use for full text search. For more information about full-text queries, see [Full-text queries]({{site.url}}{{site.baseurl}}/opensearch/query-dsl/full-text/).
|
||||
`IS NULL` | Check if the field value is `NULL`.
|
||||
`IS NOT NULL` | Check if the field value is `NOT NULL`.
|
||||
|
|
|
|||
Loading…
Reference in New Issue