@Bill Bell
Did you try debugQuery ?
yes I tried debugQuery, final score calculated is less when I apply
boost=0.002 in doc field compared to if I left blank but I can't see
where actual this 0.002 is directly impacting( As far as I understand this
is multiplicative so 0.002 technically deboost
Issue a Jura ticket ?
Did you try debugQuery ?
Bill Bell
Sent from mobile
On Mar 28, 2015, at 1:49 AM, CKReddy Bhimavarapu chaitu...@gmail.com wrote:
I am want to boost docs at index time, I am doing this using boost
parameter in doc field doc boost=2.0.
but I can't see direct impact on
Hi,
Did you disable norms ( omitNorms=true ) accidentally ?
Ahmet
On Saturday, March 28, 2015 9:49 AM, CKReddy Bhimavarapu chaitu...@gmail.com
wrote:
I am want to boost docs at index time, I am doing this using boost
parameter in doc field doc boost=2.0.
but I can't see direct impact on the
I am want to boost docs at index time, I am doing this using boost
parameter in doc field doc boost=2.0.
but I can't see direct impact on the doc by using debuQuery.
My question is that is there any other way to boost doc at index time and
can see the reflected changes i.e direct impact.
--
Hi,
I tested the BoostQueryParser and it works on the simplified example.
But we need to keep the edismax Query parser, so I tried the following query
and it seems to work (I defined a local bf='' for qq).
q=beautiful Christmas tree
mm=2
qf=title^12 description^2
defType=edismax
: http://localhost:8983/solr/collection1/select?q=ipod
:
belkinwt=xmldebugQuery=trueq.op=ANDdefType=edismaxbf=map(query($qq),0,0,0,100.0)qq={!edismax}power
:
: The error is :
: org.apache.solr.search.SyntaxError: Infinite Recursion detected parsing query
: 'power'
:
: And the stacktrace :
:
:
Hi Hoss,
Thanks for the explanation. Very complicated stuff. I never understand
NestedQParserPlugin.
We want all the documents with all terms (mm=100%) get an extra 1000 points,
but change nothing else. How would you restructure the following query?
q=beautiful Christmas treemm=2qf=title^12
] to a similar discussion.
[1] http://search-lucene.com/m/nK6t9j1fuc2
On Monday, December 16, 2013 12:19 PM, Anca Kopetz
anca.kop...@kelkoo.commailto:anca.kop...@kelkoo.commailto:anca.kop...@kelkoo.commailto:anca.kop...@kelkoo.com
wrote:
Hi,
How to boost documents that contain all search terms
] http://search-lucene.com/m/nK6t9j1fuc2
On Monday, December 16, 2013 12:19 PM, Anca Kopetz
anca.kop...@kelkoo.commailto:anca.kop...@kelkoo.com wrote:
Hi,
How to boost documents that contain all search terms in several of its fields ?
Below you cand find a simplified example :
The query
Hi,
How to boost documents that contain all search terms in several of its fields ?
Below you cand find a simplified example :
The query with Min should match:
q=beautiful Christmas treemm=2qf=title^12 description^2
There are two offers that match the query :
offer1 {title:Christmas tree
] http://search-lucene.com/m/nK6t9j1fuc2
On Monday, December 16, 2013 12:19 PM, Anca Kopetz anca.kop...@kelkoo.com
wrote:
Hi,
How to boost documents that contain all search terms in several of its fields ?
Below you cand find a simplified example :
The query with Min should match:
q=beautiful
Hi:
I'm using solr 3.6 with dismax query parser, I've found that docs that doesn't
has all the query terms get ranked above other that contains all the terms in
the search query. Using debugQuery I could see that the most part of the score
in this cases come from the coord(q,d) factor. Is
Hi, Jorge,
Here is a similar discussion : http://search-lucene.com/m/nK6t9j1fuc2/
On Sunday, December 8, 2013 2:48 AM, Ing. Jorge Luis Betancourt Gonzalez
jlbetanco...@uci.cu wrote:
Hi:
I'm using solr 3.6 with dismax query parser, I've found that docs that doesn't
has all the query terms
13 matches
Mail list logo