Fix postgres migrations (#13743)

This commit is contained in:
Pere Miquel Brull 2023-10-27 13:42:53 +02:00 committed by GitHub
parent 35869c9736
commit f7daad83da
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
3 changed files with 12 additions and 8 deletions

View File

@ -237,7 +237,7 @@ WHERE json #>> '{reportDataType}' = 'WebAnalyticUserActivityReportData';
CREATE TABLE IF NOT EXISTS installed_apps (
id VARCHAR(36) GENERATED ALWAYS AS (json ->> 'id') STORED NOT NULL,
nameHash VARCHAR(256) NOT NULL,
name VARCHAR(256) GENERATED ALWAYS AS (json ->> 'name') NOT NULL,
name VARCHAR(256) GENERATED ALWAYS AS (json ->> 'name') STORED NOT NULL,
json JSONB NOT NULL,
updatedAt BIGINT GENERATED ALWAYS AS ((json ->> 'updatedAt')::bigint) STORED NOT NULL,
updatedBy VARCHAR(256) GENERATED ALWAYS AS (json ->> 'updatedBy') STORED NOT NULL,
@ -249,7 +249,7 @@ CREATE TABLE IF NOT EXISTS installed_apps (
CREATE TABLE IF NOT EXISTS apps_marketplace (
id VARCHAR(36) GENERATED ALWAYS AS (json ->> 'id') STORED NOT NULL,
nameHash VARCHAR(256) NOT NULL,
name VARCHAR(256) GENERATED ALWAYS AS (json ->> 'name') NOT NULL,
name VARCHAR(256) GENERATED ALWAYS AS (json ->> 'name') STORED NOT NULL,
json JSONB NOT NULL,
updatedAt BIGINT GENERATED ALWAYS AS ((json ->> 'updatedAt')::bigint) STORED NOT NULL,
updatedBy VARCHAR(256) GENERATED ALWAYS AS (json ->> 'updatedBy') STORED NOT NULL,

View File

@ -117,12 +117,12 @@ After the migration is finished, you can revert this changes.
There is no direct migration to bump the indexes to the new supported versions. You might see errors like:
```
"java.lang.IllegalStateException: cannot upgrade a node from version [7.16.3] directly to version [8.5.1]
java.lang.IllegalStateException: cannot upgrade a node from version [7.16.3] directly to version [8.5.1]
ERROR: Elasticsearch did not exit normally - check the logs at /usr/share/elasticsearch/logs/elasticsearch.log
ERROR: Elasticsearch exited unexpectedly
```
In order to move forward, **you must remove volumes or delete the indexes** directly from your search instances. Note that
In order to move forward, **you must remove the volumes or delete the indexes** directly from your search instances. Note that
OpenMetadata stores everything in the database, so indexes can be recreated from the UI. We will
show you how in the [Post-Upgrade Steps](/deployment/upgrade#reindex).
@ -143,6 +143,9 @@ then there is no way to link a query to a service and the query will be removed.
### Service Connection Changes
- Domo Database, Dashboard and Pipeline renamed the `sandboxDomain` in favor of `instanceDomain`.
- The `DatabaseMetadata` configuration renamed `viewParsingTimeoutLimit` to `queryParsingTimeoutLimit`.
- The `DatabaseMetadata` configuration removed the `markAllDeletedTables` option. For simplicity, we'll only
mark as deleted the tables coming from the filtered ingestion results.
### Ingestion Framework Changes

View File

@ -45,11 +45,12 @@ Verify with the below command to see the latest release available locally.
```commandline
helm search repo open-metadata --versions
> NAME CHART VERSION APP VERSION DESCRIPTION
open-metadata/openmetadata 1.1.3 1.1.0 A Helm chart for OpenMetadata on Kubernetes
open-metadata/openmetadata 1.1.2 1.1.0 A Helm chart for OpenMetadata on Kubernetes
open-metadata/openmetadata 1.2.1 1.2.0 A Helm chart for OpenMetadata on Kubernetes
open-metadata/openmetadata 1.2.0 1.2.0 A Helm chart for OpenMetadata on Kubernetes
...
open-metadata/openmetadata-dependencies 1.1.3 1.1.0 Helm Dependencies for OpenMetadata
open-metadata/openmetadata-dependencies 1.1.2 1.1.0 Helm Dependencies for OpenMetadata
open-metadata/openmetadata-dependencies 1.2.1 1.2.0 Helm Dependencies for OpenMetadata
open-metadata/openmetadata-dependencies 1.2.0 1.2.0 Helm Dependencies for OpenMetadata
...
```