-
Notifications
You must be signed in to change notification settings - Fork 25.8k
Expose features option in Get Index API #82948
Copy link
Copy link
Closed
Labels
:Data Management/Indices APIsDO NOT USE. Use ":Distributed/Indices APIs" or ":StorageEngine/Templates" instead.DO NOT USE. Use ":Distributed/Indices APIs" or ":StorageEngine/Templates" instead.Team:Data Management (obsolete)DO NOT USE. This team no longer exists.DO NOT USE. This team no longer exists.
Metadata
Metadata
Assignees
Labels
:Data Management/Indices APIsDO NOT USE. Use ":Distributed/Indices APIs" or ":StorageEngine/Templates" instead.DO NOT USE. Use ":Distributed/Indices APIs" or ":StorageEngine/Templates" instead.Team:Data Management (obsolete)DO NOT USE. This team no longer exists.DO NOT USE. This team no longer exists.
Type
Fields
Give feedbackNo fields configured for issues without a type.
The Get Index Api always fetches all mappings, aliases and settings for each index it return results for.
It is possible to filter unwanted information out by using
filter_pathoption, but this only avoids the unneededto be added to the response. The information is still computed on the Elasticsearch side. Especially getting
the mappings is relatively expensive here, since this requires uncompressing certain parts of the cluster state.
Internally the Get Index Api has a functionality called
featuresthat allow certain parts of an index not be computed / fetch to begin with. Unfortunately this option isn't exposed in the rest layer. We should expose this feature to avoid Elasticsearch from doing unnecessary computations for things that the caller of the get index api will not use anyway.