docs: add metric engine sparse primary key encoding configuration #2211
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What's Changed in this PR
Documents the metric engine's sparse primary key encoding feature enabled by default in GreptimeDB PR #7195.
Configuration Documentation (
configuration.md)sparse_primary_key_encodingoption (default:true)Metric Engine Documentation (
metric-engine.md)Applied to both nightly and v1.0 documentation versions in English and Chinese (中文).
Chinese Documentation (中文文档)
sparse_primary_key_encodingoptionChecklist
Please confirm that all corresponding versions of the documents have been revised.
Please ensure that the content in
sidebars.tsmatches the current document structure when you changed the document structure.This change requires follow-up update in localized docs.
Fixes Update docs for feat(metric)!: enable sparse primary key encoding by default #2200
Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.