You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
POST /upload_read/_search
{"query":{"match_all":{}},"_source":{"includes":["user_id"]}}
In case the sourceInclude(Seq.empty), the request excludes will be similarly removed completely, producing "_source":true.
This could be the intended behavior, I am not sure because there is no documentation and no tests for using both of these functions. However, the classic elasticsearch library allows it and anyone who attempts a migration will end up having nasty silent bugs.
Currently you can't use
sourceExclude
andsourceInclude
together when constructing aSearchRequest
. The latter will overwrite the former.produces
In case the
sourceInclude(Seq.empty)
, the request excludes will be similarly removed completely, producing"_source":true
.This could be the intended behavior, I am not sure because there is no documentation and no tests for using both of these functions. However, the classic elasticsearch library allows it and anyone who attempts a migration will end up having nasty silent bugs.
The text was updated successfully, but these errors were encountered: