jprdonnelly/airbyte
1
0
Fork 0
mirror of synced 2025-12-25 02:09:19 -05:00
Code Issues Packages Projects Releases Wiki Activity

Hotfix: Adjust more formatting.

Browse Source
This commit is contained in:
Davin Chia
2021-04-22 11:11:58 +08:00
parent 56a7dd4c86
commit e7204b99d3
1 changed files with 6 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
docs/tutorials/upgrading-airbyte.md
View File

@@ -36,13 +36,13 @@ If you inadvertently upgrade to a version of Airbyte that is not compatible with
--target-version <version you are migrating to or empty for latest>
```
Here's an example of what might look like with the values filled in. It assumes that the downloaded `airbyte_archive.tar.gz` is in `/tmp`.
Here's an example of what might look like with the values filled in. It assumes that the downloaded `airbyte_archive.tar.gz` is in `/tmp`.
```bash
docker run --rm -v /tmp:/config airbyte/migration:0.21.0-alpha --\
--input /config/airbyte_archive.tar.gz\
--output /config/airbyte_archive_migrated.tar.gz
```
```bash
docker run --rm -v /tmp:/config airbyte/migration:0.21.0-alpha --\
--input /config/airbyte_archive.tar.gz\
--output /config/airbyte_archive_migrated.tar.gz
```
{% hint style="info" %}
It may seem confusing that you need to specify the target version twice. The version passed as `--target-version` specifies the version to which the data will be migrated. Specifying the target version in the docker container tag makes sure that you are pulling an image that at least has the migration for the version you want. Technically the version used in the docker tag can be equal to or greater than the version you are upgrading to. For the simplicity of this tutorial we have them match.