Skip to content

Commit

Permalink
Re-generate client code using latest OpenSearch API specification (20…
Browse files Browse the repository at this point in the history 
…24-12-30) (opensearch-project#1371)

Signed-off-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
  • Loading branch information
@opensearch-trigger-bot @github-actions
opensearch-trigger-bot[bot] and github-actions[bot] authored Dec 30, 2024
1 parent be6b6d8 commit 0a8d8cd
Show file tree
Hide file tree
Showing 3 changed files with 75 additions and 72 deletions.
6 changes: 3 additions & 3 deletions ...ent/src/generated/java/org/opensearch/client/opensearch/cluster/ClusterStatsResponse.java
View file
Original file line number Diff line number Diff line change
Expand Up @@ -120,7 +120,7 @@ public final String clusterUuid() {
}

/**
* Contains statistics about indices with shards assigned to selected nodes.
* Contains statistics about indexes with shards assigned to selected nodes.
* <p>
* API name: {@code indices}
* </p>
Expand Down Expand Up @@ -274,7 +274,7 @@ public final Builder clusterUuid(String value) {
}

/**
* Contains statistics about indices with shards assigned to selected nodes.
* Contains statistics about indexes with shards assigned to selected nodes.
* <p>
* API name: {@code indices}
* </p>
Expand All @@ -286,7 +286,7 @@ public final Builder indices(@Nullable ClusterIndices value) {
}

/**
* Contains statistics about indices with shards assigned to selected nodes.
* Contains statistics about indexes with shards assigned to selected nodes.
* <p>
* API name: {@code indices}
* </p>
Expand Down
111 changes: 57 additions & 54 deletions java-client/src/generated/java/org/opensearch/client/opensearch/cluster/reroute/Command.java
View file
Original file line number Diff line number Diff line change
Expand Up @@ -89,10 +89,11 @@ public static Command of(Function<Command.Builder, ObjectBuilder<Command>> fn) {
}

/**
* Allocate an empty primary shard to a node. Accepts the index and shard for index name and shard number, and node to allocate the
* shard to. Using this command leads to a complete loss of all data that was indexed into this shard, if it was previously started. If
* a node which has a copy of the data rejoins the cluster later on, that data will be deleted. To ensure that these implications are
* well-understood, this command requires the flag accept_data_loss to be explicitly set to true.
* Allocate an empty primary shard to a node. Accepts <code>index</code> and <code>shard</code> for index name and shard number, and
* <code>node</code> to allocate the shard to. Using this command leads to a complete loss of all data that was indexed into this shard,
* if it was previously started. If a node which has a copy of the data rejoins the cluster later on, that data will be deleted. To
* ensure that these implications are well-understood, this command requires the flag <code>accept_data_loss</code> to be explicitly set
* to true.
* <p>
* API name: {@code allocate_empty_primary}
* </p>
Expand All @@ -103,8 +104,8 @@ public final CommandAllocatePrimaryAction allocateEmptyPrimary() {
}

/**
* Allocate an unassigned replica shard to a node. Accepts index and shard for index name and shard number, and node to allocate the
* shard to. Takes allocation deciders into account.
* Allocate an unassigned replica shard to a node. Accepts <code>index</code> and <code>shard</code> for index name and shard number,
* and <code>node</code> to allocate the shard to. Takes allocation deciders into account.
* <p>
* API name: {@code allocate_replica}
* </p>
Expand All @@ -115,11 +116,11 @@ public final CommandAllocateReplicaAction allocateReplica() {
}

/**
* Allocate a primary shard to a node that holds a stale copy. Accepts the index and shard for index name and shard number, and node to
* allocate the shard to. Using this command may lead to data loss for the provided shard id. If a node which has the good copy of the
* data rejoins the cluster later on, that data will be deleted or overwritten with the data of the stale copy that was forcefully
* allocated with this command. To ensure that these implications are well-understood, this command requires the flag accept_data_loss
* to be explicitly set to true.
* Allocate a primary shard to a node that holds a stale copy. Accepts <code>index</code> and <code>shard</code> for index name and
* shard number, and <code>node</code> to allocate the shard to. Using this command may lead to data loss for the provided shard id. If
* a node which has the good copy of the data rejoins the cluster later on, that data will be deleted or overwritten with the data of
* the stale copy that was forcefully allocated with this command. To ensure that these implications are well-understood, this command
* requires the flag <code>accept_data_loss</code> to be explicitly set to true.
* <p>
* API name: {@code allocate_stale_primary}
* </p>
Expand All @@ -130,11 +131,11 @@ public final CommandAllocatePrimaryAction allocateStalePrimary() {
}

/**
* Cancel allocation of a shard (or recovery). Accepts index and shard for index name and shard number, and node for the node to cancel
* the shard allocation on. This can be used to force resynchronization of existing replicas from the primary shard by cancelling them
* and allowing them to be reinitialized through the standard recovery process. By default only replica shard allocations can be
* cancelled. If it is necessary to cancel the allocation of a primary shard then the allow_primary flag must also be included in the
* request.
* Cancel allocation of a shard (or recovery). Accepts <code>index</code> and <code>shard</code> for index name and shard number, and
* <code>node</code> for the node to cancel the shard allocation on. This can be used to force resynchronization of existing replicas
* from the primary shard by cancelling them and allowing them to be reinitialized through the standard recovery process. By default
* only replica shard allocations can be cancelled. If it is necessary to cancel the allocation of a primary shard then the
* <code>allow_primary</code> flag must also be included in the request.
* <p>
* API name: {@code cancel}
* </p>
Expand All @@ -145,8 +146,8 @@ public final CommandCancelAction cancel() {
}

/**
* Move a started shard from one node to another node. Accepts index and shard for index name and shard number, from_node for the node
* to move the shard from, and to_node for the node to move the shard to.
* Move a started shard from one node to another node. Accepts <code>index</code> and <code>shard</code> for index name and shard
* number, <code>from_node</code> for the node to move the shard from, and <code>to_node</code> for the node to move the shard to.
* <p>
* API name: {@code move}
* </p>
Expand Down Expand Up @@ -246,10 +247,11 @@ public Builder copy() {
}

/**
* Allocate an empty primary shard to a node. Accepts the index and shard for index name and shard number, and node to allocate the
* shard to. Using this command leads to a complete loss of all data that was indexed into this shard, if it was previously started.
* If a node which has a copy of the data rejoins the cluster later on, that data will be deleted. To ensure that these implications
* are well-understood, this command requires the flag accept_data_loss to be explicitly set to true.
* Allocate an empty primary shard to a node. Accepts <code>index</code> and <code>shard</code> for index name and shard number, and
* <code>node</code> to allocate the shard to. Using this command leads to a complete loss of all data that was indexed into this
* shard, if it was previously started. If a node which has a copy of the data rejoins the cluster later on, that data will be
* deleted. To ensure that these implications are well-understood, this command requires the flag <code>accept_data_loss</code> to
* be explicitly set to true.
* <p>
* API name: {@code allocate_empty_primary}
* </p>
Expand All @@ -261,10 +263,11 @@ public final Builder allocateEmptyPrimary(@Nullable CommandAllocatePrimaryAction
}

/**
* Allocate an empty primary shard to a node. Accepts the index and shard for index name and shard number, and node to allocate the
* shard to. Using this command leads to a complete loss of all data that was indexed into this shard, if it was previously started.
* If a node which has a copy of the data rejoins the cluster later on, that data will be deleted. To ensure that these implications
* are well-understood, this command requires the flag accept_data_loss to be explicitly set to true.
* Allocate an empty primary shard to a node. Accepts <code>index</code> and <code>shard</code> for index name and shard number, and
* <code>node</code> to allocate the shard to. Using this command leads to a complete loss of all data that was indexed into this
* shard, if it was previously started. If a node which has a copy of the data rejoins the cluster later on, that data will be
* deleted. To ensure that these implications are well-understood, this command requires the flag <code>accept_data_loss</code> to
* be explicitly set to true.
* <p>
* API name: {@code allocate_empty_primary}
* </p>
Expand All @@ -277,8 +280,8 @@ public final Builder allocateEmptyPrimary(
}

/**
* Allocate an unassigned replica shard to a node. Accepts index and shard for index name and shard number, and node to allocate the
* shard to. Takes allocation deciders into account.
* Allocate an unassigned replica shard to a node. Accepts <code>index</code> and <code>shard</code> for index name and shard
* number, and <code>node</code> to allocate the shard to. Takes allocation deciders into account.
* <p>
* API name: {@code allocate_replica}
* </p>
Expand All @@ -290,8 +293,8 @@ public final Builder allocateReplica(@Nullable CommandAllocateReplicaAction valu
}

/**
* Allocate an unassigned replica shard to a node. Accepts index and shard for index name and shard number, and node to allocate the
* shard to. Takes allocation deciders into account.
* Allocate an unassigned replica shard to a node. Accepts <code>index</code> and <code>shard</code> for index name and shard
* number, and <code>node</code> to allocate the shard to. Takes allocation deciders into account.
* <p>
* API name: {@code allocate_replica}
* </p>
Expand All @@ -304,11 +307,11 @@ public final Builder allocateReplica(
}

/**
* Allocate a primary shard to a node that holds a stale copy. Accepts the index and shard for index name and shard number, and node
* to allocate the shard to. Using this command may lead to data loss for the provided shard id. If a node which has the good copy
* of the data rejoins the cluster later on, that data will be deleted or overwritten with the data of the stale copy that was
* forcefully allocated with this command. To ensure that these implications are well-understood, this command requires the flag
* accept_data_loss to be explicitly set to true.
* Allocate a primary shard to a node that holds a stale copy. Accepts <code>index</code> and <code>shard</code> for index name and
* shard number, and <code>node</code> to allocate the shard to. Using this command may lead to data loss for the provided shard id.
* If a node which has the good copy of the data rejoins the cluster later on, that data will be deleted or overwritten with the
* data of the stale copy that was forcefully allocated with this command. To ensure that these implications are well-understood,
* this command requires the flag <code>accept_data_loss</code> to be explicitly set to true.
* <p>
* API name: {@code allocate_stale_primary}
* </p>
Expand All @@ -320,11 +323,11 @@ public final Builder allocateStalePrimary(@Nullable CommandAllocatePrimaryAction
}

/**
* Allocate a primary shard to a node that holds a stale copy. Accepts the index and shard for index name and shard number, and node
* to allocate the shard to. Using this command may lead to data loss for the provided shard id. If a node which has the good copy
* of the data rejoins the cluster later on, that data will be deleted or overwritten with the data of the stale copy that was
* forcefully allocated with this command. To ensure that these implications are well-understood, this command requires the flag
* accept_data_loss to be explicitly set to true.
* Allocate a primary shard to a node that holds a stale copy. Accepts <code>index</code> and <code>shard</code> for index name and
* shard number, and <code>node</code> to allocate the shard to. Using this command may lead to data loss for the provided shard id.
* If a node which has the good copy of the data rejoins the cluster later on, that data will be deleted or overwritten with the
* data of the stale copy that was forcefully allocated with this command. To ensure that these implications are well-understood,
* this command requires the flag <code>accept_data_loss</code> to be explicitly set to true.
* <p>
* API name: {@code allocate_stale_primary}
* </p>
Expand All @@ -337,11 +340,11 @@ public final Builder allocateStalePrimary(
}

/**
* Cancel allocation of a shard (or recovery). Accepts index and shard for index name and shard number, and node for the node to
* cancel the shard allocation on. This can be used to force resynchronization of existing replicas from the primary shard by
* cancelling them and allowing them to be reinitialized through the standard recovery process. By default only replica shard
* allocations can be cancelled. If it is necessary to cancel the allocation of a primary shard then the allow_primary flag must
* also be included in the request.
* Cancel allocation of a shard (or recovery). Accepts <code>index</code> and <code>shard</code> for index name and shard number,
* and <code>node</code> for the node to cancel the shard allocation on. This can be used to force resynchronization of existing
* replicas from the primary shard by cancelling them and allowing them to be reinitialized through the standard recovery process.
* By default only replica shard allocations can be cancelled. If it is necessary to cancel the allocation of a primary shard then
* the <code>allow_primary</code> flag must also be included in the request.
* <p>
* API name: {@code cancel}
* </p>
Expand All @@ -353,11 +356,11 @@ public final Builder cancel(@Nullable CommandCancelAction value) {
}

/**
* Cancel allocation of a shard (or recovery). Accepts index and shard for index name and shard number, and node for the node to
* cancel the shard allocation on. This can be used to force resynchronization of existing replicas from the primary shard by
* cancelling them and allowing them to be reinitialized through the standard recovery process. By default only replica shard
* allocations can be cancelled. If it is necessary to cancel the allocation of a primary shard then the allow_primary flag must
* also be included in the request.
* Cancel allocation of a shard (or recovery). Accepts <code>index</code> and <code>shard</code> for index name and shard number,
* and <code>node</code> for the node to cancel the shard allocation on. This can be used to force resynchronization of existing
* replicas from the primary shard by cancelling them and allowing them to be reinitialized through the standard recovery process.
* By default only replica shard allocations can be cancelled. If it is necessary to cancel the allocation of a primary shard then
* the <code>allow_primary</code> flag must also be included in the request.
* <p>
* API name: {@code cancel}
* </p>
Expand All @@ -368,8 +371,8 @@ public final Builder cancel(Function<CommandCancelAction.Builder, ObjectBuilder<
}

/**
* Move a started shard from one node to another node. Accepts index and shard for index name and shard number, from_node for the
* node to move the shard from, and to_node for the node to move the shard to.
* Move a started shard from one node to another node. Accepts <code>index</code> and <code>shard</code> for index name and shard
* number, <code>from_node</code> for the node to move the shard from, and <code>to_node</code> for the node to move the shard to.
* <p>
* API name: {@code move}
* </p>
Expand All @@ -381,8 +384,8 @@ public final Builder move(@Nullable CommandMoveAction value) {
}

/**
* Move a started shard from one node to another node. Accepts index and shard for index name and shard number, from_node for the
* node to move the shard from, and to_node for the node to move the shard to.
* Move a started shard from one node to another node. Accepts <code>index</code> and <code>shard</code> for index name and shard
* number, <code>from_node</code> for the node to move the shard from, and <code>to_node</code> for the node to move the shard to.
* <p>
* API name: {@code move}
* </p>
Expand Down
Loading

0 comments on commit 0a8d8cd

Please sign in to comment.