This error condition has the following derived sub error conditions.
Backing table not found for MV/ST with id <parentTableId>
belonging to pipeline <pipelineId>
.
Architecture migration is not supported for HMS pipelines. Pipeline with id <pipelineId>
is not eligible for migration.
Event log not found for pipeline <pipelineId>
Backing table name was unable to be parsed for pipeline id <pipelineId>
. Old backing table name: <oldBackingTableName>
.
Pipeline with id <pipelineId>
failed architecture migration because expected hint key <expectedHintName>
with value <expectedHint>
on table with id <tableId>
does not match generated value <migrationValue>
. If you wish to proceed with the migration, remove the conf 'pipelines.enableDPMForExistingPipeline' and re-run an update using 'pipelines.setMigrationHints'. After running an update with 'pipelines.setMigrationHints', you can re-enable the conf 'pipelines.enableDPMForExistingPipeline'.
Pipeline with id <pipelineId>
failed architecture migration due to missing property <propertyName>
on table with id <tableId>
. If you wish to proceed with the migration, remove the conf 'pipelines.enableDPMForExistingPipeline' and re-run an update using 'pipelines.setMigrationHints'. After running an update with 'pipelines.setMigrationHints', you can re-enable the conf 'pipelines.enableDPMForExistingPipeline'.
Pipeline with id <pipelineId>
was not found in the DLT Database during architecture migration.
Pipeline with id <pipelineId>
was not found in UC during architecture migration.
Pipeline with id <pipelineId>
failed pre-migration validation. Reason: <reason>
Reconciliation query not found on MV/ST with id <parentTableId>
belonging to pipeline <pipelineId>
.
Pipeline with id <pipelineId>
encountered an unexpected error during architecture migration. The error message is: <errorMessage>
.