DSL查詢變化 · my-elasticsearch-cn

### DSL查詢變化(Search and Query DSL changes) 1\. query 變化 * `span_near`?查詢中的?`collect_payloads`?參數已經被移除.如果需要使用的話Payloads將會被加載. * 在布爾字段上的查詢將嚴格的解析類似boolean的值.這將意味著只會接受字符串為`"true"`?何?`"false"`的值,而其他的值都會引起一個異常. * `in`?查詢 (`terms`?查詢的另一個同義形式) 被移除 * `geo_bbox`?查詢 (`geo_bounding_box`?查詢的另一個同義形式) 被移除 * `mlt`?查詢 (`more_like_this`?查詢的另一個同義形式) 被移除. * `more_like_this`查詢中不再推薦使用的`like_text`,?`ids`?and?`docs`?幾個參數 (`like`的同義形式) 被移除. 同樣?`min_word_len`?(a synonym for?`min_word_length`) and?`max_word_len`?(a synonym for`max_word_length`) 被移除. * `fuzzy_match`?和?`match_fuzzy`?查詢 (`match`?查詢的同義形式) 被移除 * `terms`?查詢現在返回的文檔的評分為?`1`?且跟?`indices.query.bool.max_clause_count`?無關. * 不再推薦使用的?`indices`?查詢被移除 * 從查詢DSL中移除對空查詢對象 (`{ }`) 的支持. 當提供一個空的查詢對象的時候會出現一個錯誤. * `bool`查詢中不再推薦使用的?`minimum_number_should_match`?參數被移除, 取而代之的是?`minimum_should_match`?. * The?`query_string`?query now correctly parses the maximum number of states allowed when “[determinizing](https://en.wikipedia.org/wiki/Powerset_construction#Complexity)” a regex as?`max_determinized_states`?instead of the typo`max_determined_states`. * `query_string`?查詢不再接收?`enable_position_increment`參數,取而代之的是?`enable_position_increments`?. * `geo_distance`?查詢中, 使用?`sloppy_arc`?選項進行排序、聚合已經從?`distance_type`?參數中移除. * The?`geo_distance_range`?query, which was deprecated in 5.0, has been removed. * The?`optimize_bbox`?parameter has been removed from?`geo_distance`?queries. * The?`ignore_malformed`?and?`coerce`?parameters have been removed from`geo_bounding_box`,?`geo_polygon`, and?`geo_distance`?queries. * The?`disable_coord`?parameter of the?`bool`?and?`common_terms`?queries has been removed. If provided, it will be ignored and issue a deprecation warning. * The?`template`?query has been removed. This query was deprecated since 5.0 * The?`percolate`?query’s?`document_type`?has been deprecated. From 6.0 and later it is no longer required to specify the?`document_type`?parameter. * The?`split_on_whitespace`?parameter for the?`query_string`?query has been removed. If provided, it will be ignored and issue a deprecation warning. The?`query_string`?query now splits on operator only. * The?`use_dismax`?parameter for the?`query_string`?query has been removed. If provided, it will be ignored and issue a deprecation warning. The?`tie_breaker`?parameter must be used instead. * The?`auto_generate_phrase_queries`?parameter for the?`query_string`?query has been removed, use an explicit quoted query instead. If provided, it will be ignored and issue a deprecation warning. * The?`all_fields`?parameter for the?`query_string`?has been removed. Set?`default_field`?to?*`instead. If provided,`default_field`will be automatically set to`*` * The?`index`?parameter in the terms filter, used to look up terms in a dedicated index is now mandatory. Previously, the index defaulted to the index the query was executed on. Now this index must be explicitly set in the request. * `match`查詢中不再推薦使用的`type`?and?`slop`?參數被移除. 取而代之的是在`match_phrase`?或?`match_phrase_prefix`查詢中使用?`type`參數.`match`查詢中的?`slop`被移除但是依然適用于`match_phrase`?和?`match_phrase_prefix`查詢. * `match_phrase`查詢中不再推薦使用的`phrase_slop`?參數 (與`slop`參數同義) 被移除. * `constant_score`查詢中不再推薦使用的`query`?參數 (與`filter`?參數同義)被移除 * `multi_match`查詢中不再推薦使用的`phrase_slop`?參數 (與`slop`參數同義) 被移除. * `prefix`查詢中不在推薦使用的?`prefix`?參數 (與`value`?參數同義) 被移除. * `range`查詢不再推薦使用的?`le`?(與`lte`同義) 和?`ge`?(與`gte`同義) 參數被移除. * 不再推薦使用的multi term重寫參數?`constant_score_auto`,?`constant_score_filter`?( 與`constant_score`同義) 已經被移除. 2\. 分片查詢API(search shards API) 查詢分片 API不再在url參數中接受`type`參數,之前的版本不會受到任何影響. 3\. Profile API變化用來顯示人類可讀的計時輸出`"time"`字段已經被“time_in_nanos”字段所取代，該字段顯示了納秒內的運行時間.`"time"`字段可以通過在請求url中添加`"?human=true"`來打開,它將顯示一個精密的、人類可讀的時間值. 4\. 排序變化 * 查詢歸一化(Query normalization) 查詢歸一化已經被取消.這意味著TF-IDF似度不再試圖在查詢中使分數具有可比性，而現在提高的分數是簡單的乘法因子。其他相似度模型不受影響，因為它們并沒有使分數歸一化，而且已經集成了提升系數作為乘法因子。請參考?[`LUCENE-7347`](https://issues.apache.org/jira/browse/LUCENE-7347)以了解更多信息 * 協調因子(Coordination factors) 協調因素已從評分公式中移除。這意味著布爾查詢不再根據匹配子句的數量進行評分。相反，它們總是返回匹配子句的分數之和。 As a consequence, use of the TF-IDF similarity is now discouraged as this was an important component of the quality of the scores that this similarity produces. BM25 is recommended instead. See?[`LUCENE-7347`](https://issues.apache.org/jira/browse/LUCENE-7347)?for more information 5\. _uid中的Fielddata `_uid`中使用Fielddata已經不再推薦使用. 仍然有可能將使用`_id`來替代,但是為什么還沒有讓他不再推薦使用,是因為它在`random_score`函數中被用到.如果你的確需要訪問文檔的id用來進行排序,聚合或者腳本查詢,推薦復制id作為一個文檔字段. 6\. 高亮(highlighter) `unified`高亮是新的高亮默認選擇.內部會根據字段類型(`index_options`)來決定每個字段的偏移策略以及如何高亮. 仍然有可能強制讓高亮成`fvh`?或者?`plain`?類型. `postings`高亮已經從Lucene 和 Elasticsearch中被移除.`unified`高亮輸出同樣的高亮效果當參數`index_options`被設置成`offsets`. 7\. fielddata_fields 之前不推薦使用的`fielddata_fields`已經被移除. 取而代之的是使用`docvalue_fields` 8\. docvalue_fields `docvalue_fields`現在有一個默認的上限值,一個請求中最多含有100個字段.該限制可以通過索引參數設置`index.max_docvalue_fields_search`來覆蓋. 9\. script_fields `script_fields`現在有一個默認的上限值,一個請求中最多限制在32個腳本字段內.該限制可以通過索引參數設置`index.max_script_fields`來覆蓋. 10\. Inner hits The source inside a hit of inner hits keeps its full path with respect to the entire source. In prior versions the source field names were relative to the inner hit.（此段還沒有明白是個啥） 11\. Scroll 當在開始使用scroll的時候,”from“參數不用再使用到查詢請求體中.過去如果添加了該參數,該參數將會被忽略,現在將會拋出一個錯誤. 12\. Limit on from/size in top hits and inner hits 返回結果的最大數量(from + size)允許通過inner hits被重新取回,并且 top hits 已經限制在100內.該限制能夠通過”index.max_inner_result_window“來控制.