Influxdata
/
docs-v2
mirror of https://github.com/influxdata/docs-v2.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Merge branch 'master' of github.com:influxdata/docs-v2

pull/1903/head
Scott Anderson 2020-11-30 13:57:06 -07:00
parent a226d6ab11 dd9b2069c3
commit 4479c0078b
5 changed files with 20 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
content/influxdb/v1.8/query_language/manage-database.md
View File

@ -327,7 +327,7 @@ See [Create a database with CREATE DATABASE](/influxdb/v1.8/query_language/manag
The `ALTER RETENTION POLICY` query takes the following form, where you must declare at least one of the retention policy attributes `DURATION`, `REPLICATION`, `SHARD DURATION`, or `DEFAULT`:
```sql
ALTER RETENTION POLICY <retention_policy_name> ON <database_name> DURATION <duration> REPLICATION <n> SHARD DURATION <duration> DEFAULT
ALTER RETENTION POLICY <retention_policy_name> ON <database_name> [DURATION <duration>] [REPLICATION <n>] [SHARD DURATION <duration>] [DEFAULT]
```
{{% warn %}} Replication factors do not serve a purpose with single node instances.

2
content/influxdb/v2.0/get-started.md
View File

@ -253,7 +253,7 @@ Expose port `8086`, which InfluxDB uses for client-server communication over
the [InfluxDB HTTP API](/influxdb/v2.0/reference/api/).
```sh
docker run --name influxdb -p 8086:8086 quay.io/influxdb/influxdb:2.0.0-rc
docker run --name influxdb -p 8086:8086 quay.io/influxdb/influxdb:v2.0.2
```
_To run InfluxDB in [detached mode](https://docs.docker.com/engine/reference/run/#detached-vs-foreground), include the `-d` flag in the `docker run` command._

7
content/influxdb/v2.0/security/_index.md
View File

@ -15,4 +15,11 @@ Security, access control, and sensitive secret handling are incredibly important
when handling any sort of sensitive data.
This section provides information about managing the security of your InfluxDB instance.
{{% note %}}
#### InfluxDB 2.0/1.x compatibility
If you [upgraded from 1.x to 2.0](/influxdb/v2.0/upgrade/v1-to-v2/),
use the [`influx v1 auth`](/influxdb/v2.0/reference/cli/influx/v1/auth/) commands
to manage authorizations for the [1.x compatibility API](/influxdb/v2.0/reference/api/influxdb-1x/).
{{% /note %}}
{{< children >}}

4
content/influxdb/v2.0/upgrade/v1-to-v2/_index.md
View File

@ -194,6 +194,10 @@ and are ready to proceed, follow these steps to upgrade your InfluxDB 1.x to Inf
The output of the upgrade prints to standard output.
It is also saved (for troubleshooting and debugging) in the current directory to a file called `upgrade.log` located in the home directory of the user running `influxdb upgrade`.
### Post-upgrade
To verify 1.x users were successfully migrated to 2.0, run [`influx v1 auth list`](influxdb/v2.0/reference/cli/influx/v1/auth/list/).
## Further reading
For more information on upgrading, see the [`influxd upgrade` reference documentation](/influxdb/v2.0/reference/cli/influxd/upgrade/).

7
content/influxdb/v2.0/users/_index.md
View File

@ -16,4 +16,11 @@ and provide them with an [authentication token](/influxdb/v2.0/security/tokens/)
The following articles walk through managing users.
{{% note %}}
#### InfluxDB 2.0/1.x compatibility
If you [upgraded from 1.x to 2.0](/influxdb/v2.0/upgrade/v1-to-v2/),
use the [`influx v1 auth`](/influxdb/v2.0/reference/cli/influx/v1/auth/) commands
to manage authorizations for the InfluxDB [1.x compatibility API](/influxdb/v2.0/reference/api/influxdb-1x/).
{{% /note %}}
{{< children >}}