Skip to content

Expose document collection metadata in EntitiesResponse - #3

Open
vogti wants to merge 3 commits into
mainfrom
codex/document-entity-metadata
Open

vogti wants to merge 3 commits into
mainfrom
codex/document-entity-metadata

Conversation

@vogti

@vogti vogti commented Nov 6, 2026 •

Copy link
Copy Markdown
Member

Document entities currently have an empty metadata message. Define collection identity, inferred field paths/types/optionality, an optional JSON sample, and available document indexes using the existing Entity oneof and the requested field numbers.

Comments distinguish observations from an enforced schema, specify escaped literal field-path separators, and document conservative per-field uniqueness for compound indexes. Python contract tests compile the actual protocol and cover every field, serialization, optional presence, the Entity oneof, and legacy readers. A dedicated GitHub Actions workflow runs them.

Validation: 5 Python contract tests passed locally and in GitHub Actions. Companion validation: full Java server/plugin build, 10 Java tests, and 15 live Python tests against HSQLDB-backed document collections and real MongoDB indexes all passed.

Companions: polypheny/Polypheny-DB#576 and polypheny/Polypheny-Connector-Python#4.

This PR does not publish a release. Companion builds pin this protocol revision and overlay only namespace metadata onto Prism 1.9 to preserve its existing value wire format.

Final GitHub validation: 2/2 checks successful on ac57da2459071234c4cacc6836e3f4ca6f13f101; no pending or failed checks.

JDBC 3.x companion: polypheny/Polypheny-JDBC-Driver#21.

This branch has not been deployed

No deployments
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.

1 participant