docs: update metadata-search config schema#10403
Conversation
Refresh the metadata-search Configuration Reference and sample to match the current `metadata_search` config struct in lakeFS Enterprise: - Collapse split keys (`lakefs.*` / `metadata_settings.*` / `repositories`) into a single top-level `metadata_search` block. - Rename `endpoint` -> `lakefs_mds_endpoint` and `secret_access_key` -> `secret_key`. - Document `period` (60s), `concurrency` (25), and the per-repo `storage_namespace` override. - Note that `max_commits` now defaults to 1000 and must be >= 1 (no longer 0-to-disable). - Add a Validation callout listing the strict checks the service performs at startup. - Note that as of `treeverse/charts` 1.10.0 MDS runs on the `treeverse/lakefs-enterprise` image via `lakefs mds run`. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
📚 Documentation preview at https://oss-pr-10403.docs-lakefs-preview.io/ (Updated: 5/11/2026, 7:58:48 PM - Commit: 83ceb45) |
| Use branch name prefixes (e.g., `feature-*`) to reduce the need for manual updates when new branches are added. | ||
|
|
||
| !!! warning "Validation" | ||
| The Metadata Search service refuses to start unless `lakefs_mds_endpoint` is non-empty and `period`, |
There was a problem hiding this comment.
Not sure I understand the comment. Is this a text suggestion?
There was a problem hiding this comment.
I meant to suggest that we clarify that this condition holds for versions >= 1.10.0
| 3. Install or upgrade the Helm chart with the updated configuration. | ||
|
|
||
| !!! note | ||
| From [`lakefs` Helm chart](https://github.com/treeverse/charts) version **1.10.0**, the Metadata Search |
There was a problem hiding this comment.
What happens when customers already using earlier versions of metadata search upgrade to >= 1.10.0?
There was a problem hiding this comment.
They will need to update their mds config in the chart according to the new configuration fields. It's a small change with minor friction which I believe we can live with while we have a limited number of MDS users (on-prem)
There was a problem hiding this comment.
We need to make sure to include it in the 1.10.0 release notes / change log (probably retroactively)
|
This PR is pending: |
| 3. Install or upgrade the Helm chart with the updated configuration. | ||
|
|
||
| !!! note | ||
| From [`lakefs` Helm chart](https://github.com/treeverse/charts) version **1.10.0**, the Metadata Search |
There was a problem hiding this comment.
We need to make sure to include it in the 1.10.0 release notes / change log (probably retroactively)
| Use branch name prefixes (e.g., `feature-*`) to reduce the need for manual updates when new branches are added. | ||
|
|
||
| !!! warning "Validation" | ||
| The Metadata Search service refuses to start unless `lakefs_mds_endpoint` is non-empty and `period`, |
There was a problem hiding this comment.
I meant to suggest that we clarify that this condition holds for versions >= 1.10.0
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
Closing in favor of: https://github.com/treeverse/docs-next-lakeFS/pull/2 |
Summary
metadata_searchconfig struct in lakeFS Enterprise (pkg/config/config.go).lakefs.*/metadata_settings.*/repositories) into a single top-levelmetadata_searchblock.endpoint→lakefs_mds_endpointandsecret_access_key→secret_key.period(default60s),concurrency(default25), and the per-repostorage_namespaceoverride.max_commitsnow defaults to1000and must be>= 1(no longer0-to-disable).treeverse/chartsversion 1.10.0 the MDS pod runs on thetreeverse/lakefs-enterpriseimage vialakefs mds run, replacing the legacy standalonetreeverse/mdscontainer.Source of truth used:
treeverse/lakeFS-Enterprise pkg/config/config.go(MetadataSearchstruct +Validate) andpkg/config/defaults.go(default values).Test plan
docs/src/datamanagment/metadata-search.mdlocally withmkdocs serveand verify the Configuration Reference and Sample blocks display correctly.MetadataSearchstruct inlakeFS-Enterprise.🤖 Generated with Claude Code