Skip to content

Handle glossaryStatus Import Case-Insensitively in Glossary CSV Import #29510

Description

@Prajwal214

Affected module

Governance (Glossary / Classification / Domains)

Describe the bug

While importing Glossary Terms via CSV, users provided valid status values in lowercase (draft, approved), but the import failed without a clear error message. The import succeeded only after updating the values to the exact case expected by the system.

To Reproduce

  • Draft, Approved, Deprecated → Import succeeds.
  • draft, approved, deprecated → Import fails or does not process correctly.

Expected behavior

  • glossaryStatus should be parsed in a case-insensitive manner.
  • The importer should accept any casing, for example:
    • Draft, draft, DRAFT
    • Approved, approved, APPROVED
    • Deprecated, deprecated, DEPRECATED
  • Invalid values should continue to return a clear validation error.

OS

No response

Python version

No response

OpenMetadata version

1.13.0

OpenMetadata Ingestion package version

No response

Additional context

No response

Pre-submission checklist

  • I searched for duplicate issues.
  • I removed credentials, hostnames, emails, and other sensitive data from logs and config.

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

Fields

No fields configured for Bug.

Projects

Status
Done ✅
Status
Done ✅

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions