Skip to content

feat: populate event/document metadata capabilities + tenant-scoped document diagnostics (9.12.0-alpha.1)#4790

Merged
jeremydmiller merged 3 commits into
masterfrom
feat/475-populate-event-document-metadata-capabilities
Jun 27, 2026
Merged

feat: populate event/document metadata capabilities + tenant-scoped document diagnostics (9.12.0-alpha.1)#4790
jeremydmiller merged 3 commits into
masterfrom
feat/475-populate-event-document-metadata-capabilities

Conversation

@jeremydmiller

Copy link
Copy Markdown
Member

Implements the JasperFx 2.17.0 monitoring-descriptor surfaces for store-aware consoles (CritterWatch). Part of the Event Store / Document Store Explorer work.

Changes

  • Populate EventStoreUsage.EventMetadata (from the event MetadataConfig) and DocumentStoreUsage.DocumentMetadata (from per-document metadata) in the store usage descriptors (Wrap DDL scripts generated by WritePatch() with a transaction #475) — so a console can gate query facets by what the store actually captures.
  • Tenant-scope IDocumentStoreDiagnostics.QueryDocumentsAsync via DocumentQueryOptions.TenantId: database-per-tenant resolves the tenant database (Tenancy.FindOrCreateDatabase); conjoined tenancy filters the tenant_id column; null keeps the prior default-tenant behaviour.
  • Bump to 9.12.0-alpha.1; JasperFx.* pins → 2.17.0.

Depends on

JasperFx 2.17.0 (JasperFx/jasperfx#477) — the abstraction + DocumentQueryOptions.TenantId. Publish that first; CI here stays red until 2.17.0 is on NuGet.

🤖 Generated with Claude Code

jeremydmiller and others added 3 commits June 26, 2026 19:02
…tore usage descriptors

Map MetadataConfig (events) and per-document metadata (documents) onto the
new JasperFx.Events/JasperFx descriptor capability blocks so store-aware
consumers (CritterWatch) can gate query facets by what the store actually
persists. Stream/document common facets keep the descriptor's default true;
event + document opt-in columns reflect the live config.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Honour DocumentQueryOptions.TenantId: database-per-tenant stores resolve the
tenant's physical database (Tenancy.FindOrCreateDatabase); conjoined-tenancy
mappings stay in the default database with a tenant_id filter. Null tenant
keeps the prior default-tenant behaviour.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Consumes the JasperFx 2.17.0 metadata-capabilities + DocumentQueryOptions.TenantId
APIs this branch implements (EventMetadata/DocumentMetadata population +
tenant-scoped QueryDocumentsAsync). Prerelease pending the JasperFx 2.17.0
publish.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@jeremydmiller
jeremydmiller merged commit aadc43c into master Jun 27, 2026
9 of 20 checks passed
@jeremydmiller
jeremydmiller deleted the feat/475-populate-event-document-metadata-capabilities branch June 27, 2026 12:23
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