Berichtstabellen zu Metadatenimporten und -anreicherungen
Überprüfen Sie die Anweisungen unter Postgres, Db2 und Oracle für die Tabellen, die sich auf den Import und die Anreicherung von Metadaten beziehen.
| Themenbereich | Tabellenname | Beschreibung |
|---|---|---|
| Import und Anreicherung von Metadaten | Metadatenimporte | Metadata import Informationen. |
| Import und Anreicherung von Metadaten | Ausführungen des Metadatenimports | Der geplante Zeitpunkt des Metadaten-Import-Jobs. |
| Import und Anreicherung von Metadaten | Metadaten-Anreicherungen | Informationen zur Anreicherung von Metadaten. |
| Import und Anreicherung von Metadaten | job_asset | Diese Tabelle enthält Informationen zu Job-Assets. |
| Import und Anreicherung von Metadaten | Auftragsausführung_Asset | Diese Tabelle enthält Informationen zur Ausführung von Jobs. |
Tabelle „metadata_imports“
Diese Tabelle enthält Informationen zum Metadatenimport.
Diese Tabelle enthält die folgenden Spalten:
metadata_import_id- Kennung für den Metadatenimport.container_id- Die Kennung des Projekts.metadata_import_name- Der Name des Metadaten-Imports.target_container_id- Die Kennung des Zielprojekts.connection_id- Die Verbindungs-ID, auf der ein Import erstellt wird.
Postgres
Anweisung CREATE TABLE:
create table metadata_imports(metadata_import_id varchar(128) not null,
container_id varchar(128) not null,
metadata_import_name varchar(256) not null,
target_container_id varchar(128),
connection_id varchar(128),
metadata_enrichment_id varchar(128),
tech_start TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
tech_end TIMESTAMP(6) not null default to_timestamp('9999-12-30', 'YYYY-MM-DD'),
ts_id TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
primary key(container_id,
metadata_import_id))
Anweisung ALTER TABLE:
alter table metadata_imports add constraint fk_metadata_imports_container_assets_2 foreign key (container_id,
metadata_import_id) references container_assets(container_id,
asset_id) on
delete
cascade on
update
no action
Db2
Anweisung CREATE TABLE:
create table metadata_imports(metadata_import_id varchar(128) not null,
container_id varchar(128) not null,
metadata_import_name varchar(256) not null,
target_container_id varchar(128),
connection_id varchar(128),
metadata_enrichment_id varchar(128),
tech_start TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row begin,
tech_end TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row
end,
ts_id TIMESTAMP(12) not null generated always as transaction start ID,
primary key(container_id,
metadata_import_id),
period SYSTEM_TIME (tech_start,
tech_end) ) ORGANIZE by row
Anweisung ALTER TABLE:
alter table metadata_imports add constraint fk_metadata_imports_container_assets_2 foreign key (container_id,
metadata_import_id) references container_assets(container_id,
asset_id) on
delete
cascade on
update
no action
Oracle
Anweisung CREATE TABLE:
CREATE TABLE metadata_imports(metadata_import_id varchar(128) NOT NULL,
container_id varchar(128) NOT NULL,
metadata_import_name varchar(256) NOT NULL,
target_container_id varchar(128),
connection_id varchar(128),
metadata_enrichment_id varchar(128),
tech_start TIMESTAMP(6) DEFAULT SYSTIMESTAMP NOT NULL,
tech_end TIMESTAMP(6) DEFAULT to_timestamp('9999-12-30', 'YYYY-MM-DD') NOT NULL,
ts_id TIMESTAMP(6) DEFAULT SYSTIMESTAMP NOT NULL,
PRIMARY KEY(container_id,
metadata_import_id))
Anweisung ALTER TABLE:
ALTER TABLE metadata_imports ADD CONSTRAINT fk_metadata_imports_container_assets_2 FOREIGN KEY (container_id,
metadata_import_id) REFERENCES container_assets(container_id,
asset_id) ON
DELETE
CASCADE
Tabelle „metadata_import_executions“
Diese Tabelle enthält Informationen zum Metadaten-Import-Auftrag.
Diese Tabelle enthält die folgenden Spalten:
metadata_import_id- Kennung für den Metadatenimport.container_id- Die Kennung des Projekts.job_run_id- Die Kennung des Joblaufs.invoked_by- Die ID der Person, die den Vorgang gestartet hat.is_scheduled_run- Der geplante Zeitpunkt für den Metadaten-Import.start_time- Die Startzeit des Auftrags zum Importieren von Metadaten.end_time- Die Endzeit des Auftrags für den Metadatenimport.state- Der Status des Metadaten-Importauftrags.count_discovered- Die Anzahl der ermittelten Vermögenswerte.count_discovered_with_children- Die Anzahl der ermittelten Vermögenswerte mit untergeordneten Elementen.count_submitted- Die Anzahl der ermittelten Vermögenswerte.count_succeeded- Die Anzahl der Assets, die erfolgreich importiert wurden.count_succedded_with_children- Die Anzahl der Assets mit untergeordneten Elementen, die erfolgreich importiert wurden.count_new_assets- Die Anzahl der neuen Vermögenswerte.count_updated_assets- Die Anzahl der aktualisierten Objekte.count_deleted_assets- Die Anzahl der gelöschten Objekte.
Postgres
Anweisung CREATE TABLE:
create table metadata_import_executions(metadata_import_id varchar(128) not null,
container_id varchar(36) not null,
job_run_id varchar(128) not null,
invoked_by varchar(128) not null,
is_scheduled_run boolean not null,
start_time timestamp(6) not null,
end_time timestamp(6),
state varchar(32) not null,
count_discovered bigint default 0 not null,
count_discovered_with_children bigint default 0 not null,
count_submitted bigint default 0 not null,
count_succeeded bigint default 0 not null,
count_succedded_with_children bigint default 0 not null,
count_new_assets bigint default 0 not null,
count_updated_assets bigint default 0 not null,
count_deleted_assets bigint default 0 not null,
tech_start TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
tech_end TIMESTAMP(6) not null default to_timestamp('9999-12-30', 'YYYY-MM-DD'),
ts_id TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
primary key(container_id,
metadata_import_id,
job_run_id))
Anweisungen ALTER TABLE:
alter table metadata_import_executions add constraint fk_metadata_import_executions_metadata_imports_3 foreign key (container_id,
metadata_import_id) references metadata_imports(container_id,
metadata_import_id) on
delete
cascade on
update
no action
alter table metadata_import_executions add constraint fk_metadata_import_executions_container_assets_4 foreign key (container_id,
job_run_id) references container_assets(container_id,
asset_id) on
delete
cascade on
update
no action
Db2
Anweisung CREATE TABLE:
create table metadata_import_executions(metadata_import_id varchar(128) not null,
container_id varchar(36) not null,
job_run_id varchar(128) not null,
invoked_by varchar(128) not null,
is_scheduled_run boolean not null,
start_time timestamp(12) not null,
end_time timestamp(12),
state varchar(32) not null,
count_discovered bigint default 0 not null,
count_discovered_with_children bigint default 0 not null,
count_submitted bigint default 0 not null,
count_succeeded bigint default 0 not null,
count_succedded_with_children bigint default 0 not null,
count_new_assets bigint default 0 not null,
count_updated_assets bigint default 0 not null,
count_deleted_assets bigint default 0 not null,
tech_start TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row begin,
tech_end TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row
end,
ts_id TIMESTAMP(12) not null generated always as transaction start ID,
primary key(container_id,
metadata_import_id,
job_run_id),
period SYSTEM_TIME (tech_start,
tech_end) ) ORGANIZE by row
Anweisungen ALTER TABLE:
alter table metadata_import_executions add constraint fk_metadata_import_executions_metadata_imports_3 foreign key (container_id,
metadata_import_id) references metadata_imports(container_id,
metadata_import_id) on
delete
cascade on
update
no action
alter table metadata_import_executions add constraint fk_metadata_import_executions_container_assets_4 foreign key (container_id,
job_run_id) references container_assets(container_id,
asset_id) on
delete
cascade on
update
no action
Oracle
Anweisung CREATE TABLE:
CREATE TABLE metadata_import_executions(metadata_import_id varchar(128) NOT NULL,
container_id varchar(36) NOT NULL,
job_run_id varchar(128) NOT NULL,
invoked_by varchar(128) NOT NULL,
is_scheduled_run decimal(1) NOT NULL,
start_time timestamp(6) NOT NULL,
end_time timestamp(6),
state varchar(32) NOT NULL,
count_discovered NUMBER(19) DEFAULT 0 NOT NULL,
count_discovered_with_children NUMBER(19) DEFAULT 0 NOT NULL,
count_submitted NUMBER(19) DEFAULT 0 NOT NULL,
count_succeeded NUMBER(19) DEFAULT 0 NOT NULL,
count_succedded_with_children NUMBER(19) DEFAULT 0 NOT NULL,
count_new_assets NUMBER(19) DEFAULT 0 NOT NULL,
count_updated_assets NUMBER(19) DEFAULT 0 NOT NULL,
count_deleted_assets NUMBER(19) DEFAULT 0 NOT NULL,
tech_start TIMESTAMP(6) DEFAULT SYSTIMESTAMP NOT NULL,
tech_end TIMESTAMP(6) DEFAULT to_timestamp('9999-12-30', 'YYYY-MM-DD') NOT NULL,
ts_id TIMESTAMP(6) DEFAULT SYSTIMESTAMP NOT NULL,
PRIMARY KEY(container_id,
metadata_import_id,
job_run_id))
Anweisungen ALTER TABLE:
ALTER TABLE metadata_import_executions ADD CONSTRAINT fk_metadata_import_executions_metadata_imports_3 FOREIGN KEY (container_id,
metadata_import_id) REFERENCES metadata_imports(container_id,
metadata_import_id) ON
DELETE
CASCADE
ALTER TABLE metadata_import_executions ADD CONSTRAINT fk_metadata_import_executions_container_assets_4 FOREIGN KEY (container_id,
job_run_id) REFERENCES container_assets(container_id,
asset_id) ON
DELETE
CASCADE
Tabelle „metadata_enrichments“
Diese Tabelle enthält Informationen zu den Metadaten-Erweiterungen.
Diese Tabelle enthält die folgenden Spalten:
metadata_enrichment_id- Kennung für die Metadatenanreicherung.container_id- Die Kennung des Projekts.metadata_enrichment_name- Der Name der Metadatenanreicherung.
Postgres
Anweisung CREATE TABLE:
create table metadata_enrichments(metadata_enrichment_id varchar(128) not null,
container_id varchar(36) not null,
metadata_enrichment_name varchar(256) not null,
tech_start TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
tech_end TIMESTAMP(6) not null default to_timestamp('9999-12-30', 'YYYY-MM-DD'),
ts_id TIMESTAMP(6) not null default CURRENT_TIMESTAMP,
primary key(container_id,
metadata_enrichment_id))
Anweisung ALTER TABLE:
alter table metadata_enrichments add constraint fk_metadata_enrichments_container_assets_1 foreign key (container_id,
metadata_enrichment_id) references container_assets(container_id,
asset_id) on
delete
cascade on
update
no action
Db2
Anweisung CREATE TABLE:
create table metadata_enrichments(metadata_enrichment_id varchar(128) not null,
container_id varchar(36) not null,
metadata_enrichment_name varchar(256) not null,
tech_start TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row begin,
tech_end TIMESTAMP(12) not null IMPLICITLY HIDDEN generated always as row
end,
ts_id TIMESTAMP(12) not null generated always as transaction start ID,
primary key(container_id,
metadata_enrichment_id),
period SYSTEM_TIME (tech_start,
tech_end) ) ORGANIZE by row
Anweisung ALTER TABLE:
alter table metadata_enrichments add constraint fk_metadata_enrichments_container_assets_1 foreign key (container_id,
metadata_enrichment_id) references container_assets(container_id,
asset_id) on
delete
cascade on
update
no action
Oracle
Anweisung CREATE TABLE:
CREATE TABLE metadata_enrichments(metadata_enrichment_id varchar(128) NOT NULL,
container_id varchar(36) NOT NULL,
metadata_enrichment_name varchar(256) NOT NULL,
tech_start TIMESTAMP(6) DEFAULT SYSTIMESTAMP NOT NULL,
tech_end TIMESTAMP(6) DEFAULT to_timestamp('9999-12-30', 'YYYY-MM-DD') NOT NULL,
ts_id TIMESTAMP(6) DEFAULT SYSTIMESTAMP NOT NULL,
PRIMARY KEY(container_id,
metadata_enrichment_id))
Anweisung ALTER TABLE:
ALTER TABLE metadata_enrichments ADD CONSTRAINT fk_metadata_enrichments_container_assets_1 FOREIGN KEY (container_id,
metadata_enrichment_id) REFERENCES container_assets(container_id,
asset_id) ON
DELETE
CASCADE
Tabelle „job_asset“
Diese Tabelle enthält Informationen zu Job-Assets.
Diese Tabelle enthält die folgenden Spalten:
container_id- Die Kennung des Containers (Katalog oder Projekt), in dem sich das Asset befindet.asset_id- Die Kennung des Datenbestands.version- Gibt die Version des Job-Assets an.job_name- Der Name des Job-Assets.asset_ref_type- Gibt den Typ des Assets an, für das der Auftrag erstellt wird.asset_ref- Kennung für das eigentliche Objekt.schedule- Legt fest, wann der Job ausgeführt wird (z. B. 0 0 * * *).schedule_info- Weitere Metadaten zum Zeitplan, wie z. B. Startdatum und Enddatum.last_run_status_timestamp- Zeitstempel der letzten Ausführung des Auftrags.future_scheduled_runs- Eine Liste oder ein Array der nächsten geplanten Ausführungszeiten für den Job.enable_notifications- Ein boolescher Schalter, um festzulegen, ob Benachrichtigungen bei Änderungen aktiviert werden sollen.project_name- Der Name des Projekts.schedule_id- Eindeutige Kennung des Zeitplans selbst, wodurch mehrere Aufträge auf dieselbe Zeitplanungskonfiguration verweisen können.schedule_creator_id- Kennung des Benutzers, der den Zeitplan erstellt hat.
Postgres
Anweisung CREATE TABLE:
CREATE TABLE "globalschema".job_asset(
container_id varchar(36) NOT NULL,
asset_id varchar(128) NOT NULL,
version integer NOT NULL,
job_name varchar(256) NOT NULL,
asset_ref_type varchar(256),
asset_ref varchar(36),
schedule varchar(36),
schedule_info jsonb,
last_run_status_timestamp timestamp(6),
future_scheduled_runs jsonb,
enable_notifications decimal(1) CHECK (
enable_notifications in (0, 1)
) NOT NULL,
project_name varchar(256) NOT NULL,
schedule_id varchar(36),
schedule_creator_id varchar(128),
tech_start TIMESTAMP(6) NOT NULL DEFAULT CURRENT_TIMESTAMP,
tech_end TIMESTAMP(6) NOT NULL DEFAULT to_timestamp('9999-12-30', 'YYYY-MM-DD'),
ts_id TIMESTAMP(6) NOT NULL DEFAULT CURRENT_TIMESTAMP,
PRIMARY KEY(container_id, asset_id)
)
Db2
Anweisung CREATE TABLE:
CREATE TABLE "globalschema".job_asset(
container_id varchar(36) NOT NULL,
asset_id varchar(128) NOT NULL,
version integer NOT NULL,
job_name varchar(256) NOT NULL,
asset_ref_type varchar(256),
asset_ref varchar(36),
schedule varchar(36),
schedule_info clob,
last_run_status_timestamp timestamp(12),
future_scheduled_runs clob,
enable_notifications decimal(1) CHECK (
enable_notifications in (0, 1)
) NOT NULL,
project_name varchar(256) NOT NULL,
schedule_id varchar(36),
schedule_creator_id varchar(128),
tech_start TIMESTAMP(12) NOT NULL IMPLICITLY HIDDEN GENERATED ALWAYS AS ROW BEGIN,
tech_end TIMESTAMP(12) NOT NULL IMPLICITLY HIDDEN GENERATED ALWAYS AS ROW END,
ts_id TIMESTAMP(12) NOT NULL GENERATED ALWAYS AS TRANSACTION START ID,
PRIMARY KEY(container_id, asset_id),
PERIOD SYSTEM_TIME (tech_start, tech_end)
)
Oracle
Anweisung CREATE TABLE:
CREATE TABLE "globalschema".job_asset(
container_id varchar(36) NOT NULL,
asset_id varchar(128) NOT NULL,
version integer NOT NULL,
job_name varchar(256) NOT NULL,
asset_ref_type varchar(256),
asset_ref varchar(36),
schedule varchar(36),
schedule_info clob,
last_run_status_timestamp timestamp(6),
future_scheduled_runs clob,
enable_notifications decimal(1) NOT NULL CHECK (
enable_notifications in (0, 1)
),
project_name varchar(256) NOT NULL,
schedule_id varchar(36),
schedule_creator_id varchar(128),
tech_start TIMESTAMP(6) DEFAULT SYSTIMESTAMP NOT NULL,
tech_end TIMESTAMP(6) DEFAULT to_timestamp('9999-12-30', 'YYYY-MM-DD') NOT NULL,
ts_id TIMESTAMP(6) DEFAULT SYSTIMESTAMP NOT NULL,
PRIMARY KEY(container_id, asset_id)
)
MS SQL Server
Anweisung CREATE TABLE:
CREATE TABLE "globalschema".job_asset(
container_id varchar(36) NOT NULL,
asset_id varchar(128) NOT NULL,
version integer NOT NULL,
job_name varchar(256) NOT NULL,
asset_ref_type varchar(256),
asset_ref varchar(36),
schedule varchar(36),
schedule_info varchar(MAX),
last_run_status_timestamp DATETIME2,
future_scheduled_runs varchar(MAX),
enable_notifications decimal(1) CHECK (
enable_notifications in (0, 1)
) NOT NULL,
project_name varchar(256) NOT NULL,
schedule_id varchar(36),
schedule_creator_id varchar(128),
tech_start DATETIME2 GENERATED ALWAYS AS ROW START NOT NULL,
tech_end DATETIME2 GENERATED ALWAYS AS ROW END NOT NULL,
ts_id DATETIME2 DEFAULT CURRENT_TIMESTAMP NOT NULL,
CONSTRAINT PK_job_asset_globalschema PRIMARY KEY(container_id, asset_id),
PERIOD FOR SYSTEM_TIME (tech_start, tech_end)
) WITH (
SYSTEM_VERSIONING = ON (
HISTORY_TABLE = "globalschema".hist_job_asset
)
)
Tabelle „job_run_asset“
Diese Tabelle enthält Informationen zur Ausführung von Jobs.
Diese Tabelle enthält die folgenden Spalten:
container_id- Die Kennung des Containers (Katalog oder Projekt), in dem sich das Asset befindet.asset_id- Die Kennung des Datenbestands.version- Gibt die Version des Job-Assets an.job_name- Der Name des Job-Assets.job_ref- Eine Referenz-ID, die mit dem Auftrag verknüpft ist.job_type- Gibt den Typ des Assets an, für das der Joblauf erstellt wird.state- Der Status des Job-Lauf-Assets ( E.g : „Running“, „Completed“, „FAILED“).isScheduledRun- Gibt an, ob der Lauf durch einen Zeitplan oder manuell ausgelöst wurde.project_name- Der Name des Projekts.last_state_change_timestamp- Zeitstempel der letzten Statusaktualisierung.duration- Die Dauer der Auftragsausführung.
Postgres
Anweisung CREATE TABLE:
CREATE TABLE "globalschema".job_run_asset(
container_id varchar(36) NOT NULL,
asset_id varchar(128) NOT NULL,
job_ref varchar(36) NOT NULL,
version integer NOT NULL,
job_name varchar(256) NOT NULL,
job_type varchar(256) NOT NULL,
state varchar(32),
isScheduledRun decimal(1) CHECK (
isScheduledRun in (0, 1)
),
project_name varchar(256) NOT NULL,
last_state_change_timestamp timestamp(6) NOT NULL,
duration integer NOT NULL,
tech_start TIMESTAMP(6) NOT NULL DEFAULT CURRENT_TIMESTAMP,
tech_end TIMESTAMP(6) NOT NULL DEFAULT to_timestamp('9999-12-30', 'YYYY-MM-DD'),
ts_id TIMESTAMP(6) NOT NULL DEFAULT CURRENT_TIMESTAMP,
PRIMARY KEY(container_id, asset_id, job_ref)
)
Db2
Anweisung CREATE TABLE:
CREATE TABLE "globalschema".job_run_asset(
container_id varchar(36) NOT NULL,
asset_id varchar(128) NOT NULL,
job_ref varchar(36) NOT NULL,
version integer NOT NULL,
job_name varchar(256) NOT NULL,
job_type varchar(256) NOT NULL,
state varchar(32),
isScheduledRun decimal(1) CHECK (
isScheduledRun in (0, 1)
),
project_name varchar(256) NOT NULL,
last_state_change_timestamp timestamp(12) NOT NULL,
duration integer NOT NULL,
tech_start TIMESTAMP(12) NOT NULL IMPLICITLY HIDDEN GENERATED ALWAYS AS ROW BEGIN,
tech_end TIMESTAMP(12) NOT NULL IMPLICITLY HIDDEN GENERATED ALWAYS AS ROW END,
ts_id TIMESTAMP(12) NOT NULL GENERATED ALWAYS AS TRANSACTION START ID,
PRIMARY KEY(container_id, asset_id, job_ref),
PERIOD SYSTEM_TIME (tech_start, tech_end)
)
Oracle
Anweisung CREATE TABLE:
CREATE TABLE "globalschema".job_run_asset(
container_id varchar(36) NOT NULL,
asset_id varchar(128) NOT NULL,
job_ref varchar(36) NOT NULL,
version integer NOT NULL,
job_name varchar(256) NOT NULL,
job_type varchar(256) NOT NULL,
state varchar(32),
isScheduledRun decimal(1) CHECK (
isScheduledRun in (0, 1)
),
project_name varchar(256) NOT NULL,
last_state_change_timestamp timestamp(6) NOT NULL,
duration integer NOT NULL,
tech_start TIMESTAMP(6) DEFAULT SYSTIMESTAMP NOT NULL,
tech_end TIMESTAMP(6) DEFAULT to_timestamp('9999-12-30', 'YYYY-MM-DD') NOT NULL,
ts_id TIMESTAMP(6) DEFAULT SYSTIMESTAMP NOT NULL,
PRIMARY KEY(container_id, asset_id, job_ref)
)
MS SQL Server
Anweisung CREATE TABLE:
CREATE TABLE "globalschema".job_run_asset (
container_id varchar(36) NOT NULL,
asset_id varchar(128) NOT NULL,
job_ref varchar(36) NOT NULL,
version integer NOT NULL,
job_name varchar(256) NOT NULL,
job_type varchar(256) NOT NULL,
state varchar(32),
isScheduledRun decimal(1) CHECK (isScheduledRun in (0, 1)),
project_name varchar(256) NOT NULL,
last_state_change_timestamp DATETIME2 NOT NULL,
duration integer NOT NULL,
tech_start DATETIME2 GENERATED ALWAYS AS ROW START NOT NULL,
tech_end DATETIME2 GENERATED ALWAYS AS ROW END NOT NULL,
ts_id DATETIME2 DEFAULT CURRENT_TIMESTAMP NOT NULL,
CONSTRAINT PK_job_run_asset_globalschema
PRIMARY KEY (container_id, asset_id, job_ref),
PERIOD FOR SYSTEM_TIME (tech_start, tech_end)
WITH (SYSTEM_VERSIONING = ON (HISTORY_TABLE = "globalschema".hist_job_run_asset))
);