correction in schema kind authority for manifest by reference
Type of change
-
Bug Fix -
Feature
Does this introduce a change in the core logic?
- [Yes]
Does this introduce a change in the cloud provider implementation, if so which cloud?
-
AWS -
Azure -
GCP -
IBM
Updates description?
This is related to issue -ingestion-dags#108 (closed)
Encountered an error - "Schema is not present" from Dataset service while running the manifest by reference DAG
After analysis we observed there are few codes where the 'Kind' of the schema is constructed with data-partition-id (which is 'opendes' in our case). But the schema which is present in our DB, there the 'Kind' actually starts with 'authority' (which is 'osdu' in our case). Hence the error.
So code changes done so that this value is fetched from a new DAG environment variable named "kind_authority" instead of 'data-partition-id'.