Skip to main content

​
Applications & Automation

Four installed applications have their stored configuration rewritten by the 2.0.0 migration. If you manage application configuration as code, read this before you replay it.

​
Search Indexing app configuration fields removed

Breaking. Affects scripted reindex triggers and infrastructure-as-code.
In 2.0 reindex always recreates the index and distributed indexing is always used. Supporting infrastructure added by the migration:
Any automation that triggers a reindex with {"recreateIndex": false} — for example an “incremental reindex” job — must drop the field. There is no incremental mode in 2.0.
New diagnostics ship alongside: reindex-drift and index-health checks in /v1/system/validate, plus a cluster-fitness diagnostic.

​
RDF Index app defaults changed

Behavioural — the migration overwrites your settings.
Incremental RDF indexing produced unbounded triple growth because relationship-removal paths were not fully reconciled. With a per-run clear the dataset always converges to the relational state, and a weekly cadence keeps per-run cost from saturating the triple store. The entities reset is a safety measure — with a full rebuild issuing a clear before indexing, a narrowed entity subset would wipe triples for entity types still present in the database.
Your entities subset is not preserved. Reapply it after the migration if you need partial RDF indexing, understanding that the following run will still clear first.

​
RDF configuration defaults

RDF inference is now off. SPARQL queries relying on inferred triples return fewer results. Set RDF_INFERENCE_ENABLED=true to restore 1.13 behaviour.

​
Data Insights app: the dataQuality module is removed

Breaking. A stored configuration containing moduleConfiguration.dataQuality prevents DataInsightsApplication from deserialising at startup. See Data Quality.

​
MCP application configuration removed

Breaking. Affects MCP deployments.
MCP configuration lives solely in the mcpConfiguration setting. The application-level copy — which no code read — is dropped by the migration and the now-empty configure step is hidden in the UI.
Configure MCP through Settings → MCP, not through the application’s configuration.

​
Runtime-only fields stripped from stored application data

Behavioural and security-relevant.
openMetadataServerConnection and privateConfiguration were being persisted into application rows and version history. They are runtime-only and are removed by the migration. Separately, 2.0 stops exposing the application bot JWT and privateConfiguration secrets in API responses.
If your tooling read the application bot token out of /v1/apps/..., obtain it through the bot API instead.

​
Application configuration union changed

Behavioural. Affects generated models and strict validators.
The appConfig union drops the three Collate AI agent configurations and gains a permissive terminal branch. Branch indexes shift, so generated unions that key on position must be regenerated rather than hand-patched.

​
New tenant-wide application configuration setting

Additive.
settingType: "appConfiguration" is backed by a new schema:
It is seeded from YAML or environment on first boot, then database-backed and admin-mutable at runtime — YAML is ignored once a database row exists. Precedence is user preference → persona app mode → tenant default. See UI, Personas & Customization.

​
MCP tool contracts

Breaking for MCP clients that parse responses. No tools are removed, but 7 tools are added and 15 change.

​
New tools

create_context_memory, find_context, get_asset_context, get_company_context, get_knowledge_content, get_persona_context and search_company_context — all Context Center and AI-context tools.

​
Changed tools

create_classification, create_data_product, create_domain, create_glossary, create_glossary_term, create_lineage, create_metric, create_tag, create_test_case, get_entity_lineage, get_test_definitions, patch_entity, root_cause_analysis, search_metadata and semantic_search.

​
Contract changes that will break clients

​
Other MCP changes

  • Tools are annotated with title, read-only, destructive and open-world hints; create_lineage is marked destructive.
  • get_entity_details is authorized against the resolved entity.
  • Create tools can set custom properties, and create-overwrites are re-authorized.
  • SAML SSO is supported in the MCP OAuth flow; public clients are no longer issued a client secret.
  • Content negotiation prefers application/json when the client accepts both JSON and SSE.
  • Tool-call usage is tracked via /v1/mcp/usage.
Re-run your MCP client against 2.0 before rolling out. Anything that counted results with a size: 0 aggregation query, or paged with a bespoke offset, must change.

​
CSV import and export become tracked background jobs

Behavioural. Affects CSV automation and the UI.
background_jobs gains progress, total, result, error, message, cancelRequested and completedAt, plus a new background_job_logs table. jobType gains CSV_IMPORT, CSV_EXPORT and AUDIT_EXPORT; status gains CANCELLED. In 1.13 async CSV progress was delivered only over WebSocket — a client without a live socket had no way to observe the job. 2.0 makes jobs pollable and downloadable, and the UI surfaces them in a Background jobs tray. Async entity restore is also available via PUT /v1/{entityType}/restore?async=true, and entity metrics gain full CSV import and export support.

​
Concurrency limits for background fan-out

Additive. New openmetadata.yaml block.
Prevents background fan-out from exhausting the request connection pool. Tune down if you see connection-pool starvation during reindex or Data Insights runs.

​
Search & vector infrastructure

Additive.

​
Cache

Additive. New admin endpoints: GET /v1/system/cache/keys, POST /v1/system/cache/invalidate and POST /v1/system/cache/invalidate/entity. The cache default is unchanged — set CACHE_PROVIDER=redis to enable the Redis L2 cache, which falls back to a no-op provider if Redis is unreachable at startup.