Skip to content

feat: Add Reverse Metadata Agent pipeline type support#26817

Draft
aji-aju wants to merge 2 commits intomainfrom
feat/reverse-metadata-agent
Draft

feat: Add Reverse Metadata Agent pipeline type support#26817
aji-aju wants to merge 2 commits intomainfrom
feat/reverse-metadata-agent

Conversation

@aji-aju
Copy link
Copy Markdown
Collaborator

@aji-aju aji-aju commented Mar 27, 2026

Summary

  • Add reverseMetadataPipeline.json schema with sync toggles (syncDescriptions, syncTags, syncOwners) and filter patterns (databaseFilterPattern, schemaFilterPattern, tableFilterPattern)
  • Add REVERSE_METADATA to pipelineType enum in ingestionPipeline.json
  • Add reverseMetadata command to ingestion CLI (cmd.py)
  • Add deployReverseMetadata method to PipelineServiceClientInterface

Context

Migrating Reverse Metadata from an Application to an Agent (ingestion pipeline). This PR contains the OSS-level schema and interface changes. The corresponding Collate PR contains the workflow implementation, config builder, and CLI integration.

Linked Issue

Test plan

  • Verify JSON schema validation passes for reverseMetadataPipeline.json
  • Verify mvn clean install -DskipTests builds successfully with new schema
  • Verify reverseMetadata CLI command is registered correctly

🤖 Generated with Claude Code

Add OSS-level support for the Reverse Metadata Agent pipeline, enabling
reverse metadata operations (description, tag, owner sync) to run as
an ingestion workflow instead of an application.

- Add reverseMetadataPipeline JSON schema with sync toggles and filter patterns
- Add REVERSE_METADATA pipeline type to ingestionPipeline schema
- Add reverseMetadata command to ingestion CLI (cmd.py)
- Add deployReverseMetadata to PipelineServiceClientInterface

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@github-actions
Copy link
Copy Markdown
Contributor

Hi there 👋 Thanks for your contribution!

The OpenMetadata team will review the PR shortly! Once it has been labeled as safe to test, the CI workflows
will start executing and we'll be able to make sure everything is working as expected.

Let us know if you need any help!

Comment thread ingestion/src/metadata/cmd.py
@gitar-bot
Copy link
Copy Markdown

gitar-bot bot commented Mar 27, 2026

Code Review ✅ Approved 1 resolved / 1 findings

Introduces support for the Reverse Metadata Agent pipeline type by adding it to the CLI dispatch map. The previously identified missing method in RUN_PATH_METHODS has been resolved.

✅ 1 resolved
Bug: REVERSE_METADATA missing from CLI dispatch map (RUN_PATH_METHODS)

📄 ingestion/src/metadata/cmd.py:56 📄 ingestion/src/metadata/cmd.py:60-69 📄 ingestion/src/metadata/cmd.py:169-174 📄 ingestion/src/metadata/cmd.py:264-265
The REVERSE_METADATA command is registered in the enum (line 56) and the argument parser (lines 169-174), but it is not added to the RUN_PATH_METHODS dictionary (lines 60-69) that dispatches commands to handler functions. When a user runs metadata reverse_metadata -c config.yaml, the command will be parsed but silently do nothing because the dispatch logic at line 264 checks if metadata_workflow in RUN_PATH_METHODS and skips execution when the key is missing.

For comparison, AUTO_CLASSIFICATION has a corresponding entry mapping to run_classification.

Options

Display: compact → Showing less information.

Comment with these commands to change:

Compact
gitar display:verbose         

Was this helpful? React with 👍 / 👎 | Gitar

@github-actions
Copy link
Copy Markdown
Contributor

Hi there 👋 Thanks for your contribution!

The OpenMetadata team will review the PR shortly! Once it has been labeled as safe to test, the CI workflows
will start executing and we'll be able to make sure everything is working as expected.

Let us know if you need any help!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants