Repository navigation
Report vectordb_document usage in _xpack/usage - #152780
Merged
elasticsearchmachine merged 7 commits intoJul 3, 2026
Merged
elasticsearchmachine merged 7 commits into
elasticsearchmachine merged 7 commits into
Conversation
Add a vectordb_document section to the _xpack/usage API,
following the same pattern already used for logsdb and
time_series. VectorDBDocumentUsageTransportAction counts
indices with index.mode=vectordb_document from cluster state
and fetches aggregated doc counts via IndexModeStatsActionType.
Sample response with no vectordb_document indices:
{
"vectordb_document": {
"available": true,
"enabled": true,
"indices_count": 0,
"num_docs": 0
}
}
Sample response with one index holding 2 documents:
{
"vectordb_document": {
"available": true,
"enabled": true,
"indices_count": 1,
"num_docs": 2
}
}
Collaborator
|
Pinging @elastic/es-search-relevance (Team:Search Relevance) |
benwtrent
reviewed
Jul 2, 2026
VectorDBDocumentFeatureSetUsage is a new named writeable, so it needs its own TransportVersion instead of reusing minimumCompatible() or the unrelated index-mode constant. Also drop the redundant IndexMetadata scan for indices_count: IndexModeStatsActionType's response already carries numIndices from the same fan-out used for num_docs, so there is no need for a second, separate pass over cluster state.
Collaborator
|
Hi @mayya-sharipova, I've created a changelog YAML for you. |
Contributor
🔍 Preview links for changed docs⏳ Building and deploying preview... View progress This comment will be updated with preview links when the build is complete. |
Contributor
ℹ️ Important: Docs version tagging👋 Thanks for updating the docs! Just a friendly reminder that our docs are now cumulative. This means all 9.x versions are documented on the same page and published off of the main branch, instead of creating separate pages for each minor version. We use applies_to tags to mark version-specific features and changes. Expand for a quick overviewWhen to use applies_to tags:✅ At the page level to indicate which products/deployments the content applies to (mandatory) What NOT to do:❌ Don't remove or replace information that applies to an older version 🤔 Need help?
|
benwtrent
approved these changes
Jul 2, 2026
The yaml test asserted on the vectordb_document usage section unconditionally, which would fail if it ever ran against a mixed cluster with nodes predating this feature. Register a test-only NodeFeature and require it, so the test skips cleanly instead. Nothing in production code branches on this feature, so it belongs in getTestFeatures(), not getFeatures().
OperatorPrivilegesIT requires every action to be declared either operator-only or non-operator. The new usage action was missing, matching every other _xpack/usage feature action.
…ndex-mode-stats # Conflicts: # server/src/main/resources/transport/upper_bounds/9.5.csv
szybia
added a commit
to szybia/elasticsearch
that referenced
this pull request
Jul 3, 2026
…uisition * upstream/main: (65 commits) Use forceEvictEntries for all forceEvict methods (elastic#152846) [ESQL] Normalize local StorageObject path for stats reconcile (elastic#152837) Report vectordb_document usage in _xpack/usage (elastic#152780) Mute org.elasticsearch.common.lucene.LuceneTests testSearchWithoutBulkScorer elastic#152898 Make DiskBBQ CentroidSupplier generic in the indexing method (elastic#152863) AGGS: Prevent OOM in test (elastic#152690) [CI] Fix bc upgrade disk size (elastic#152895) Mute org.elasticsearch.xpack.transform.integration.TransformIT testStopWaitForCheckpoint elastic#149663 Always report script queries as maximum cost (elastic#152856) test(tsdb): cover `ES95` ordinal doc values (elastic#152802) Skip semantic_field source yaml tests in release (elastic#152852) Mute org.elasticsearch.xpack.esql.action.NdJsonScalarObjectConflictIT testSkipRowPolicyNullFillsAndWarnsClient elastic#152891 [ESQL] Async STOP / cancel / DELETE contract for EXTERNAL queries (elastic#152585) Unmute rolling upgrade tests (elastic#152715) [ESQL] Fix ExternalSourceExec BWC serialization test types (elastic#152836) Add AllocateReshardSplitTargetPrimaryCommand (elastic#152806) [ESQL] Reconcile temporal stat units in cross-file merge (elastic#152859) ES|QL: error on `match` options w/ runtime field (elastic#152597) Improve allocation explain API for canRemain decisions (elastic#152121) [Inference API] Remove fallbackRegion from RegionPolicy (elastic#152798) ...
burqen
pushed a commit
to burqen/elasticsearch
that referenced
this pull request
Jul 7, 2026
Add a vectordb_document section to the _xpack/usage API, following the
same pattern already used for logsdb and time_series.
VectorDBDocumentUsageTransportAction counts indices with
index.mode=vectordb_document from cluster state and fetches aggregated
doc counts via IndexModeStatsActionType.
Sample response with no vectordb_document indices:
```js
{
"vectordb_document": {
"available": true,
"enabled": true,
"indices_count": 0,
"num_docs": 0
}
}
```
Sample response with one index holding 2 documents:
```
{
"vectordb_document": {
"available": true,
"enabled": true,
"indices_count": 1,
"num_docs": 2
}
}
```
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Add a vectordb_document section to the _xpack/usage API, following the same pattern already used for logsdb and time_series. VectorDBDocumentUsageTransportAction counts indices with index.mode=vectordb_document from cluster state and fetches aggregated doc counts via IndexModeStatsActionType.
Sample response with no vectordb_document indices:
Sample response with one index holding 2 documents: