Merge pull request #136 from opensearch-project/remove-redirects

Remove outdated redirects
This commit is contained in:
Andrew Etter 2021-08-12 15:31:51 -07:00 committed by GitHub
commit 95b5157c19
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
93 changed files with 17 additions and 110 deletions

View File

@ -3,9 +3,6 @@ layout: default
title: OpenSearch CLI
nav_order: 52
has_children: false
redirect_from:
- /odfe-cli/
- /cli/
---
# OpenSearch CLI

View File

@ -5,7 +5,7 @@ nav_order: 200
has_children: true
has_toc: true
redirect_from:
- /logstash/
- /clients/logstash/
---
# Logstash

View File

@ -5,7 +5,6 @@ nav_order: 1
has_children: false
has_toc: false
redirect_from:
- /opensearch-dashboards/
- /dashboards/
---

View File

@ -27,4 +27,4 @@ nav_order: 30
./bin/opensearch-dashboards
```
1. See the [OpenSearch Dashboards documentation]({{site.url}}{{site.baseurl}}/opensearch-dashboards/).
1. See the [OpenSearch Dashboards documentation]({{site.url}}{{site.baseurl}}/dashboards/index/).

View File

@ -3,7 +3,7 @@ layout: default
title: Index rollups
nav_order: 35
has_children: true
redirect_from: /ism/index-rollups/
redirect_from: /im-plugin/index-rollups/
has_toc: false
---

View File

@ -2,7 +2,6 @@
layout: default
title: Index rollups API
parent: Index rollups
redirect_from: /ism/rollup-api/
nav_order: 9
---

View File

@ -3,7 +3,7 @@ layout: default
title: Index transforms
nav_order: 20
has_children: true
redirect_from: /im/index-transforms/
redirect_from: /im-plugin/index-transforms/
has_toc: false
---

View File

@ -2,7 +2,6 @@
layout: default
title: ISM API
parent: Index State Management
redirect_from: /ism/api/
nav_order: 5
---

View File

@ -4,8 +4,7 @@ title: Index State Management
nav_order: 3
has_children: true
redirect_from:
- /im/ism/
- /ism/
- /im-plugin/ism/
has_toc: false
---
@ -90,7 +89,6 @@ Make sure that the alias that you enter already exists. For more information abo
After you attach a policy to an index, ISM creates a job that runs every 5 minutes by default to perform policy actions, check conditions, and transition the index into different states. To change the default time interval for this job, see [Settings]({{site.url}}{{site.baseurl}}/im-plugin/ism/settings/).
If you want to use an OpenSearch operation to create an index with a policy already attached to it, see [create index]({{site.url}}{{site.baseurl}}/im-plugin/ism/api#create-index).
### Step 3: Manage indices

View File

@ -3,7 +3,6 @@ layout: default
title: Managed Indices
nav_order: 3
parent: Index State Management
redirect_from: /ism/managedindices/
has_children: false
---

View File

@ -3,7 +3,6 @@ layout: default
title: Policies
nav_order: 1
parent: Index State Management
redirect_from: /ism/policies/
has_children: false
---

View File

@ -2,7 +2,6 @@
layout: default
title: Settings
parent: Index State Management
redirect_from: /ism/settings/
nav_order: 4
---

View File

@ -3,7 +3,7 @@ layout: default
title: Refresh search analyzer
nav_order: 40
has_children: false
redirect_from: /ism/refresh-analyzer/
redirect_from: /im-plugin/refresh-analyzer/
has_toc: false
---

View File

@ -13,7 +13,7 @@ An anomaly in OpenSearch is any unusual behavior change in your time-series data
It can be challenging to discover anomalies using conventional methods such as creating visualizations and dashboards. You could configure an alert based on a static threshold, but this requires prior domain knowledge and isn't adaptive to data that exhibits organic growth or seasonal behavior.
Anomaly detection automatically detects anomalies in your OpenSearch data in near real-time using the Random Cut Forest (RCF) algorithm. RCF is an unsupervised machine learning algorithm that models a sketch of your incoming data stream to compute an `anomaly grade` and `confidence score` value for each incoming data point. These values are used to differentiate an anomaly from normal variations. For more information about how RCF works, see [Random Cut Forests](https://pdfs.semanticscholar.org/8bba/52e9797f2e2cc9a823dbd12514d02f29c8b9.pdf?_ga=2.56302955.1913766445.1574109076-1059151610.1574109076).
Anomaly detection automatically detects anomalies in your OpenSearch data in near real-time using the Random Cut Forest (RCF) algorithm. RCF is an unsupervised machine learning algorithm that models a sketch of your incoming data stream to compute an `anomaly grade` and `confidence score` value for each incoming data point. These values are used to differentiate an anomaly from normal variations. For more information about how RCF works, see [Random Cut Forests](https://api.semanticscholar.org/CorpusID:927435).
You can pair the anomaly detection plugin with the [alerting plugin]({{site.url}}{{site.baseurl}}/monitoring-plugins/alerting/) to notify you as soon as an anomaly is detected.

View File

@ -4,8 +4,6 @@ title: Cron
nav_order: 20
parent: Alerting
has_children: false
redirect_from:
- /alerting/cron/
---
# Cron expression reference

View File

@ -255,7 +255,7 @@ POST logs-redis/_rollover
If you now perform a `GET` operation on the `logs-redis` data stream, you see that the generation ID is incremented from 1 to 2.
You can also set up an [Index State Management (ISM) policy]({{site.url}}{{site.baseurl}}/ism/policies/) to automate the rollover process for the data stream.
You can also set up an [Index State Management (ISM) policy]({{site.url}}{{site.baseurl}}/im-plugin/ism/policies/) to automate the rollover process for the data stream.
The ISM policy is applied to the backing indices at the time of their creation. When you associate a policy to a data stream, it only affects the future backing indices of that data stream.
You also dont need to provide the `rollover_alias` setting, because the ISM policy infers this information from the backing index.

View File

@ -3,7 +3,6 @@ layout: default
title: Install OpenSearch
nav_order: 2
redirect_from:
- /install/
- /opensearch/install/
has_children: true
---

View File

@ -3,7 +3,6 @@ layout: default
title: Boolean queries
parent: Query DSL
nav_order: 45
redirect_from: /opensearch/bool/
---
# Boolean queries

View File

@ -3,7 +3,6 @@ layout: default
title: Full-text queries
parent: Query DSL
nav_order: 40
redirect_from: /opensearch/full-text/
---
# Full-text queries

View File

@ -3,7 +3,6 @@ layout: default
title: Term-level queries
parent: Query DSL
nav_order: 30
redirect_from: /opensearch/term/
---
# Term-level queries
@ -145,7 +144,7 @@ The search query “To be, or not to be” is analyzed and tokenized into an arr
...
```
For a list of all full-text queries, see [Full-text queries]({{site.url}}{{site.baseurl}}/opensearch/full-text/).
For a list of all full-text queries, see [Full-text queries]({{site.url}}{{site.baseurl}}/opensearch/query-dsl/full-text/).
If you want to query for an exact term like “HAMLET” in the speaker field and don't need the results to be sorted by relevance scores, a term-level query is more efficient:

View File

@ -4,6 +4,8 @@ title: Document APIs
parent: REST API reference
has_children: true
nav_order: 7
redirect_from:
- /opensearch/rest-api/document-apis/
---
# Document APIs

View File

@ -3,8 +3,6 @@ layout: default
title: Tasks
parent: REST API reference
nav_order: 80
redirect_from:
- /opensearch/tasksapi/
---
# Tasks

View File

@ -4,7 +4,6 @@ title: Asynchronous search
nav_order: 51
has_children: true
redirect_from:
- /async/
- /search-plugins/async/
---

View File

@ -4,7 +4,6 @@ title: Asynchronous search security
nav_order: 2
parent: Asynchronous search
has_children: false
redirect_from: /async/security/
---
# Asynchronous search security

View File

@ -3,7 +3,6 @@ layout: default
title: Settings
parent: Asynchronous search
nav_order: 4
redirect_from: /async/settings/
---
# Settings

View File

@ -4,7 +4,6 @@ title: k-NN API
nav_order: 5
parent: k-NN
has_children: false
redirect_from: /knn/api/
---
# k-NN plugin API

View File

@ -5,7 +5,6 @@ nav_order: 2
parent: k-NN
has_children: false
has_math: true
redirect_from: /knn/approximate-knn/
---
# Approximate k-NN search

View File

@ -5,7 +5,6 @@ nav_order: 50
has_children: true
has_toc: false
redirect_from:
- /knn/
- /search-plugins/knn/
---

View File

@ -4,7 +4,6 @@ title: JNI library
nav_order: 6
parent: k-NN
has_children: false
redirect_from: /knn/jni-library/
---
# JNI library

View File

@ -4,7 +4,6 @@ title: k-NN Index
nav_order: 1
parent: k-NN
has_children: false
redirect_from: /knn/knn-index/
---
# k-NN Index

View File

@ -5,7 +5,6 @@ nav_order: 3
parent: k-NN
has_children: false
has_math: true
redirect_from: /knn/knn-score-script/
---
# Exact k-NN with scoring script

View File

@ -5,7 +5,6 @@ nav_order: 4
parent: k-NN
has_children: false
has_math: true
redirect_from: /knn/painless-functions/
---
# k-NN Painless Scripting extensions

View File

@ -3,7 +3,6 @@ layout: default
title: Performance tuning
parent: k-NN
nav_order: 8
redirect_from: /knn/performance-tuning/
---
# Performance tuning

View File

@ -3,7 +3,6 @@ layout: default
title: Settings
parent: k-NN
nav_order: 7
redirect_from: /knn/settings/
---
# k-NN settings

View File

@ -3,7 +3,6 @@ layout: default
title: Commands
parent: Piped processing language
nav_order: 4
redirect_from: /ppl/commands/
---

View File

@ -3,7 +3,6 @@ layout: default
title: Data Types
parent: Piped processing language
nav_order: 6
redirect_from: /ppl/datatypes/
---

View File

@ -3,7 +3,6 @@ layout: default
title: Endpoint
parent: Piped processing language
nav_order: 1
redirect_from: /ppl/endpoint/
---
# Endpoint

View File

@ -3,7 +3,6 @@ layout: default
title: Functions
parent: Piped processing language
nav_order: 10
redirect_from: /ppl/functions/
---
# Functions

View File

@ -3,7 +3,6 @@ layout: default
title: Identifiers
parent: Piped processing language
nav_order: 7
redirect_from: /ppl/identifiers/
---

View File

@ -5,7 +5,6 @@ nav_order: 42
has_children: true
has_toc: false
redirect_from:
- /ppl/
- /search-plugins/ppl/
---

View File

@ -3,7 +3,6 @@ layout: default
title: Protocol
parent: Piped processing language
nav_order: 2
redirect_from: /ppl/protocol/
---
# Protocol

View File

@ -3,7 +3,6 @@ layout: default
title: Settings
parent: Piped processing language
nav_order: 3
redirect_from: /ppl/settings/
---
# Settings

View File

@ -3,7 +3,6 @@ layout: default
title: Aggregation Functions
parent: SQL
nav_order: 11
redirect_from: /sql/aggregations/
---
# Aggregation functions

View File

@ -3,7 +3,6 @@ layout: default
title: Basic Queries
parent: SQL
nav_order: 5
redirect_from: /sql/basic/
---

View File

@ -3,7 +3,6 @@ layout: default
title: SQL CLI
parent: SQL
nav_order: 2
redirect_from: /sql/cli/
---
# SQL CLI

View File

@ -3,7 +3,6 @@ layout: default
title: Complex Queries
parent: SQL
nav_order: 6
redirect_from: /sql/complex/
---
# Complex queries

View File

@ -3,7 +3,6 @@ layout: default
title: Data Types
parent: SQL
nav_order: 73
redirect_from: /sql/datatypes/
---
# Data types

View File

