Requests the detailed status of the current operation (by default) or a prior
cluster operation specified by input parameter history_index . Returns details
on the requested cluster operation.
The response will also indicate how many cluster operations are stored in the
history.
Indicates which cluster operation to retrieve. Use 0 for the most recent. The default value is 0.
Optional parameters. The default value is an empty map ( {} ).
Output Parameter Description The Kinetica server embeds the endpoint response inside a standard response structure which contains status information and the actual response to the query. Here is a description of the various fields of the wrapper:
Empty if success or an error message
‘admin_show_cluster_operations_response’ or ‘none’ in case of an error
This embedded JSON represents the result of the /admin/show/cluster/operations endpoint: The index of this cluster operation in the reverse-chronologically sorted list of operations, where 0 is the most recent operation.
Number of cluster operations executed to date.
Whether this cluster operation is currently in progress or not. The supported values are: The start time of the cluster operation.
The end time of the cluster operation, if completed.
The endpoint that initiated the cluster operation.
The schema for the original request.
Overall success status of the operation.
OK : The operation was successful, or, if still in progress, the operation is successful so far.ERROR : An error occurred executing the operation. Whether a user stopped this operation at any point while in progress. The supported values are: Percent complete of this entire operation.
Whether this operation was a dry run. The supported values are: Updates and error messages if any.
Whether adding ranks is (or was) part of this operation. The supported values are: If this was a rank-adding operation, the add-specific status of the operation. The supported values are:
NOT_STARTED
IN_PROGRESS
INTERRUPTED
COMPLETED_OK
ERROR
The rank numbers of the ranks currently being added, or the rank numbers that were added if the operation is complete.
The host IP addresses of the ranks being added, in the same order as the output parameter ranks_being_added list.
add_ranks_percent_complete Current percent complete of the add ranks operation.
Whether removing ranks is (or was) part of this operation. The supported values are: If this was a rank-removing operation, the removal-specific status of the operation. The supported values are:
NOT_STARTED
IN_PROGRESS
INTERRUPTED
COMPLETED_OK
ERROR
The ranks being removed, or that have been removed if the operation is completed.
remove_ranks_percent_complete Current percent complete of the remove ranks operation.
Whether data and/or shard rebalancing is (or was) part of this operation. The supported values are: Whether rebalancing of unsharded data is (or was) part of this operation. The supported values are: rebalance_unsharded_data_status If this was an operation that included rebalancing unsharded data, the rebalancing-specific status of the operation. The supported values are:
NOT_STARTED
IN_PROGRESS
INTERRUPTED
COMPLETED_OK
ERROR
unsharded_rebalance_percent_complete Percentage of unsharded tables that completed rebalancing, out of all unsharded tables to rebalance.
Whether rebalancing of sharded data is (or was) part of this operation. The supported values are: Version of the shard array that is (or was) being rebalanced to. Each change to the shard array results in the version number incrementing.
rebalance_sharded_data_status If this was an operation that included rebalancing sharded data, the rebalancing-specific status of the operation. The supported values are:
NOT_STARTED
IN_PROGRESS
INTERRUPTED
COMPLETED_OK
ERROR
Number of shards that will change as part of rebalance.
sharded_rebalance_percent_complete Percentage of shard keys, and their associated data if applicable, that have completed rebalancing.
Empty string in case of an error. 
