You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When we are running snowflake ingestion, it is failing with following error
| OpenMetadata | CreateTableRequest [ADM_SF_TRT_REPORT] | Failed to ingest CreateTableRequest [ADM_SF_TRT_REPORT] due to api request failure: Invalid column name found in table constraint | Traceback (most recent call last):
But when we look into table, which is looking fine create or replace TABLE ADM_INST.ADM_SF_TRT_REPORT (
TRT_NAME VARCHAR(100) NOT NULL,
GRP_NAME VARCHAR(100) NOT NULL,
SUBJECT VARCHAR(100) NOT NULL,
TRT_CREATED TIMESTAMP_NTZ(9) DEFAULT CAST(CURRENT_TIMESTAMP() AS TIMESTAMP_NTZ(9)),
TRT_BEGIN TIMESTAMP_NTZ(9) DEFAULT CAST(CURRENT_TIMESTAMP() AS TIMESTAMP_NTZ(9)),
TRT_END TIMESTAMP_NTZ(9),
TRT_NEXT_RUN TIMESTAMP_NTZ(9) DEFAULT CAST(CURRENT_TIMESTAMP() AS TIMESTAMP_NTZ(9)),
TRT_ITERATION VARCHAR(100),
TRT_PERIOD NUMBER(38,0),
constraint TRT_REPORT_UK unique (TRT_NAME)
To Reproduce
Screenshots or steps to reproduce
Expected behavior
Our expected behavior is load metadata without fail
we are running the ingestion pod that included with the OpenMetadata helm image. There is an option to run the ingestion externally which is where you could have a difference in version between OpenMetadata and the ingestion component. But in our case they should be matched based on the helm version. Here are the details:
Affected module
Does Ingestion Framework
Describe the bug
When we are running snowflake ingestion, it is failing with following error
| OpenMetadata | CreateTableRequest [ADM_SF_TRT_REPORT] | Failed to ingest CreateTableRequest [ADM_SF_TRT_REPORT] due to api request failure: Invalid column name found in table constraint | Traceback (most recent call last):
But when we look into table, which is looking fine
create or replace TABLE ADM_INST.ADM_SF_TRT_REPORT (
TRT_NAME VARCHAR(100) NOT NULL,
GRP_NAME VARCHAR(100) NOT NULL,
SUBJECT VARCHAR(100) NOT NULL,
TRT_CREATED TIMESTAMP_NTZ(9) DEFAULT CAST(CURRENT_TIMESTAMP() AS TIMESTAMP_NTZ(9)),
TRT_BEGIN TIMESTAMP_NTZ(9) DEFAULT CAST(CURRENT_TIMESTAMP() AS TIMESTAMP_NTZ(9)),
TRT_END TIMESTAMP_NTZ(9),
TRT_NEXT_RUN TIMESTAMP_NTZ(9) DEFAULT CAST(CURRENT_TIMESTAMP() AS TIMESTAMP_NTZ(9)),
TRT_ITERATION VARCHAR(100),
TRT_PERIOD NUMBER(38,0),
constraint TRT_REPORT_UK unique (TRT_NAME)
To Reproduce
Screenshots or steps to reproduce
Expected behavior
Our expected behavior is load metadata without fail
we are running the ingestion pod that included with the OpenMetadata helm image. There is an option to run the ingestion externally which is where you could have a difference in version between OpenMetadata and the ingestion component. But in our case they should be matched based on the helm version. Here are the details:
for ingestion pod:
OS: VERSION="Debian GNU/Linux 12 (bookworm)"
Python version: 3.10.14
openmetadata-ingestion==1.6.3.2
openmetadata_managed_apis==1.6.3.2
This is what comes with tehir standard image for 1.6.3
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: