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

[7.x] Make sure copy_to accepts null values (#76665) #76770

Merged
merged 2 commits into from
Aug 20, 2021

Conversation

jtibshirani
Copy link
Contributor

Backports the following commits to 7.x:

In elastic#72820 we improved the error message when attempting to `copy_to` with an
object value. The change accidentally started throwing errors for null values
too, although they're allowed. This PR fixes the regression and adds an
explicit test for `copy_to` with null values.
@jtibshirani jtibshirani merged commit f7cb1d4 into elastic:7.x Aug 20, 2021
@jtibshirani jtibshirani deleted the backport/7.x/pr-76665 branch August 20, 2021 17:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants