Andrii Krupskyi
05/28/2024, 9:40 AMkapa.ai
05/28/2024, 9:40 AMVERSION
at the top of the ./run-ab-platform.sh
script. 3. Execute the Downgrade Commands: - Follow these steps to change the version and restart your Airbyte instance: bash # Change version on `./run-ab-platform.sh` to the desired version VERSION=0.50.20 # Replace with your desired version # If your instance is running, bring it down docker compose down # Remove your docker-compose and .env files ./run-ab-platform.sh -r # Bring your instance back up for the required version ./run-ab-platform.sh -b
- This will download the docker-compose.yml
and .env
files for your required version. If you have customized these files, you can run ./run-ab-platform.sh -d
to download them without running docker compose up
. 4. Reset Configuration if Necessary: - If the Airbyte instance does not start properly, you may need to reset your configuration. This means redoing all sources, destinations, and connections. bash # Warning: Resetting your configuration # You may have to reset your configuration if the Airbyte instance does not start properly. # This means redoing all sources, destinations, and connections.
### Additional Considerations - Rolling Back to Legacy Normalization: - If you are an Open Source user and encounter issues after upgrading to Destinations V2, you can optionally roll back. This process involves clearing each of your upgraded connections and manually typing in the previous destination version in the Airbyte UI. For more detailed instructions, you can refer to the following knowledge sources: - [Downgrading Airbyte Version](https://github.com/airbytehq/airbyte/issues/30287) - [Rolling Back to Legacy Normalization](https://docs.airbyte.com/release_notes/upgrading_to_destinations_v2#open-source-only-rolling-back-to-legacy-normalization) If you encounter any issues or need further assistance, feel free to reach out to the Airbyte support team or community forums.Andrii Krupskyi
05/28/2024, 9:41 AMkapa.ai
05/28/2024, 9:41 AMkapa.ai
05/28/2024, 9:41 AMACTOR_DEFINITION_ID
with the ID of the actor you want to downgrade and NEW_VERSION
with the desired version. sh docker exec -ti airbyte-db psql -U docker -d airbyte -c "UPDATE actor_definition_version SET version = 'NEW_VERSION' WHERE actor_definition_id = 'ACTOR_DEFINITION_ID';"
### Example If you want to downgrade a specific source or destination to version 0.44.0
, you would replace NEW_VERSION
with 0.44.0
and ACTOR_DEFINITION_ID
with the actual ID of the actor. sh docker exec -ti airbyte-db psql -U docker -d airbyte -c "UPDATE actor_definition_version SET version = '0.44.0' WHERE actor_definition_id = 'your_actor_definition_id';"
### Additional Considerations - Check for Null Documentation URLs: - If you encounter issues related to documentation URLs being null, you can run the following command to update the documentation_url
field: sh docker exec -ti airbyte-db psql -U docker -d airbyte -c "UPDATE actor_definition_version SET documentation_url = '' WHERE documentation_url IS NULL;"
This command ensures that any null documentation_url
fields are set to an empty string, which can resolve certain issues. For more detailed instructions and troubleshooting, you can refer to the following knowledge sources: - [Downgrading Airbyte Version](https://github.com/airbytehq/airbyte/issues/30287) - [Updating Actor Definition Version](https://github.com/airbytehq/airbyte/issues/28779) If you encounter any issues or need further assistance, feel free to reach out to the Airbyte support team or community forums.