Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

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

Merged
merged 3 commits into from
Jun 4, 2021
Merged

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

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
ba6a15f
docs(nocode): fix link to datahub-upgrade
hsheth2 Jun 4, 2021
41a2272
fix other link too
hsheth2 Jun 4, 2021
c50607b
fix line length
hsheth2 Jun 4, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions docs/advanced/no-code-upgrade.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down Expand Up @@ -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

Expand Down
3 changes: 2 additions & 1 deletion metadata-io/src/main/java/com/linkedin/metadata/entity/ebean/EbeanAspectDao.java
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -99,7 +99,8 @@ private boolean validateConnection() {
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 {
Expand Down