rebuild_index
Use the rebuild index operation to rebuild an existing vector index with updated parameters.
Recreates the index, optionally with new configuration parameters. Useful for optimizing search performance or adjusting to changed data distributions. The rebuild runs asynchronously as a background job.
Parameters
| Parameter | Type | Value Range | Required | Default | Description | Notes |
|---|---|---|---|---|---|---|
table_name |
str |
Valid vector table identifier | Yes | No default | Name of the vector table whose index will be rebuilt. | Table must exist in the database schema. |
index_params |
dict |
Object or NULL | No | None | Rebuild configuration for vector indexes, metadata indexes, or both. | Use index_type to scope the rebuild to vector, metadata, or all; parallel_creation controls the optional parallel DDL degree. |
debug_flags |
dict |
Object or NULL | No | None | Debug or tracing flags for detailed logging. | Optional; omit unless diagnostics are needed. |
Raises InvalidTableNameFormatError is raised when the table name is invalid.
Rebuild all indexes with parallel DDL
response = client.rebuild_index(
table_name='products',
index_params={
'index_type': 'all',
'parallel_creation': 4
}
)
print(response)
Example response
{
"job_creator": "VECTOR3",
"job_name": "VECDB_REBUILD_INDEX_575FD66FCCF405F1E063324946644650",
"job_type": "PLSQL_BLOCK",
"operation": "REBUILD",
"start_date": "2026-07-27T07:11:36.741624Z",
"state": "SCHEDULED",
"links": [
{
"rel": "collection",
"href": ".../vecdb/vector-indexes/jobs/"
},
{
"rel": "self",
"href": ".../vecdb/vector-indexes/jobs/vecdb_rebuild_index_.../"
},
{
"rel": "related",
"href": ".../vecdb/vector-indexes/jobs/vecdb_rebuild_index_.../jobfile"
}
]
}
Return type JobResponse
Returns JSON response containing the rebuild job ID and status.