(selectable by the user).
It seams like ES is not 100 Percent Lucene conform because it is not using
omitNorms=true on numeric fields :-(
The issue you mentioned is years ago and also fixed.
Nevertheless the boosting problem of ES is somewhere in the QueryParsers
which transforms the result
Maybe a typo?
For this example
PUT /test/test/1
{
name : einzelhandel,
type : oa
}
PUT /test/test/2
{
name : grosshandel,
type : oa
}
PUT /test/test/3
{
name : grosshandel,
type : closed
}
POST /test/test/_search
{
explain: true,
query: {
bool: {
must: {
Actually I can't follow you.
My query should be:
must_match(fieldname text, value einzelhandel, boost 200) AND
should_match(fieldname oa, value 1, boost 400)
Where is my typo?
Ahh you mean the value of oa with 1 is a string whereas the mapping is
integer?
Am Montag, 4. August 2014
So because of problems with boosted numeric field values in Elasticsearch I
should change my mapping
and change all my 60 million documents from integer (or short) to string?
Wouldn't it be better to fix this in Elasticsearch?
At least it works with Solr, so Lucene is not the problem.
I will
Because integer fields have no norms, it is quite uncommon to use them for
boosting. More common is the use for interpreting integer values as input
for scoring algorithm with function score.
Which Solr version is this? Solr did not follow the Lucene default in
previous versions regarding integer
I am trying to do the follwing query but it is showing error
{
query: {
boosting: {
positive: {
term: {
name: kamal
}
},
negative: {
term: {
email: abc
}
}
}
}
}
--
You received this message because you
Hi Navneet,
What error you are getting while running above command?
Try following Query:
curl -XPOST localhost:9200/indexName/indexType/_search?pretty=true -d '
{
query : {
boosting : {
positive : {
term : {
name : kamal
}
},
if I am running the above command it is showing SearchPhaseExecutionException
error ... but the command you have suggested working fine.
Thanks.
On Tuesday, 4 February 2014 14:24:39 UTC+5:30, Jayesh Bhoyar wrote:
Hi Navneet,
What error you are getting while running above command?
