Re: Custom Score Query not working in elasticsearch-0.90.3
Binh,
Thanks for the help. I fixed my scoring issue but loat my indexed time
boosting. I tried using boosting at indexing using some other fields but
results are not very satisfactory. I was using custom score so that I can
get documents matching a search phrase with higher value of po field on
the top but things are not going that way. Is there any way of modifying my
current query mechanism so that I can get what I expect.
I want to search in a way which gives me docs which contains some part or
the whole text which is searched by user instead right now I'm getting docs
which contains words of the text only.
On Fri, Jan 31, 2014 at 5:30 AM, Ivan Brusic i...@brusic.com wrote:
I fixed this bug a while ago and it should be fixed in versions 0.90.6 and
higher.
https://github.com/elasticsearch/elasticsearch/issues/3752
https://github.com/elasticsearch/elasticsearch/pull/2913
Ivan
On Thu, Jan 30, 2014 at 11:51 AM, Binh Ly b...@hibalo.com wrote:
Coder, I've verified that this is a bug. However, the _boost field will
be deprecated in 1.0 in favor of the function_score query (
http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/query-dsl-function-score-query.html#_using_function_score).
For now, what you can do to fix this is to remove the _boost part from
your mapping and reindex your data and you should be able to access the
po field after that.
Remove this part from your mapping:
_boost : {
name : po,
null_value : 4.0
},
--
You received this message because you are subscribed to the Google Groups
elasticsearch group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/a1894a05-4195-44eb-aa62-80f173a58a99%40googlegroups.com
.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups
elasticsearch group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/CALY%3DcQAeYwN-%3DLNyaGRpMfuQuW8ytk0nJDtdv2gpKgGThO1YWg%40mail.gmail.com
.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups
elasticsearch group.
To unsubscribe from this group and stop receiving emails from it, send an email
to elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/CAAVTvp6-YkRL7qA6WjvTnOQEu-SDV07MCXWn0WntAH8q%2Bd63iA%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: Custom Score Query not working in elasticsearch-0.90.3
Ivan, I tried using different field for script and boost. script seems to
be working fine but boost is not working since I'm not able to see any
factor from _boost in explain api. Can you please tell me how can I make
use of boost ?
On Fri, Jan 31, 2014 at 5:53 AM, Ivan Brusic i...@brusic.com wrote:
BTW, if you do not want to upgrade, you can also simply maintain two
fields. One to use as a document boost (the _boost) and another to use for
scripting/sorting/faceting.
--
Ivan
On Thu, Jan 30, 2014 at 4:00 PM, Ivan Brusic i...@brusic.com wrote:
I fixed this bug a while ago and it should be fixed in versions 0.90.6
and higher.
https://github.com/elasticsearch/elasticsearch/issues/3752
https://github.com/elasticsearch/elasticsearch/pull/2913
Ivan
On Thu, Jan 30, 2014 at 11:51 AM, Binh Ly b...@hibalo.com wrote:
Coder, I've verified that this is a bug. However, the _boost field
will be deprecated in 1.0 in favor of the function_score query (
http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/query-dsl-function-score-query.html#_using_function_score).
For now, what you can do to fix this is to remove the _boost part from
your mapping and reindex your data and you should be able to access the
po field after that.
Remove this part from your mapping:
_boost : {
name : po,
null_value : 4.0
},
--
You received this message because you are subscribed to the Google
Groups elasticsearch group.
To unsubscribe from this group and stop receiving emails from it, send
an email to elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/a1894a05-4195-44eb-aa62-80f173a58a99%40googlegroups.com
.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups
elasticsearch group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/CALY%3DcQDY1nxQB_cYu%2B7Ph8Osai3PMNTUyKQuW8zL2z9OYxYAOQ%40mail.gmail.com
.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups
elasticsearch group.
To unsubscribe from this group and stop receiving emails from it, send an email
to elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/CAAVTvp6bcp5Zy9a5z8GFz1r_-9raub5NDsHAE%2BacEegaOrW%2BoQ%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: Custom Score Query not working in elasticsearch-0.90.3
Here is part of something I wrote on another thread just 20 minutes ago:
Index-time boosts are encoded inside the field norms. You should see a
difference inside each field norm. If you have omitted norms, then you will
not have any boosts on that field. The field norm is also lossly since it
uses only 1-byte. Some of the many reasons to switch from document time
boosts.
There is no reason to use both document boosts and custom scores. If you
are already using a score function, just apply the boost at that level.
Either way, you will not see the boost value directly.
Ivan
On Fri, Jan 31, 2014 at 8:13 AM, Mukul Gupta mukulnit...@gmail.com wrote:
Ivan, I tried using different field for script and boost. script seems to
be working fine but boost is not working since I'm not able to see any
factor from _boost in explain api. Can you please tell me how can I make
use of boost ?
On Fri, Jan 31, 2014 at 5:53 AM, Ivan Brusic i...@brusic.com wrote:
BTW, if you do not want to upgrade, you can also simply maintain two
fields. One to use as a document boost (the _boost) and another to use for
scripting/sorting/faceting.
--
Ivan
On Thu, Jan 30, 2014 at 4:00 PM, Ivan Brusic i...@brusic.com wrote:
I fixed this bug a while ago and it should be fixed in versions 0.90.6
and higher.
https://github.com/elasticsearch/elasticsearch/issues/3752
https://github.com/elasticsearch/elasticsearch/pull/2913
Ivan
On Thu, Jan 30, 2014 at 11:51 AM, Binh Ly b...@hibalo.com wrote:
Coder, I've verified that this is a bug. However, the _boost field
will be deprecated in 1.0 in favor of the function_score query (
http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/query-dsl-function-score-query.html#_using_function_score).
For now, what you can do to fix this is to remove the _boost part
from your mapping and reindex your data and you should be able to access
the po field after that.
Remove this part from your mapping:
_boost : {
name : po,
null_value : 4.0
},
--
You received this message because you are subscribed to the Google
Groups elasticsearch group.
To unsubscribe from this group and stop receiving emails from it, send
an email to elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/a1894a05-4195-44eb-aa62-80f173a58a99%40googlegroups.com
.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups
elasticsearch group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/CALY%3DcQDY1nxQB_cYu%2B7Ph8Osai3PMNTUyKQuW8zL2z9OYxYAOQ%40mail.gmail.com
.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups
elasticsearch group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/CAAVTvp6bcp5Zy9a5z8GFz1r_-9raub5NDsHAE%2BacEegaOrW%2BoQ%40mail.gmail.com
.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups
elasticsearch group.
To unsubscribe from this group and stop receiving emails from it, send an email
to elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/CALY%3DcQD3vOZ-skoK6k02mrCE%3Df-T8yyz3d1pRQ%2Bzwi2OV3SSrg%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: Custom Score Query not working in elasticsearch-0.90.3
I agree that modifying the score of a doc gives me same effect as the
document boost but somehow I'm not finding the results very satisfactory.
I'm thinking may be using _boost for the entire doc can give me some
advantage. Also, I'm talking about _boost not the boost per field,
something like this:
_boost : {
name : po,
null_value : 4.0
}
Please correct me if _boost is same as boost which I guess is not as far as
I have understood.
Thanks
On Fri, Jan 31, 2014 at 9:52 PM, Ivan Brusic i...@brusic.com wrote:
Here is part of something I wrote on another thread just 20 minutes ago:
Index-time boosts are encoded inside the field norms. You should see a
difference inside each field norm. If you have omitted norms, then you will
not have any boosts on that field. The field norm is also lossly since it
uses only 1-byte. Some of the many reasons to switch from document time
boosts.
There is no reason to use both document boosts and custom scores. If you
are already using a score function, just apply the boost at that level.
Either way, you will not see the boost value directly.
Ivan
On Fri, Jan 31, 2014 at 8:13 AM, Mukul Gupta mukulnit...@gmail.comwrote:
Ivan, I tried using different field for script and boost. script seems to
be working fine but boost is not working since I'm not able to see any
factor from _boost in explain api. Can you please tell me how can I make
use of boost ?
On Fri, Jan 31, 2014 at 5:53 AM, Ivan Brusic i...@brusic.com wrote:
BTW, if you do not want to upgrade, you can also simply maintain two
fields. One to use as a document boost (the _boost) and another to use for
scripting/sorting/faceting.
--
Ivan
On Thu, Jan 30, 2014 at 4:00 PM, Ivan Brusic i...@brusic.com wrote:
I fixed this bug a while ago and it should be fixed in versions 0.90.6
and higher.
https://github.com/elasticsearch/elasticsearch/issues/3752
https://github.com/elasticsearch/elasticsearch/pull/2913
Ivan
On Thu, Jan 30, 2014 at 11:51 AM, Binh Ly b...@hibalo.com wrote:
Coder, I've verified that this is a bug. However, the _boost field
will be deprecated in 1.0 in favor of the function_score query (
http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/query-dsl-function-score-query.html#_using_function_score).
For now, what you can do to fix this is to remove the _boost part
from your mapping and reindex your data and you should be able to access
the po field after that.
Remove this part from your mapping:
_boost : {
name : po,
null_value : 4.0
},
--
You received this message because you are subscribed to the Google
Groups elasticsearch group.
To unsubscribe from this group and stop receiving emails from it, send
an email to elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/a1894a05-4195-44eb-aa62-80f173a58a99%40googlegroups.com
.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google
Groups elasticsearch group.
To unsubscribe from this group and stop receiving emails from it, send
an email to elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/CALY%3DcQDY1nxQB_cYu%2B7Ph8Osai3PMNTUyKQuW8zL2z9OYxYAOQ%40mail.gmail.com
.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups
elasticsearch group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/CAAVTvp6bcp5Zy9a5z8GFz1r_-9raub5NDsHAE%2BacEegaOrW%2BoQ%40mail.gmail.com
.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups
elasticsearch group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/CALY%3DcQD3vOZ-skoK6k02mrCE%3Df-T8yyz3d1pRQ%2Bzwi2OV3SSrg%40mail.gmail.com
.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups
elasticsearch group.
To unsubscribe from this group and stop receiving emails from it, send an email
to elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/CAAVTvp65GDe79Gf%2B4sz23T_Yr4s4b%2BZ5eJZUsy%3DZ409mfG0jXQ%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: Custom Score Query not working in elasticsearch-0.90.3
Coder, I can duplicate your problem. I am trying to find out if this is a bug, or it is by design and will get back to you shortly. Thanks. -- You received this message because you are subscribed to the Google Groups elasticsearch group. To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/4c6625f0-299c-441a-8c44-826e543054e7%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Custom Score Query not working in elasticsearch-0.90.3
I fixed this bug a while ago and it should be fixed in versions 0.90.6 and
higher.
https://github.com/elasticsearch/elasticsearch/issues/3752
https://github.com/elasticsearch/elasticsearch/pull/2913
Ivan
On Thu, Jan 30, 2014 at 11:51 AM, Binh Ly b...@hibalo.com wrote:
Coder, I've verified that this is a bug. However, the _boost field will
be deprecated in 1.0 in favor of the function_score query (
http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/query-dsl-function-score-query.html#_using_function_score).
For now, what you can do to fix this is to remove the _boost part from
your mapping and reindex your data and you should be able to access the
po field after that.
Remove this part from your mapping:
_boost : {
name : po,
null_value : 4.0
},
--
You received this message because you are subscribed to the Google Groups
elasticsearch group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/a1894a05-4195-44eb-aa62-80f173a58a99%40googlegroups.com
.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups
elasticsearch group.
To unsubscribe from this group and stop receiving emails from it, send an email
to elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/CALY%3DcQAeYwN-%3DLNyaGRpMfuQuW8ytk0nJDtdv2gpKgGThO1YWg%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: Custom Score Query not working in elasticsearch-0.90.3
BTW, if you do not want to upgrade, you can also simply maintain two
fields. One to use as a document boost (the _boost) and another to use for
scripting/sorting/faceting.
--
Ivan
On Thu, Jan 30, 2014 at 4:00 PM, Ivan Brusic i...@brusic.com wrote:
I fixed this bug a while ago and it should be fixed in versions 0.90.6 and
higher.
https://github.com/elasticsearch/elasticsearch/issues/3752
https://github.com/elasticsearch/elasticsearch/pull/2913
Ivan
On Thu, Jan 30, 2014 at 11:51 AM, Binh Ly b...@hibalo.com wrote:
Coder, I've verified that this is a bug. However, the _boost field will
be deprecated in 1.0 in favor of the function_score query (
http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/query-dsl-function-score-query.html#_using_function_score).
For now, what you can do to fix this is to remove the _boost part from
your mapping and reindex your data and you should be able to access the
po field after that.
Remove this part from your mapping:
_boost : {
name : po,
null_value : 4.0
},
--
You received this message because you are subscribed to the Google Groups
elasticsearch group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/a1894a05-4195-44eb-aa62-80f173a58a99%40googlegroups.com
.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups
elasticsearch group.
To unsubscribe from this group and stop receiving emails from it, send an email
to elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/CALY%3DcQDY1nxQB_cYu%2B7Ph8Osai3PMNTUyKQuW8zL2z9OYxYAOQ%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.
