Elasticsearch: Issue in command

[Dev393]

Hi,
There is an issue in this doc https://www.elastic.co/guide/en/elasticsearch/reference/current/cat-snapshots.html which says about command "GET /_cat/snapshots/repo1?v&s=id" when I do copyascurl it gives curl -X GET "localhost:9200/_cat/snapshots/repo1?v&s=id&pretty", If there is a pretty at the end it gives no result, issue reported here "https://discuss.elastic.co/t/elasticsearch-snapshot-query/235820/5"

Regards
Dev

Elasticsearch version (bin/elasticsearch --version):

Plugins installed: []

JVM version (java -version):

OS version (uname -a if on a Unix-like system):

Description of the problem including expected versus actual behavior:

Steps to reproduce:

Please include a minimal but complete recreation of the problem,
including (e.g.) index creation, mappings, settings, query etc. The easier
you make for us to reproduce it, the more likely that somebody will take the
time to look at it.

1.
2.
3.

Provide logs (if relevant):

[dadoonet]

That's a documentation issue I think.

[cbuescher]

Just tried locally with 7.6.2 and both 7.7 versions, always works for me with "&pretty":

PUT /_snapshot/my_backup
{
  "type": "fs",
  "settings": {
    "location": "my_backup_location"
  }
}

GET /_cat/snapshots/my_backup?v&s=duration&pretty

[cbuescher]

@Dev393 which version did you use?

[elasticmachine]

Pinging @elastic/es-core-features (:Core/Features/CAT APIs)

[Dev393]

Hello,

If I do curl -X GET "localhost:9200/_cat/snapshots/repo1?v&s=id&pretty"
from ES version of 7.6.2 of servers.
If I remove Pretty curl -X GET "localhost:9200/_cat/snapshots/repo1?v&s=id"
it works fine.

Regards
Dev

On Mon, Jun 8, 2020 at 2:46 PM Elastic Machine [e-mail]
wrote:

Pinging @elastic/es-core-features
https://github.com/orgs/elastic/teams/es-core-features
(:Core/Features/CAT APIs)

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/elastic/elasticsearch/issues/57765#issuecomment-640479992,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFBKWO3B2AI6HYR6CBXXECTRVSUADANCNFSM4NVAKHMA
.

--
Best Regards
Dev

[cbuescher]

I cannot reproduce this on 7.6.2. curl -X GET "localhost:9200/_cat/snapshots/my_backup?v&s=id&pretty" gives me the same output as curl -X GET "localhost:9200/_cat/snapshots/my_backup?v&s=id". I'm inclined to say there's something else going on on your side. Can you repro this on a completely new repo? Can you add the steps that you do to create the repo and snapshots in it?

[Dev393]

Hello,

Here is the error:

{ "error" : { "root_cause" : [ { "type" : "illegal_argument_exception",
"reason" : "request [/_snapshot/repo name] contains unrecognized
parameters: [s], [v]" } ], "type" : "illegal_argument_exception", "reason"
: "request [/_snapshot/repo name] contains unrecognized parameters: [s],
[v]" }, "status" : 400 } Which I get if run with pretty.

Regards
Dev

On Mon, Jun 8, 2020 at 8:25 PM Christoph Büscher [e-mail]
wrote:

I cannot reproduce this on 7.6.2. curl -X GET
"localhost:9200/_cat/snapshots/my_backup?v&s=id&pretty" gives me the same
output as curl -X GET "localhost:9200/_cat/snapshots/my_backup?v&s=id".
I'm inclined to say there's something else going on on your side. Can you
repro this on a completely new repo? Can you add the steps that you do to
create the repo and snapshots in it?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/elastic/elasticsearch/issues/57765#issuecomment-640681442,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFBKWO6KZCLUNMQCGYXI3PTRVT3X5ANCNFSM4NVAKHMA
.

--
Best Regards
Dev

[henningandersen]

@Dev393 the error snippet you pasted indicates that you ran this against the /_snapshot API, not against the /_cat/snapshots API. Can you for completeness paste both the curl command used as well as the response. "v" and "s" are only valid parameters for the /_cat/snapshots API, not for the /_snapshot API.

[danielmitterdorfer]

No further feedback received. @Dev393 if you have the requested
information please add it in a comment and we can look at re-opening
this issue.