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
Been trying out NEST 2.0.0-Alpha 1 and I think there are some changes that could be important do document. If you try to add something to a boolean that's not "complete", it's not added. This is a bit different to the NEST 1.x behaviour.
Example:
var oldNest = new SearchDescriptor<TestObject>()
.Index("index")
.Type("type")
.Query(q => q
.Bool(b => b
.Must(m => m.MatchAll())
.Should(s => s
.Fuzzy(f => f
.Field("name")
.Value("testvalue")))));
var newNest = new SearchDescriptor<TestObject>()
.Index("index")
.Type("type")
.Query(q => q
.Bool(b => b
.Must(m => m.MatchAll())
.Should(s => s
.Fuzzy(f => f
.Field("name")
.Value("testvalue")
.Fuzziness(Fuzziness.Auto)))));
it produces the expected output in NEST 2.0.0 Alpha 1:
Hi,
Been trying out NEST 2.0.0-Alpha 1 and I think there are some changes that could be important do document. If you try to add something to a boolean that's not "complete", it's not added. This is a bit different to the NEST 1.x behaviour.
Example:
Produces in NEST 1.7.1:
But in NEST 2.0.0 Alpha 1, it produces:
If you then change it to be the following:
it produces the expected output in NEST 2.0.0 Alpha 1:
This seems to apply to
QueryString
as well (theDefaultField
must be set). I have not checked any of the other queries.The text was updated successfully, but these errors were encountered: