docs(nocode): fix links to datahub-upgrade (#2651)

This commit is contained in:
Harshal Sheth 2021-06-04 11:30:06 -07:00 committed by GitHub
parent d26903f160
commit f91062d827
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 6 additions and 5 deletions

View File

@ -71,8 +71,8 @@ You can either
2. Define a new ".env" file containing your variables and
execute `docker pull acryldata/datahub-upgrade && docker run acryldata/datahub-upgrade:latest -u NoCodeDataMigration`
To see the required environment variables, see the (datahub-upgrade)[../../docker/datahub-upgrade/README.md]
documentation
To see the required environment variables, see the [datahub-upgrade](../../docker/datahub-upgrade/README.md)
documentation.
##### How to fix the "listening to port 5005" issue
@ -105,8 +105,8 @@ validated that your DataHub deployment is healthy after performing the upgrade.
view your Metadata after the upgrade steps have been completed, you should be in good shape.
In advanced DataHub deployments, or cases in which you cannot easily rebuild the state stored in DataHub, it is strongly
advised that you do due diligence prior to running cleanup. This may involve manually inspecting the relational tables (
metadata_aspect_v2), search indices, and graph topology.
advised that you do due diligence prior to running cleanup. This may involve manually inspecting the relational
tables (metadata_aspect_v2), search indices, and graph topology.
#### Docker Compose Deployments

View File

@ -99,7 +99,8 @@ public class EbeanAspectDao {
return true;
}
if (!AspectStorageValidationUtil.checkV2TableExists(_server)) {
_logger.error("GMS is on a newer version than your storage layer. Please refer to /docs/advanced/no-code-upgrade.md for an easy upgrade guide");
_logger.error("GMS is on a newer version than your storage layer. Please refer to "
+ "https://datahubproject.io/docs/advanced/no-code-upgrade for an easy upgrade guide");
_canWrite = false;
return false;
} else {