-
Notifications
You must be signed in to change notification settings - Fork 29
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Using OpenSearch Cat API Response Formats
- Loading branch information
Showing
1 changed file
with
123 additions
and
0 deletions.
There are no files selected for viewing
123 changes: 123 additions & 0 deletions
123
_posts/2024/2024-07-02-using-opensearch-cat-api-response-formats.markdown
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,123 @@ | ||
--- | ||
layout: post | ||
title: "Using OpenSearch Cat API Response Formats" | ||
date: 2024-07-02 | ||
tags: [opensearch] | ||
comments: true | ||
--- | ||
I've been working on the new [OpenSearch OpenAPI Specification](https://github.com/opensearch-project/opensearch-api-specification) that aims to properly document OpenSearch RESTful APIs. The spec is to be used to [auto-generate OpenSearch clients](https://github.com/opensearch-project/opensearch-clients/issues/19) in Python, Java, .NET, etc. One of the neat features of the API specification repo is [a set of declarative YAML integration tests](https://github.com/opensearch-project/opensearch-api-specification/tree/main/tests) that ensure that the spec has the correct request parameters, and that it matches the actual responses from the server. This is particularly useful when documenting a large existing API such as OpenSearch with its 1021 known APIs. | ||
|
||
Thus, I recently added support for [`text/plain`](https://github.com/opensearch-project/opensearch-api-specification/pull/360), [`application/yaml`](https://github.com/opensearch-project/opensearch-api-specification/pull/363), [`application/cbor`](https://github.com/opensearch-project/opensearch-api-specification/pull/371) response types to the test tooling, and have yet to add support for `application/smile`. | ||
|
||
I've heard of YAML, but what is SMILE or CBOR?! | ||
|
||
OpenSearch `_cat` API stands for "Compact and Aligned Text". | ||
|
||
{% highlight bash %} | ||
$ curl -k -u admin:$OPENSEARCH_PASSWORD https://localhost:9200/_cat | ||
=^.^= | ||
/_cat/allocation | ||
... | ||
{% endhighlight %} | ||
|
||
Do you see the `=^.^=` cat? Neat! This was a `content-type: text/plain; charset=UTF-8` response. | ||
|
||
Other CAT APIs respond with text the same way. | ||
|
||
{% highlight bash %} | ||
$ curl -k -u admin:$OPENSEARCH_PASSWORD https://localhost:9200/_cat/indices | ||
|
||
green open .plugins-ml-model-group LDXIur-YTqim9fiEHLJZ1w 1 0 0 0 10.3kb 10.3kb | ||
yellow open security-auditlog-2024.05.30 7yBZpI7HS22-6mZtPrVg2g 1 1 62 0 78.8kb 78.8kb | ||
{% endhighlight %} | ||
|
||
You can ask for JSON, `application/json`. Pipe it with [jq](https://jqlang.github.io/jq/). | ||
|
||
{% highlight bash %} | ||
$ curl -k -u admin:$OPENSEARCH_PASSWORD https://localhost:9200/_cat/indices?format=json | jq | ||
{% endhighlight %} | ||
|
||
{% highlight json %} | ||
[ | ||
{ | ||
"health": "green", | ||
"status": "open", | ||
"index": ".plugins-ml-model-group", | ||
"uuid": "LDXIur-YTqim9fiEHLJZ1w", | ||
"pri": "1", | ||
"rep": "0", | ||
"docs.count": "0", | ||
"docs.deleted": "0", | ||
"store.size": "10.3kb", | ||
"pri.store.size": "10.3kb" | ||
}, | ||
{ | ||
"health": "yellow", | ||
"status": "open", | ||
"index": "security-auditlog-2024.05.30", | ||
"uuid": "7yBZpI7HS22-6mZtPrVg2g", | ||
"pri": "1", | ||
"rep": "1", | ||
"docs.count": "62", | ||
"docs.deleted": "0", | ||
"store.size": "78.8kb", | ||
"pri.store.size": "78.8kb" | ||
} | ||
] | ||
{% endhighlight %} | ||
|
||
You can ask for YAML, `application/yaml`. | ||
|
||
{% highlight bash %} | ||
$ curl -k -u admin:$OPENSEARCH_PASSWORD https://localhost:9200/_cat/indices?format=yaml | ||
{% endhighlight %} | ||
|
||
{% highlight yaml %} | ||
yaml | ||
--- | ||
- health: "green" | ||
status: "open" | ||
index: ".plugins-ml-model-group" | ||
uuid: "LDXIur-YTqim9fiEHLJZ1w" | ||
pri: "1" | ||
rep: "0" | ||
docs.count: "0" | ||
docs.deleted: "0" | ||
store.size: "10.3kb" | ||
pri.store.size: "10.3kb" | ||
- health: "yellow" | ||
status: "open" | ||
index: "security-auditlog-2024.05.30" | ||
uuid: "7yBZpI7HS22-6mZtPrVg2g" | ||
pri: "1" | ||
rep: "1" | ||
docs.count: "62" | ||
docs.deleted: "0" | ||
store.size: "78.8kb" | ||
pri.store.size: "78.8kb" | ||
{% endhighlight %} | ||
|
||
Or for [CBOR](https://cbor.io/), which stands for "Concise Binary Object Representation". Pipe it using [cbor2](https://pypi.org/project/cbor2/). | ||
|
||
{% highlight bash %} | ||
$ curl -k -u admin:$OPENSEARCH_PASSWORD https://localhost:9200/_cat/indices?format=cbor | ||
{% endhighlight %} | ||
|
||
{% highlight json %} | ||
[{"health": "green", "status": "open", "index": ".plugins-ml-model-group", "uuid": "LDXIur-YTqim9fiEHLJZ1w", "pri": "1", "rep": "0", "docs.count": "0", "docs.deleted": "0", "store.size": "10.3kb", "pri.store.size": "10.3kb"}, {"health": "yellow", "status": "open", "index": "security-auditlog-2024.05.30", "uuid": "7yBZpI7HS22-6mZtPrVg2g", "pri": "1", "rep": "1", "docs.count": "62", "docs.deleted": "0", "store.size": "78.8kb", "pri.store.size": "78.8kb"}] | ||
{% endhighlight %} | ||
|
||
Finally, [SMILE](https://github.com/FasterXML/smile-format-specification) is another binary data format that defines a binary equivalent of standard JSON data format. | ||
|
||
{% highlight bash %} | ||
$ curl -k -u admin:$OPENSEARCH_PASSWORD https://localhost:9200/_cat/indices?format=smile | ||
{% endhighlight %} | ||
|
||
{% highlight text %} | ||
:) | ||
???healthDgreen?statusCopen?indexV.plugins | ||
... | ||
{% endhighlight %} | ||
|
||
Yes, the data is prefixed with `:)`. I tried to find a command-line processor for it, and even build [unsmile](https://github.com/pierre/libsmile) on MacOS (arm64), but [failed](https://github.com/pierre/libsmile/issues/5). | ||
|