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
Change in index_in_parent
doesn't work, but throws no error
#53792
Comments
Pinging @elastic/es-search (:Search/Mapping) |
Thanks @AndyHunt66 for reporting this. I agree that we should throw an error when attempting to change the values for these parameters. The alternative is to add support for changing the value. This would allow for a situation in which some documents contain the values in the parent/ root but others do not, which is a strange index state and could cause confusion when querying against these fields. |
elastic#54386) The main changes are: 1. Throw an error when updating `include_in_parent` or `include_in_root` attribute of nested field dynamically by the PUT mapping API. 2. Add a test for the change. Closes elastic#53792
The main changes are: 1. Throw an error when updating `include_in_parent` or `include_in_root` attribute of nested field dynamically by the PUT mapping API. 2. Add a test for the change. Closes #53792 Co-authored-by: bellengao <gbl_long@163.com>
elastic#54386) The main changes are: 1. Throw an error when updating `include_in_parent` or `include_in_root` attribute of nested field dynamically by the PUT mapping API. 2. Add a test for the change. Closes elastic#53792
Elasticsearch version (
bin/elasticsearch --version
): 6.8.6 / 7.6.0Description:
Trying to change the value of
index_in_parent
seems to succeed, but doesn't.I would expect that it is working as designed that that value cannot be changed, but I think it's a bug that no error is returned when trying to change it.
Steps to Reproduce:
Expected behaviour:
The third
PUT
returns an error explaining that it's not possible to change the value of "include_in_parent"Observed Behaviour:
None of the calls throws an error.
The second
GET
returns exactly the same data as the first.The text was updated successfully, but these errors were encountered: