Skip to content

Commit

Permalink
[codegen] update to latest spec
Browse files Browse the repository at this point in the history
  • Loading branch information
l-trotta committed Dec 17, 2024
1 parent 61d01cc commit f60b79f
Show file tree
Hide file tree
Showing 193 changed files with 10,786 additions and 2,350 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -1151,7 +1151,34 @@ public final <TDocument> CompletableFuture<GetSourceResponse<TDocument>> getSour
// ----- Endpoint: health_report

/**
* Returns the health of the cluster.
* Get the cluster health. Get a report with the health status of an
* Elasticsearch cluster. The report contains a list of indicators that compose
* Elasticsearch functionality.
* <p>
* Each indicator has a health status of: green, unknown, yellow or red. The
* indicator will provide an explanation and metadata describing the reason for
* its current health status.
* <p>
* The cluster’s status is controlled by the worst indicator status.
* <p>
* In the event that an indicator’s status is non-green, a list of impacts may
* be present in the indicator result which detail the functionalities that are
* negatively affected by the health issue. Each impact carries with it a
* severity level, an area of the system that is affected, and a simple
* description of the impact on the system.
* <p>
* Some health indicators can determine the root cause of a health problem and
* prescribe a set of steps that can be performed in order to improve the health
* of the system. The root cause and remediation steps are encapsulated in a
* diagnosis. A diagnosis contains a cause detailing a root cause analysis, an
* action containing a brief description of the steps to take to fix the
* problem, the list of affected resources (if applicable), and a detailed
* step-by-step troubleshooting guide to fix the diagnosed problem.
* <p>
* NOTE: The health indicators perform root cause analysis of non-green health
* statuses. This can be computationally expensive when called frequently. When
* setting up automated polling of the API for health status, set verbose to
* false to disable the more expensive analysis logic.
*
* @see <a href=
* "https://www.elastic.co/guide/en/elasticsearch/reference/current/health-api.html">Documentation
Expand All @@ -1166,7 +1193,34 @@ public CompletableFuture<HealthReportResponse> healthReport(HealthReportRequest
}

/**
* Returns the health of the cluster.
* Get the cluster health. Get a report with the health status of an
* Elasticsearch cluster. The report contains a list of indicators that compose
* Elasticsearch functionality.
* <p>
* Each indicator has a health status of: green, unknown, yellow or red. The
* indicator will provide an explanation and metadata describing the reason for
* its current health status.
* <p>
* The cluster’s status is controlled by the worst indicator status.
* <p>
* In the event that an indicator’s status is non-green, a list of impacts may
* be present in the indicator result which detail the functionalities that are
* negatively affected by the health issue. Each impact carries with it a
* severity level, an area of the system that is affected, and a simple
* description of the impact on the system.
* <p>
* Some health indicators can determine the root cause of a health problem and
* prescribe a set of steps that can be performed in order to improve the health
* of the system. The root cause and remediation steps are encapsulated in a
* diagnosis. A diagnosis contains a cause detailing a root cause analysis, an
* action containing a brief description of the steps to take to fix the
* problem, the list of affected resources (if applicable), and a detailed
* step-by-step troubleshooting guide to fix the diagnosed problem.
* <p>
* NOTE: The health indicators perform root cause analysis of non-green health
* statuses. This can be computationally expensive when called frequently. When
* setting up automated polling of the API for health status, set verbose to
* false to disable the more expensive analysis logic.
*
* @param fn
* a function that initializes a builder to create the
Expand All @@ -1182,7 +1236,34 @@ public final CompletableFuture<HealthReportResponse> healthReport(
}

/**
* Returns the health of the cluster.
* Get the cluster health. Get a report with the health status of an
* Elasticsearch cluster. The report contains a list of indicators that compose
* Elasticsearch functionality.
* <p>
* Each indicator has a health status of: green, unknown, yellow or red. The
* indicator will provide an explanation and metadata describing the reason for
* its current health status.
* <p>
* The cluster’s status is controlled by the worst indicator status.
* <p>
* In the event that an indicator’s status is non-green, a list of impacts may
* be present in the indicator result which detail the functionalities that are
* negatively affected by the health issue. Each impact carries with it a
* severity level, an area of the system that is affected, and a simple
* description of the impact on the system.
* <p>
* Some health indicators can determine the root cause of a health problem and
* prescribe a set of steps that can be performed in order to improve the health
* of the system. The root cause and remediation steps are encapsulated in a
* diagnosis. A diagnosis contains a cause detailing a root cause analysis, an
* action containing a brief description of the steps to take to fix the
* problem, the list of affected resources (if applicable), and a detailed
* step-by-step troubleshooting guide to fix the diagnosed problem.
* <p>
* NOTE: The health indicators perform root cause analysis of non-green health
* statuses. This can be computationally expensive when called frequently. When
* setting up automated polling of the API for health status, set verbose to
* false to disable the more expensive analysis logic.
*
* @see <a href=
* "https://www.elastic.co/guide/en/elasticsearch/reference/current/health-api.html">Documentation
Expand Down Expand Up @@ -1814,7 +1895,7 @@ public final CompletableFuture<OpenPointInTimeResponse> openPointInTime(
// ----- Endpoint: ping

/**
* Ping the cluster. Returns whether the cluster is running.
* Ping the cluster. Get information about whether the cluster is running.
*
* @see <a href=
* "https://www.elastic.co/guide/en/elasticsearch/reference/current/index.html">Documentation
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -1168,7 +1168,34 @@ public final <TDocument> GetSourceResponse<TDocument> getSource(
// ----- Endpoint: health_report

/**
* Returns the health of the cluster.
* Get the cluster health. Get a report with the health status of an
* Elasticsearch cluster. The report contains a list of indicators that compose
* Elasticsearch functionality.
* <p>
* Each indicator has a health status of: green, unknown, yellow or red. The
* indicator will provide an explanation and metadata describing the reason for
* its current health status.
* <p>
* The cluster’s status is controlled by the worst indicator status.
* <p>
* In the event that an indicator’s status is non-green, a list of impacts may
* be present in the indicator result which detail the functionalities that are
* negatively affected by the health issue. Each impact carries with it a
* severity level, an area of the system that is affected, and a simple
* description of the impact on the system.
* <p>
* Some health indicators can determine the root cause of a health problem and
* prescribe a set of steps that can be performed in order to improve the health
* of the system. The root cause and remediation steps are encapsulated in a
* diagnosis. A diagnosis contains a cause detailing a root cause analysis, an
* action containing a brief description of the steps to take to fix the
* problem, the list of affected resources (if applicable), and a detailed
* step-by-step troubleshooting guide to fix the diagnosed problem.
* <p>
* NOTE: The health indicators perform root cause analysis of non-green health
* statuses. This can be computationally expensive when called frequently. When
* setting up automated polling of the API for health status, set verbose to
* false to disable the more expensive analysis logic.
*
* @see <a href=
* "https://www.elastic.co/guide/en/elasticsearch/reference/current/health-api.html">Documentation
Expand All @@ -1183,7 +1210,34 @@ public HealthReportResponse healthReport(HealthReportRequest request) throws IOE
}

/**
* Returns the health of the cluster.
* Get the cluster health. Get a report with the health status of an
* Elasticsearch cluster. The report contains a list of indicators that compose
* Elasticsearch functionality.
* <p>
* Each indicator has a health status of: green, unknown, yellow or red. The
* indicator will provide an explanation and metadata describing the reason for
* its current health status.
* <p>
* The cluster’s status is controlled by the worst indicator status.
* <p>
* In the event that an indicator’s status is non-green, a list of impacts may
* be present in the indicator result which detail the functionalities that are
* negatively affected by the health issue. Each impact carries with it a
* severity level, an area of the system that is affected, and a simple
* description of the impact on the system.
* <p>
* Some health indicators can determine the root cause of a health problem and
* prescribe a set of steps that can be performed in order to improve the health
* of the system. The root cause and remediation steps are encapsulated in a
* diagnosis. A diagnosis contains a cause detailing a root cause analysis, an
* action containing a brief description of the steps to take to fix the
* problem, the list of affected resources (if applicable), and a detailed
* step-by-step troubleshooting guide to fix the diagnosed problem.
* <p>
* NOTE: The health indicators perform root cause analysis of non-green health
* statuses. This can be computationally expensive when called frequently. When
* setting up automated polling of the API for health status, set verbose to
* false to disable the more expensive analysis logic.
*
* @param fn
* a function that initializes a builder to create the
Expand All @@ -1200,7 +1254,34 @@ public final HealthReportResponse healthReport(
}

/**
* Returns the health of the cluster.
* Get the cluster health. Get a report with the health status of an
* Elasticsearch cluster. The report contains a list of indicators that compose
* Elasticsearch functionality.
* <p>
* Each indicator has a health status of: green, unknown, yellow or red. The
* indicator will provide an explanation and metadata describing the reason for
* its current health status.
* <p>
* The cluster’s status is controlled by the worst indicator status.
* <p>
* In the event that an indicator’s status is non-green, a list of impacts may
* be present in the indicator result which detail the functionalities that are
* negatively affected by the health issue. Each impact carries with it a
* severity level, an area of the system that is affected, and a simple
* description of the impact on the system.
* <p>
* Some health indicators can determine the root cause of a health problem and
* prescribe a set of steps that can be performed in order to improve the health
* of the system. The root cause and remediation steps are encapsulated in a
* diagnosis. A diagnosis contains a cause detailing a root cause analysis, an
* action containing a brief description of the steps to take to fix the
* problem, the list of affected resources (if applicable), and a detailed
* step-by-step troubleshooting guide to fix the diagnosed problem.
* <p>
* NOTE: The health indicators perform root cause analysis of non-green health
* statuses. This can be computationally expensive when called frequently. When
* setting up automated polling of the API for health status, set verbose to
* false to disable the more expensive analysis logic.
*
* @see <a href=
* "https://www.elastic.co/guide/en/elasticsearch/reference/current/health-api.html">Documentation
Expand Down Expand Up @@ -1842,7 +1923,7 @@ public final OpenPointInTimeResponse openPointInTime(
// ----- Endpoint: ping

/**
* Ping the cluster. Returns whether the cluster is running.
* Ping the cluster. Get information about whether the cluster is running.
*
* @see <a href=
* "https://www.elastic.co/guide/en/elasticsearch/reference/current/index.html">Documentation
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -50,7 +50,8 @@
// typedef: ccr.stats.Request

/**
* Gets all stats related to cross-cluster replication.
* Get cross-cluster replication stats. This API returns stats about
* auto-following and the same shard-level stats as the get follower stats API.
*
* @see <a href="../doc-files/api-spec.html#ccr.stats.Request">API
* specification</a>
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -56,7 +56,8 @@
// typedef: ccr.delete_auto_follow_pattern.Request

/**
* Deletes auto-follow patterns.
* Delete auto-follow patterns. Delete a collection of cross-cluster replication
* auto-follow patterns.
*
* @see <a href=
* "../doc-files/api-spec.html#ccr.delete_auto_follow_pattern.Request">API
Expand Down
Loading

0 comments on commit f60b79f

Please sign in to comment.