fix(knowledge): carry the requested entityStatus onto the created page

[Vishnuujain]

fixes: #31754

CreatePage carries entityStatus, but KnowledgePageMapper.createToEntity never copied it and the shared EntityMapper.copy does not either. The value was validated at the API boundary and then dropped before the entity was built, so every page was persisted as Unprocessed no matter what the caller asked for.

One line, matching the existing DataContractMapper precedent. Safe because EntityRepository.setDefaultStatus only fills in Unprocessed when the value is still null, so omitting it still defaults correctly.

Verified live

Creating pages with each of the seven EntityStatus values and reading them back: all seven persist; omitting the field still yields Unprocessed.

Tests

Two: a requested status reaches the entity, and an absent one is left for the repository default.

Found while testing MCP's create_article, but it is a general mapper bug on any POST /v1/contextCenter/pages — split out of #31723 to keep that PR scoped to openmetadata-mcp/.

Greptile Summary

The PR propagates CreatePage.entityStatus through KnowledgePageMapper and adds focused mapper tests.

• Copies the requested status onto the created Page.
• Covers explicit, omitted, and null status inputs at the mapper boundary.

Confidence Score: 4/5

The PR is not yet safe to merge because an omitted entityStatus can still be persisted as Approved instead of receiving the repository's Unprocessed default.

The mapper copies a generated non-null default before repository preparation, while the omission test merely mirrors that request value and therefore does not prevent the previously reported incorrect persisted status.

Files Needing Attention: openmetadata-service/src/main/java/org/openmetadata/service/resources/knowledge/KnowledgePageMapper.java; openmetadata-service/src/test/java/org/openmetadata/service/resources/knowledge/KnowledgePageMapperTest.java

Important Files Changed

Filename	Overview
openmetadata-service/src/main/java/org/openmetadata/service/resources/knowledge/KnowledgePageMapper.java	Propagates the create request's entity status onto the mapped Page.
openmetadata-service/src/test/java/org/openmetadata/service/resources/knowledge/KnowledgePageMapperTest.java	Adds mapper tests for requested, omitted, and explicitly null status values.

_{Reviews (6): Last reviewed commit: "Merge branch 'main' into fix/knowledge-p..." | Re-trigger Greptile}

Context used:

• Knowledge Base — OpenMetadata Service Core: Entities, Resources, Repositories

[github-actions]

✅ PR checks passed

The linked issue has a description and all required Shipping project fields set. Thanks!

[github-actions]

🔴 Playwright Results — workflow failed

Validated commit 079a83bc24a7cd193dc5b143a38baa346fd77953 in Playwright run 32465415833, attempt 1.

✅ 0 passed · ❌ 0 failed · 🟡 0 flaky · ⏭️ 0 skipped · 🧰 0 lifecycle flaky

Pipeline and setup failures (26)

• Seeded fixture preparation finished with status failure.
• The Playwright shard matrix was unexpectedly skipped.
• Shard chromium-01 did not upload a usable Playwright results artifact.
• Shard chromium-02 did not upload a usable Playwright results artifact.
• Shard chromium-03 did not upload a usable Playwright results artifact.
• Shard chromium-04 did not upload a usable Playwright results artifact.
• Shard chromium-05 did not upload a usable Playwright results artifact.
• Shard data-asset-rules-01 did not upload a usable Playwright results artifact.
• Shard domain-isolation-01 did not upload a usable Playwright results artifact.
• Shard global-state-01 did not upload a usable Playwright results artifact.
• Shard ingestion-01 did not upload a usable Playwright results artifact.
• Shard reindex-01 did not upload a usable Playwright results artifact.
• Shard search-01 did not upload a usable Playwright results artifact.
• Shard search-rbac-01 did not upload a usable Playwright results artifact.
• Shard chromium-01 did not upload its execution status.
• Shard chromium-02 did not upload its execution status.
• Shard chromium-03 did not upload its execution status.
• Shard chromium-04 did not upload its execution status.
• Shard chromium-05 did not upload its execution status.
• Shard data-asset-rules-01 did not upload its execution status.
• Shard domain-isolation-01 did not upload its execution status.
• Shard global-state-01 did not upload its execution status.
• Shard ingestion-01 did not upload its execution status.
• Shard reindex-01 did not upload its execution status.
• Shard search-01 did not upload its execution status.
• Shard search-rbac-01 did not upload its execution status.

Performance

⚪ Performance metrics unavailable; see the CI and reporting failures above.

Shard	Passed	Failed	Flaky	Skipped	Lifecycle failed	Lifecycle flaky
⛔ Shard chromium-01	—	—	—	—	—	—
⛔ Shard chromium-02	—	—	—	—	—	—
⛔ Shard chromium-03	—	—	—	—	—	—
⛔ Shard chromium-04	—	—	—	—	—	—
⛔ Shard chromium-05	—	—	—	—	—	—
⛔ Shard data-asset-rules-01	—	—	—	—	—	—
⛔ Shard domain-isolation-01	—	—	—	—	—	—
⛔ Shard global-state-01	—	—	—	—	—	—
⛔ Shard ingestion-01	—	—	—	—	—	—
⛔ Shard reindex-01	—	—	—	—	—	—
⛔ Shard search-01	—	—	—	—	—	—
⛔ Shard search-rbac-01	—	—	—	—	—	—

📦 Download artifacts

How to debug locally

# Download playwright-test-results-<shard> artifact and unzip
npx playwright show-trace path/to/trace.zip    # view trace

[sonarqubecloud]

Quality Gate passed for 'open-metadata-ingestion'

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[github-actions]

🚦 Removed from the merge queue — failed_checks (2026-08-20T14:40:22Z)

Blocked the queue: playwright-summary

• Postgresql PR Playwright E2E Tests — playwright-summary, playwright / playwright-ci (chromium-08)

[github-actions]

🚦 Removed from the merge queue — failed_checks (2026-08-20T21:20:07Z)

Blocked the queue: py-tests-status, py-tests-status

• py-tests — py-tests-status, python / Verify Expected Jobs, python / Integration Tests (shard-2), python / Integration Tests (shard-2), python / Integration Tests (shard-2)
• py-tests-postgres — py-tests-status, python / Verify Expected Jobs, python / Integration Tests (shard-2), python / Integration Tests (shard-2), python / Integration Tests (shard-2)

[gitar-bot]

Code Review ✅ Approved

Propagates the requested entityStatus through the KnowledgePageMapper and includes focused unit tests covering explicit status propagation and omitted values. No issues found.

Options

Display: compact → Showing less information.

Comment with these commands to change the behavior for this request:

Compact

gitar display:verbose

_{Was this helpful? React with 👍 / 👎 | Powered by Gitar — free for open source}