Hi Tomas
Yeah, I now understand it. I was confused about interpreting the output.
Thanks for the comments.
Sowmya.
2011/7/20 Tomás Fernández Löbbe
> So, what you want is to have the same exact results set as if the query was
> "scientific", but the documents that also match Field1:[20 TO 30]
So, what you want is to have the same exact results set as if the query was
"scientific", but the documents that also match Field1:[20 TO 30] to have
more score, right?
On Wed, Jul 20, 2011 at 10:53 AM, Sowmya V.B. wrote:
> Hi Tomas
>
> Here is what I was trying to give.
>
>
> http://localhost:8
Hi Tomas
Here is what I was trying to give.
http://localhost:8085/apache-solr-3.3.0/select?indent=on&version=2.2&defType=dismax&q=scientific&bq=Field1:[20%20TO%2030]
^10&start=0&rows=30&qf=text&fl=Field1,docid&debugQuery=on
Over here, I was trying to change the range of Field1, keeping everythin
Yes, it should, but make sure you specify at least the "qf" parameter for
dismax. You can activate debugQuery and you'll see which documents get
boosted and which aren't.
On Wed, Jul 20, 2011 at 9:21 AM, Sowmya V.B. wrote:
> Hi Tomasso
>
> Thanks for a quick response.
>
> So, if I say:
> http:/
Hi Tomasso
Thanks for a quick response.
So, if I say:
http://localhost:8085/apache-solr-3.3.0/select?indent=on&version=2.2*
&defType=dismax*&q=scientific&bq=Field1:[20%20TO%2025]^10&start=0&rows=30
-will it be right?
The above query: boosts the documents which suit the given query
("scientific")
Hi Sowmya, "bq" is a great way of boosting, but you have to be using the
Dismax Query Parser or the Extended Dismax (edismax) query parser, it
doesn't work with the Lucene Query Parser. If you can use any of those, then
that's the solution. If you need to use the Lucene Query Parser, for a user
que
Can anyone throw some light on this issue?
My problem is to: give a query time boost to certain documents, which have a
field, say field1, in the range that the user chooses during query time. I
think the below link indicates a range query:
http://localhost:8085/solr/select?indent=on&version=2.2&
Checking it further by looking at the code, it seems that in most cases
it indeed adds the boost queries as SHOULD. But if you define *one* bq
parameter which contains a boolean query, then each clause in this
boolean query will be added to the query as is. Therefore:
This set up will filter t
Well.. this is mainly based on some experiments I did (not based on the
code base). It appeared as if the boost queries were appended to the
generated dismax query and if the default operator (in the schema) was
set to AND it actually filtered out the request. For example, here's a
dismax confi
Are you sure about the default operator and bq? I assume we're
talking about the setting in schema.xml.
I think boosting queries are OR'd in automatically to the main query:
From DismaxQParser#addBoostQuery()
... query.add(f, BooleanClause.Occur.SHOULD);...
There is one case where query.ad
You can actually define boost queries to do that (bq parameter). Boost
queries accept the standard Lucene query syntax and eventually appended
to the user query. Just make sure that the default operator is set to OR
other wise these boost queries will not only influence the boosts but
also filt
Terms no, but fields (with terms) and phrases, yes.
Otis
--
Sematext -- http://sematext.com/ -- Solr - Lucene - Nutch
- Original Message
> From: Girish Redekar
> To: solr-user@lucene.apache.org
> Sent: Fri, December 4, 2009 11:42:16 PM
> Subject: Query time boosting with dismax
>
>
I'm in a rush, so here is just a pointer: Function Queries are your friend.
They'll let you use use field values to calculate your own custom scores based
on your own custom rules/functions.
Otis
--
Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch
- Original Message
From: Ami
13 matches
Mail list logo
