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

Expose search.highlight.term_vector_multi_value as a node level setting #22999

Merged
merged 1 commit into from Feb 6, 2017

Conversation

s1monw
Copy link
Contributor

@s1monw s1monw commented Feb 6, 2017

This setting was missed in the great settings refactoring and should be exposed
via node level settings.

…ting

This setting was missed in the great settings refactoring and should be exposed
via node level settings.
@s1monw
Copy link
Contributor Author

s1monw commented Feb 6, 2017

this came up on discuss

@s1monw s1monw merged commit f09c4e1 into elastic:master Feb 6, 2017
@s1monw s1monw deleted the expose_tv_multi_value_settings branch February 6, 2017 17:17
s1monw added a commit that referenced this pull request Feb 6, 2017
…ting (#22999)

This setting was missed in the great settings refactoring and should be exposed
via node level settings.
s1monw added a commit that referenced this pull request Feb 6, 2017
…ting (#22999)

This setting was missed in the great settings refactoring and should be exposed
via node level settings.
s1monw added a commit that referenced this pull request Feb 6, 2017
…ting (#22999)

This setting was missed in the great settings refactoring and should be exposed
via node level settings.
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.

None yet

2 participants