Error when calling refresh - unrecognized parameter force
See original GitHub issueI used es 2.4.2 till now and version 12 of this package. Today I tried to use es 5.3 and version 13 of this package.
My calls to indices.refresh like this:
client.indices.refresh({force: true});
ends with an error:
request [/xxx/_refresh] contains unrecognized parameter: [force]
I’ve tried version 5.3, 5.3.3 and 5.4.1. All the same.
I think this may be related to the fact that in es 2.4.2 I could make a request like:
localhost:9200/xxx/_refresh?force=true
But in es 5 I have to move the force param to the body, otherwise I get the same error as above. Is there any chance this library is doing it wrong?
Issue Analytics
- State:
- Created 6 years ago
- Comments:9 (5 by maintainers)
Top Results From Across the Web
indices.refresh API spec is out of date · Issue #25234 · elastic ...
Error when calling refresh - unrecognized parameter force elastic/elasticsearch-js#555 ... @spalger indeed operation_threading and force are not relevant.
Read more >request [/someindex/_refresh] contains unrecognized ...
The client seems to send a parameter, that is not supported by Elasticsearch. In Elasticsearch 5.x adding unused parameters leads to an ...
Read more >Getting error You might just need to refresh it. Error in $A ...
Error in $A.getCallback() [An unknown error occurred attempting to fetch definitions at: https://sit-cscrm.cs12.force.com/auraCmpDef?aura.
Read more >Resolve the role_arn error when updating or deleting an AWS ...
1. Open the IAM console. 2. In the navigation pane, choose Roles. 3. In the Role name column, choose the IAM role that's...
Read more >Payment Method set to Status=Invalid on an update - Community
Attempting to update the Payment Method causes the error: Received unknown parameter: billing_details[address][zip] The bug is sending postal code ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thanks for the note @amiram, Elasticsearch seems to have dropped support for the
force
parameter without updating the rest api spec. I filed https://github.com/elastic/elasticsearch/issues/25234 with them and will regenerate/release an API update when it’s available.Hi! I’m closing this due to inactivity, if it is still an issue, please feel free to reopen! 😃