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

Explicit doc_values setting. #4561

Closed
wants to merge 1 commit into from
Closed

Conversation

jpountz
Copy link
Contributor

@jpountz jpountz commented Dec 27, 2013

Once doc values are enabled on a field, they can't be disabled.

Close #4560

Once doc values are enabled on a field, they can't be disabled.

Close elastic#4560
@s1monw
Copy link
Contributor

s1monw commented Dec 29, 2013

just to get it right - this PR makes sure that you set DV with the mapping and if you don't do so (ie with dynamic mapping) you can't add it later. So you need to make the decision ahead of time and you can't go back, right?

@jpountz
Copy link
Contributor Author

jpountz commented Dec 29, 2013

This is correct: decision needs to be made ahead of time and doc values can't be removed from an existing field. Also there are two ways to set them, either explicitely (doc_values: true) or because the fielddata format requires them (fielddata: { format: "doc_values" }).

@s1monw
Copy link
Contributor

s1monw commented Dec 29, 2013

good +1 in that case!

@jpountz jpountz closed this Dec 30, 2013
@jpountz jpountz deleted the fix/doc_values branch December 30, 2013 10:22
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.

Explicit doc values setting
2 participants