Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FIX: wrong usage of Scripted updates API's params field #1477

Merged
merged 1 commit into from Apr 12, 2021

Conversation

@lryong
Copy link
Contributor

@lryong lryong commented Mar 29, 2021

I don't know if ElasticSearch's API documentation has been updated, but to update script variables via the params field, It seems to add the params prefix, otherwise it will report an error like: Variable [x] is not defined.

Reference:

@olivere olivere merged commit 12eba18 into olivere:release-branch.v7 Apr 12, 2021
5 checks passed
5 checks passed
@github-actions
Run 1.15.x on ubuntu-latest Run 1.15.x on ubuntu-latest
Details
@github-actions
Run 1.15.x on ubuntu-latest Run 1.15.x on ubuntu-latest
Details
@github-actions
Run 1.16.x on ubuntu-latest Run 1.16.x on ubuntu-latest
Details
@github-actions
Run 1.16.x on ubuntu-latest Run 1.16.x on ubuntu-latest
Details
@github-code-scanning
CodeQL No new or fixed alerts
Details
@olivere olivere added this to the 7.0.24 milestone Apr 12, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

2 participants