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
Affected module
Does it impact the UI, backend or Ingestion Framework? -- Ingestion
Describe the bug
A clear and concise description of what the bug is.
-- When using the inspector.get_unique_constraints() function to retrieve unique constraints for a DB2 table, the function returns columns that do not exist in the table. Specifically, the function returns a prjid column that is not listed in the actual table columns returned by inspector.get_columns().
To Reproduce
Screenshots or steps to reproduce
Use the inspector.get_unique_constraints() method to retrieve unique constraints for a DB2 table.
Compare the columns listed in the unique constraints against the actual columns retrieved by inspector.get_columns().
Observe that the inspector.get_unique_constraints() returns columns like prjid that do not exist in the table.
Expected behavior
A clear and concise description of what you expected to happen.
Affected module
Does it impact the UI, backend or Ingestion Framework? -- Ingestion
Describe the bug
A clear and concise description of what the bug is.
-- When using the inspector.get_unique_constraints() function to retrieve unique constraints for a DB2 table, the function returns columns that do not exist in the table. Specifically, the function returns a prjid column that is not listed in the actual table columns returned by inspector.get_columns().
To Reproduce
Screenshots or steps to reproduce
Expected behavior
A clear and concise description of what you expected to happen.
Version:
openmetadata-ingestion[docker]==XYZ
] v.1.5.5Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: