RemoveIndex
Removes the index of the specified kind on an entity or connection property. Other kinds on that property are retained. Removing an absent index succeeds. Indexes on system properties are managed in the same way as other property indexes. Removing an index does not remove the property or its values.
Requires indexes.delete permission. No input or output blobs are used.
Parameters
An exact node target is its type and class, for example {"target":"image","class":"Photos"}.
For a connection, class names the source class, connection class, and destination class. target supplies the corresponding endpoint types.
{
"class": {"src": "People", "connection": "AppearsIn", "dst": "Photos"},
"target": {"src": "entity", "dst": "image"}
}
Metadata mutations require all five values for a connection. Class names are nonempty, cannot begin with _, and are matched without case sensitivity. Index selectors also include property and kind. With GetIndexes and GetAggregates you can supply only the fields you want to match, such as {"class":{"connection":"AppearsIn"},"target":{"dst":"image"}}.
property and kind are required. Allowed kinds are ordered, trigram, similarity, fulltext, type, array, flat, ivf, hnsw, and acorn.
Removing a vector index leaves descriptors and their raw binary values intact. Its index identity is retired; bounded physical reclamation can continue after the command succeeds. A recreated definition gets a new identity.
Response and recovery
Success returns status: 0, including when the selected index is absent. Invalid selectors or unknown kinds fail validation. See Responses for error envelopes and transaction rollback behavior.
Examples
Remove the ordered index on the “name” property of “Person”:
[{
"RemoveIndex": {
"kind": "ordered",
"target": "entity",
"class": "Person",
"property": "name"
}
}]