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
Default to all possible fields for items #7382
Closed
alexksikes
wants to merge
2
commits into
elastic:master
from
alexksikes:feature/mlt-default-all-fields
Closed
Default to all possible fields for items #7382
alexksikes
wants to merge
2
commits into
elastic:master
from
alexksikes:feature/mlt-default-all-fields
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Items with no specified field now defaults to all the possible fields from the document source. Previously, we had required 'fields' to be specified either as a top level parameter or for each item. The default behavior is now similar to the MLT API.
What would happen eg. on a binary field or a geo shape? |
The field must be of type string so it will be skipped. |
This sounds good to me. Can you make it explicit in the documentation? |
alexksikes
force-pushed
the
feature/mlt-default-all-fields
branch
from
August 22, 2014 12:06
6ddfaa4
to
4e0eb0f
Compare
LGTM |
alexksikes
added a commit
that referenced
this pull request
Aug 22, 2014
Items with no specified field now defaults to all the possible fields from the document source. Previously, we had required 'fields' to be specified either as a top level parameter or for each item. The default behavior is now similar to the MLT API. Closes #7382
alexksikes
added a commit
that referenced
this pull request
Sep 8, 2014
Items with no specified field now defaults to all the possible fields from the document source. Previously, we had required 'fields' to be specified either as a top level parameter or for each item. The default behavior is now similar to the MLT API. Closes #7382
clintongormley
changed the title
More Like This Query: defaults to all possible fields for items
More Like This Query: Default to all possible fields for items
Sep 8, 2014
clintongormley
changed the title
More Like This Query: Default to all possible fields for items
Default to all possible fields for items
Jun 7, 2015
clintongormley
added
:Search/Search
Search-related issues that do not fall into other categories
and removed
:More Like This
labels
Feb 13, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
>enhancement
:Search/Search
Search-related issues that do not fall into other categories
v1.4.0.Beta1
v2.0.0-beta1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Items with no specified field now defaults to all the possible fields from the
document source. Previously, we had required 'fields' to be specified either
as a top level parameter or for each item. The default behavior is now similar
to the MLT API.