@ -3,7 +3,6 @@ layout: default
title: Delete
parent: SQL
nav_order: 12
redirect_from: /sql/delete/
---
@ -17,7 +16,7 @@ If you don't specify the `WHERE` clause, all documents are deleted.
The `DELETE` statement is disabled by default. To enable the `DELETE` functionality in SQL, you need to update the configuration by sending the following request:
```json
PUT _plugins/_query/settings
PUT _plugins/_query/settings
{
"transient": {
"plugins.sql.delete.enabled": "true"

View File

@ -3,7 +3,6 @@ layout: default
title: Endpoint
parent: SQL
nav_order: 13
redirect_from: /sql/endpoints/
---

View File

@ -3,7 +3,6 @@ layout: default
title: Functions
parent: SQL
nav_order: 10
redirect_from: /sql/functions/
---
# Functions

View File

@ -5,13 +5,12 @@ nav_order: 38
has_children: true
has_toc: false
redirect_from:
- /sql/
- /search-plugins/sql/
---
# SQL
OpenSearch SQL lets you write queries in SQL rather than the [OpenSearch query domain-specific language (DSL)]({{site.url}}{{site.baseurl}}/opensearch/full-text). If you're already familiar with SQL and don't want to learn the query DSL, this feature is a great option.
OpenSearch SQL lets you write queries in SQL rather than the [OpenSearch query domain-specific language (DSL)]({{site.url}}{{site.baseurl}}/opensearch/query-dsl/full-text). If you're already familiar with SQL and don't want to learn the query DSL, this feature is a great option.
## Workbench

View File

@ -3,7 +3,6 @@ layout: default
title: JDBC Driver
parent: SQL
nav_order: 71
redirect_from: /sql/jdbc/
---
# JDBC driver

View File

@ -3,7 +3,6 @@ layout: default
title: Limitations
parent: SQL
nav_order: 18
redirect_from: /sql/limitation/
---
# Limitations

View File

@ -3,7 +3,6 @@ layout: default
title: Metadata Queries
parent: SQL
nav_order: 9
redirect_from: /sql/metadata/
---
# Metadata queries

View File

@ -3,7 +3,6 @@ layout: default
title: Monitoring
parent: SQL
nav_order: 15
redirect_from: /sql/monitoring/
---
# Monitoring

View File

@ -3,7 +3,6 @@ layout: default
title: ODBC Driver
parent: SQL
nav_order: 72
redirect_from: /sql/obdc/
---
# ODBC driver

View File

@ -3,7 +3,6 @@ layout: default
title: JSON Support
parent: SQL
nav_order: 7
redirect_from: /sql/partiql/
---
# JSON Support

View File

@ -3,7 +3,6 @@ layout: default
title: Protocol
parent: SQL
nav_order: 14
redirect_from: /sql/protocol/
---
# Protocol
@ -132,7 +131,7 @@ Explain:
### Description
By default, the plugin returns the JDBC standard format. This format
is provided for JDBC driver and clients that need both schema and
is provided for JDBC driver and clients that need both schema and
result set well formatted.
### Example 1

View File

@ -3,7 +3,6 @@ layout: default
title: Settings
parent: SQL
nav_order: 16
redirect_from: /sql/settings/
---
# Settings

View File

@ -3,14 +3,13 @@ layout: default
title: Full-Text Search
parent: SQL
nav_order: 8
redirect_from: /sql/sql-full-text/
---
# Full-text search
Use SQL commands for full-text search. The SQL plugin supports a subset of the full-text queries available in OpenSearch.
To learn about full-text queries in OpenSearch, see [Full-text queries]({{site.url}}{{site.baseurl}}/opensearch/full-text/).
To learn about full-text queries in OpenSearch, see [Full-text queries]({{site.url}}{{site.baseurl}}/opensearch/query-dsl/full-text/).
## Match

View File

@ -3,7 +3,6 @@ layout: default
title: Troubleshooting
parent: SQL
nav_order: 17
redirect_from: /sql/troubleshoot/
---
# Troubleshooting

View File

@ -3,10 +3,8 @@ layout: default
title: Query Workbench
parent: SQL
nav_order: 1
redirect_from: /sql/workbench/
---
# Query Workbench
Use the Query Workbench to easily run on-demand SQL queries, translate SQL into its REST equivalent, and view and save results as text, JSON, JDBC, or CSV.

View File

@ -3,7 +3,6 @@ layout: default
title: Cross-Cluster Search
parent: Access Control
nav_order: 40
redirect_from: /security/access-control/cross-cluster-search/
---
# Cross-cluster search

View File

@ -3,7 +3,6 @@ layout: default
title: Default Action Groups
parent: Access Control
nav_order: 51
redirect_from: /security/access-control/default-action-groups/
---
# Default action groups

View File

@ -3,7 +3,6 @@ layout: default
title: Document-Level Security
parent: Access Control
nav_order: 10
redirect_from: /security/access-control/document-level-security/
---
# Document-level security

View File

@ -3,7 +3,6 @@ layout: default
title: Field-Level Security
parent: Access Control
nav_order: 11
redirect_from: /security/access-control/field-level-security/
---
# Field-level security

View File

@ -3,7 +3,6 @@ layout: default
title: Field Masking
parent: Access Control
nav_order: 12
redirect_from: /security/access-control/field-masking/
---
# Field masking

View File

@ -3,7 +3,6 @@ layout: default
title: User Impersonation
parent: Access Control
nav_order: 20
redirect_from: /security/access-control/impersonation/
---
# User impersonation

View File

@ -5,7 +5,6 @@ nav_order: 10
has_children: true
has_toc: false
redirect_from:
- /security/access-control/
- /security-plugin/access-control/
---

View File

@ -3,7 +3,6 @@ layout: default
title: OpenSearch Dashboards Multi-Tenancy
parent: Access Control
nav_order: 30
redirect_from: /security/access-control/multi-tenancy/
---
# OpenSearch Dashboards multi-tenancy

View File

@ -3,7 +3,6 @@ layout: default
title: Permissions
parent: Access Control
nav_order: 50
redirect_from: /security/access-control/permissions/
---
# Permissions

View File

@ -3,7 +3,6 @@ layout: default
title: Users and Roles
parent: Access Control
nav_order: 1
redirect_from: /security/access-control/users-roles/
---
# Users and roles

View File

@ -3,7 +3,6 @@ layout: default
title: Audit Log Field Reference
parent: Audit Logs
nav_order: 1
redirect_from: /security/audit-logs/field-reference/
---
# Audit log field reference

View File

@ -5,7 +5,6 @@ nav_order: 90
has_children: true
has_toc: false
redirect_from:
- /security/audit-logs/
- /security-plugin/audit-logs/
---

View File

@ -3,7 +3,6 @@ layout: default
title: Audit Log Storage Types
parent: Audit Logs
nav_order: 10
redirect_from: /security/audit-logs/storage-types/
---
# Audit log storage types

View File

@ -3,7 +3,6 @@ layout: default
title: Client certificate authentication
parent: Configuration
nav_order: 50
redirect_from: /security/configuration/client-auth/
---
# Client certificate authentication

View File

@ -3,7 +3,6 @@ layout: default
title: Authentication flow
parent: Configuration
nav_order: 1
redirect_from: /security/configuration/concepts/
---
# Authentication flow

View File

@ -3,7 +3,6 @@ layout: default
title: Backend Configuration
parent: Configuration
nav_order: 2
redirect_from: /security/configuration/configuration/
---
# Backend configuration

View File

@ -3,7 +3,6 @@ layout: default
title: Disable Security
parent: Configuration
nav_order: 99
redirect_from: /security/configuration/disable/
---
# Disable security

View File

@ -5,7 +5,6 @@ nav_order: 5
has_children: true
has_toc: false
redirect_from:
- /security/configuration/
- /security-plugin/configuration/
---

View File

@ -3,7 +3,6 @@ layout: default
title: Active Directory and LDAP
parent: Configuration
nav_order: 30
redirect_from: /security/configuration/ldap/
---
# Active Directory and LDAP

View File

@ -3,7 +3,6 @@ layout: default
title: OpenID Connect
parent: Configuration
nav_order: 32
redirect_from: /security/configuration/openid-connect/
---
# OpenID Connect

View File

@ -3,7 +3,6 @@ layout: default
title: Proxy-based authentication
parent: Configuration
nav_order: 40
redirect_from: /security/configuration/proxy/
---
# Proxy-based authentication

View File

@ -3,7 +3,6 @@ layout: default
title: SAML
parent: Configuration
nav_order: 31
redirect_from: /security/configuration/saml/
---
# SAML

View File

@ -3,7 +3,6 @@ layout: default
title: System Indices
parent: Configuration
nav_order: 15
redirect_from: /security/configuration/system-indices/
---
# System indices

View File

@ -3,7 +3,6 @@ layout: default
title: TLS Certificates
parent: Configuration
nav_order: 10
redirect_from: /security/configuration/tls/
---
# Configure TLS certificates

View File

@ -3,7 +3,6 @@ layout: default
title: YAML Files
parent: Configuration
nav_order: 3
redirect_from: /security/configuration/yaml/
---
# YAML files

View File

@ -5,7 +5,6 @@ nav_order: 1
has_children: false
has_toc: false
redirect_from:
- /security/
- /security-plugin/
---

View File

@ -2,8 +2,6 @@
layout: default
title: Upgrade from Kibana OSS to OpenSearch Dashboards
nav_order: 50
redirect_from:
- /migrate/dashboards/
---
# Upgrade from Kibana OSS to OpenSearch Dashboards

View File

@ -2,14 +2,12 @@
layout: default
title: Upgrade Docker clusters to OpenSearch
nav_order: 25
redirect_from:
- /migrate/docker-migrate/
---
# Upgrade Docker clusters to OpenSearch
If you use a container orchestration system like Kubernetes (or manage your containers manually) and want to avoid downtime, think of the process not as an upgrade of each node, but as a decommissioning and replacement of each node. One by one, add OpenSearch nodes to the cluster and remove Elasticsearch OSS nodes, pointing to existing data volumes as necessary and allowing time for all indices to return to a green status prior to proceeding.
If you use Docker Compose, we highly recommend that you perform what amounts to a [cluster restart upgrade]({{site.url}}{{site.baseurl}}/migrate/upgrade-migrate/). Update your cluster configuration with new images, new settings, and new environment variables, and test it. Then stop and start the cluster. This process requires downtime, but takes very few steps and lets you continue to treat the cluster as a single entity that you can reliably deploy and redeploy.
If you use Docker Compose, we highly recommend that you perform what amounts to a [cluster restart upgrade]({{site.url}}{{site.baseurl}}/upgrade-to/upgrade-to/). Update your cluster configuration with new images, new settings, and new environment variables, and test it. Then stop and start the cluster. This process requires downtime, but takes very few steps and lets you continue to treat the cluster as a single entity that you can reliably deploy and redeploy.
The most important step is to leave your data volumes intact. **Don't** run `docker-compose down -v`.

View File

@ -3,7 +3,6 @@ layout: default
title: About the process
nav_order: 1
redirect_from:
- /migrate/
- /upgrade-to/
---

View File

@ -2,8 +2,6 @@
layout: default
title: Use snapshots to migrate data
nav_order: 5
redirect_from:
- /migrate/snapshot-migrate/
---
# Use snapshots to migrate data

View File

@ -2,13 +2,11 @@
layout: default
title: Upgrade from Elasticsearch OSS to OpenSearch
nav_order: 15
redirect_from:
- /migrate/upgrade-migrate/
---
# Upgrade from Elasticsearch OSS to OpenSearch
If you want to upgrade from an existing Elasticsearch OSS cluster to OpenSearch and find the [snapshot approach]({{site.url}}{{site.baseurl}}/migrate/snapshot-migrate/) unappealing, you can upgrade your existing nodes from Elasticsearch OSS to OpenSearch.
If you want to upgrade from an existing Elasticsearch OSS cluster to OpenSearch and find the [snapshot approach]({{site.url}}{{site.baseurl}}/upgrade-to/snapshot-migrate/) unappealing, you can upgrade your existing nodes from Elasticsearch OSS to OpenSearch.
If your existing cluster runs an older version of Elasticsearch OSS, the first step is to upgrade to version 6.x or 7.x. Elasticsearch OSS supports two types of upgrades: rolling and cluster restart.