-
Notifications
You must be signed in to change notification settings - Fork 25k
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
Remove DFS_QUERY_AND_FETCH as a search type #22787
Conversation
This commit removes the search type `dfs_query_and_fetch` without a replacement. We don't allow to use this type via REST since 2.x but still keep it around for no particular reason. There we no users complaining about the availability. This should now be removed from the codebase. `query_and_fetch` is still used internally to safe a roundtrip if there is only one shard but it can't be used via the rest interface.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@elasticmachine test this please |
* master: (47 commits) Remove non needed import use expectThrows instead of manually testing exception Fix checkstyle and a test Update after review Read ec2 discovery address from aws instance tags Invalidate cached query results if query timed out (elastic#22807) Add remaining generated painless API Generate reference links for painless API (elastic#22775) [TEST] Fix ElasticsearchExceptionTests Add parsing method for ElasticsearchException.generateThrowableXContent() (elastic#22783) Improve connection closing in `RemoteClusterConnection` (elastic#22804) Docs: Cluster allocation explain should be on one page Remove DFS_QUERY_AND_FETCH as a search type (elastic#22787) Add repository-url module and move URLRepository (elastic#22752) fix date-processor to a new default year for every new pipeline execution. (elastic#22601) Add tests for top_hits aggregation (elastic#22754) [TEST] Added this for 93a28b0 submitted via elastic#22772 Fix typo in comment in OsProbe.java Add new ruby search library to community clients doc (elastic#22765) RangeQuery WITHIN case now normalises query (elastic#22431) ...
I will port this to 5.x as well. documentation for this stuff has been removed long ago and it's impossible to use it with REST anyway. @jpountz @clintongormley objections? |
This commit removes the search type `dfs_query_and_fetch` without a replacement. We don't allow to use this type via REST since 2.x but still keep it around for no particular reason. There we no users complaining about the availability. This should now be removed from the codebase. `query_and_fetch` is still used internally to safe a roundtrip if there is only one shard but it can't be used via the rest interface.
No objections, we removed the documentation for it a long time ago. |
+1 I can't imagine why anybody would be using this in java land |
@clintongormley And we wrote that in Java doc 2 years ago: https://www.elastic.co/guide/en/elasticsearch/client/java-api/current/java-search.html
So to me it's really clear that people should never use that. |
We should also remove |
@gmarz |
@clintongormley ah! thanks -- totally misread this |
This commit removes the search type
dfs_query_and_fetch
without areplacement. We don't allow to use this type via REST since 2.x
but still keep it around for no particular reason. There we no users
complaining about the availability. This should now be removed from the
codebase.
query_and_fetch
is still used internally to safe a roundtripif there is only one shard but it can't be used via the rest interface.