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
On the "nameTokens" filed the boost parameter keeps increasing with the number of queries. Thats is
When the query is fired for the first time. The explanation i got for the two results, one matched the "nameToken" clause and the other matched the "companyDomain" clause:
… mutable changing the query else where in the execution path changes the instance in the cache too.
Instead the query parser cache should return a cloned instances.
Closeselastic#2542
… mutable changing the query else where in the execution path changes the instance in the cache too.
Instead the query parser cache should return a cloned instances.
Closes#2542Closes#6733
… mutable changing the query else where in the execution path changes the instance in the cache too.
Instead the query parser cache should return a cloned instances.
Closes#2542Closes#6733
mute
pushed a commit
to mute/elasticsearch
that referenced
this issue
Jul 29, 2015
… mutable changing the query else where in the execution path changes the instance in the cache too.
Instead the query parser cache should return a cloned instances.
Closeselastic#2542Closeselastic#6733
Hi,
I think this is an issue. I posted in the user group but got no response.
When the following query is created on an Index with lot of fields...
On the "nameTokens" filed the boost parameter keeps increasing with the number of queries. Thats is
1st result
2nd result
2nd time the same search result is fired:
2nd result
If you look at the boost parameter in the query explanation, it is increasing with every query of one clause.
The text was updated successfully, but these errors were encountered: