Hi Erick,
Finally Made it work.
bf=if(exists(query($qqone)),one_score,0)&qqone=one_query:\"google cloud\"
Thanks a lot for guiding, also reminding its not url escape.
No analyzers used.
Regards,
Govind
On Tue, Jun 27, 2017 at 11:01 AM, govind nitk wrote:
> Hi Erick,
> I accept, I should
Hi Erick,
I accept, I should have mentioned the what I was doing first.
field types:
one_query is "string",
one_score is float.
So No explicit analyzers.
mentioned sow=false. and escaping as you mentioned. But still the error
persist. - undefined field "cloud"
Will get back.
Regards,
Givind
O
bq: So, ultimate goal is when the exact query matches in field
one_query, apply boost of one_score
It would have been helpful to have made that statement in the first
place, would have saved some false paths.
What is your analysis chain here? If it's anything like "text_general"
or the like then
Hi Developers, Erick
I am able to add boost through function as below:
bf=if(termfreq(one_query,"google"),one_score,0)
Problem is when I say "google cloud" as query, it gives error:
undefined field: \"cloud\""
I tried encoding the query(%20, + for space), but not able to get it
working.
So, ult
Hi Erick,
Exactly this is what I was looking for.
Thanks a lot.
Regards,
Govind
On Mon, Jun 26, 2017 at 12:03 AM, Erick Erickson
wrote:
> Take a look at function queries. You're probably looking for "field",
> "termfreq" and "if" functions or some other combination like that.
>
> On Sun, Jun
Take a look at function queries. You're probably looking for "field",
"termfreq" and "if" functions or some other combination like that.
On Sun, Jun 25, 2017 at 9:01 AM, govind nitk wrote:
> Hi Erik, Thanks for the reply.
>
> My intention of using the domain_ct in the qf was, giving the weight
>
Hi Erik, Thanks for the reply.
My intention of using the domain_ct in the qf was, giving the weight
present in the that document.
e.g
qf=category^domain_ct
if the current query matched in the category, the boost given will be
domain_ct, which is present in the current matched document.
So if I
With dismax use bf=domain_ct. you can also use boost=domain_ct with edismax.
> On Jun 23, 2017, at 23:01, govind nitk wrote:
>
> Hi Solr,
>
> My Index Data:
>
> id name category domain domain_ct
> 1 Banana Fruits Home > Fruits > Banana 2
> 2 Orange Fruits Home > Fruits > Orange 4
> 3 Samsung
Hi Solr,
My Index Data:
id name category domain domain_ct
1 Banana Fruits Home > Fruits > Banana 2
2 Orange Fruits Home > Fruits > Orange 4
3 Samsung Mobile Electronics > Mobile > Samsung 3
I am able to retrieve the documents with dismax parser with the weights
mentioned as below.
http://local
: Right now, I specify the boost for my request handler as:
:
: .
: ln(qty)
:
:
:
: Is there a way to specify this boost in the Solrconfig.xml?
:
: I tried: (*:* -Refurbished)^10 and I get the
: following exception:
:
: ERROR - 2015-05-01 15:13:41.609; org.apache.solr.commo
t; (*:* -Refurbished)^10
>
> -Hoss
> http://www.lucidworks.com/
--
View this message in context:
http://lucene.472066.n3.nabble.com/Negative-Boosting-documents-with-a-certain-word-tp4203224p4203488.html
Sent from the Solr - User mailing list archive at Nabble.com.
n certain words in
: their description.
:
: Thank you in advance for all your help,
: O. O.
:
:
:
: --
: View this message in context:
http://lucene.472066.n3.nabble.com/Negative-Boosting-documents-with-a-certain-word-tp4203224.html
: Sent from the Solr - User mailing list archive at Nabble.com.
:
-Hoss
http://www.lucidworks.com/
if they contain certain words in
their description.
Thank you in advance for all your help,
O. O.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Negative-Boosting-documents-with-a-certain-word-tp4203224.html
Sent from the Solr - User mailing list archive at Nabble.com.
Chris,
Sounds good! Thanks for the tips.. I'll be glad to submit my talk to this
as I have a writeup pretty much ready to go.
Cheers
Amit
On Tue, Jan 28, 2014 at 11:24 AM, Chris Hostetter
wrote:
>
> : The initial results seem to be kinda promising... of course there are
> many
> : more optimiz
: The initial results seem to be kinda promising... of course there are many
: more optimizations I could do like decay user ratings over time to indicate
: that preferences decay over time so a 5 rating a year ago doesn't count as
: much as a 5 rating today.
:
: Hope this helps others. I'll open
Hi Chris (and others interested in this),
Sorry for dropping off.. I got sidetracked with other work and came back to
this and finally got a V1 of this implemented.
The final process is as follows:
1) Pre-compute the global categorical num_ratings/average/std-dev (so for
Action the average rating
ct so, but then how should this
behaviour be implemented - the basic recipe failed to work, so I'm a little
confused.
Thanks!
-
Thanks,
Michael
--
View this message in context:
http://lucene.472066.n3.nabble.com/Boosting-documents-at-index-time-based-on-payloads-tp4110661.html
Sent from
: I thought about that but my concern/question was how. If I used the pow
: function then I'm still boosting the bad categories by a small
: amount..alternatively I could multiply by a negative number but does that
: work as expected?
I'm not sure i understand your concern: negative powers would
I thought about that but my concern/question was how. If I used the pow
function then I'm still boosting the bad categories by a small
amount..alternatively I could multiply by a negative number but does that
work as expected?
I haven't done much with negative boosting except for the sledgehammer
: My approach was something like:
: 1) Look at the categories that the user has preferred and compute the
: z-score
: 2) Pick the top 3 among those
: 3) Use those to boost search results.
I think that totaly makes sense ... the additional bit i was suggesting
that you consider is that instead of
Hey Chris,
Sorry for the delay and thanks for your response. This was inspired by your
talk on boosting and biasing that you presented way back when at a meetup.
I'm glad that my general approach seems to make sense.
My approach was something like:
1) Look at the categories that the user has pref
: I have a question around boosting. I wanted to use the &boost= to write a
: nested query that will boost a document based on categorical preferences.
You have no idea how stoked I am to see you working on this in a real
world application.
: Currently I have the weights set to the z-score equi
Hi all,
I have a question around boosting. I wanted to use the &boost= to write a
nested query that will boost a document based on categorical preferences.
For a movie search for example, say that a user likes drama, comedy, and
action. I could use things like
qq=&q={!boost%20b=$b%20defType=edis
Oh thank you Chris, this is much clearer, and thank you for updating the
Wiki too.
On 05/22/2013 08:29 PM, Chris Hostetter wrote:
: NOTE: make sure norms are enabled (omitNorms="false" in the schema.xml) for
: any fields where the index-time boost should be stored.
:
: In my case where I only n
: NOTE: make sure norms are enabled (omitNorms="false" in the schema.xml) for
: any fields where the index-time boost should be stored.
:
: In my case where I only need to boost the whole document (not a specific
: field), do I have to activate the << omitNorms="false" >> for all the fields
: in
olr/SolrRelevancyFAQ<http://wiki.apache.org/solr/SolrRelevancyFAQ>
http://wiki.apache.org/solr/**SolrRelevancyFAQ>
<http://wiki.**apache.org/solr/**SolrRelevancyFAQ<http://apache.org/**solr/**SolrRelevancyFAQ>
http://apache.org/solr/**SolrRelevancyFAQ>
http:/
;
>>>>>>> All you need to do is something similar to below..
>>>>>>>
>>>>>>> -
>>>>>>>
>>>>>>> >>>>>> name="employeeId">05991>>>>&g
<http://wiki.apache.org/solr/SolrRelevancyFAQ>
<http://**wiki.apache.org/solr/SolrRelevancyFAQ<http://wiki.apache.org/solr/**SolrRelevancyFAQ>
<http://wiki.**apache.org/**solr/**SolrRelevancyFAQ<http://apache.org/solr/**SolrRelevancyFAQ>
http://wiki.apache.org/solr/So
your message is whether you need better scoring
>>>>> or
>>>>> better sorting. so, additionally, you can consider adding a secondary
>>>>> sort
>>>>> parameter for the docs having the same score.
>>>>> http://wiki.apache.org/solr/CommonQueryParameters#sort<http://wiki.ap
e^2 subject
You can refer:
http://wiki.apache.org/solr/SolrRelevancyFAQ<http://wiki.apache.org/solr/**SolrRelevancyFAQ>
<http://wiki.**apache.org/solr/**SolrRelevancyFAQ<http://wiki.apache.org/solr/SolrRelevancyFAQ>
--
View this message in context: http://lucene.472066.n3.**
nabb
k you for your reply bbarani,
>>>>
>>>> I can't do that because I want to boost some documents over others,
>>>> independing of the query.
>>>>
>>>>
>>>> On 05/21/2013 05:41 PM, bbarani wrote:
>>>>
&
st during query time?
Something like q=superman&qf=title^2 subject
You can refer:
http://wiki.apache.org/solr/**SolrRelevancyFAQ<http://wiki.apache.org/solr/SolrRelevancyFAQ>
--
View this message in context: http://lucene.472066.n3.**
nabble.com/Boosting-Documents-**tp4064955p4064966
Q>
--
View this message in context: http://lucene.472066.n3.**
nabble.com/Boosting-Documents-**tp4064955p4064966.html<http://lucene.472066.n3.nabble.com/Boosting-Documents-tp4064955p4064966.html>
Sent from the Solr - User mailing list archive at Nabble.com.
ing like q=superman&qf=title^2 subject
>>
>> You can refer:
>> http://wiki.apache.org/solr/**SolrRelevancyFAQ<http://wiki.apache.org/solr/SolrRelevancyFAQ>
>>
>>
>>
>> --
>> View this message in context: http://lucene.472066.n3.**
&
iki.apache.org/solr/SolrRelevancyFAQ
--
View this message in context:
http://lucene.472066.n3.nabble.com/Boosting-Documents-tp4064955p4064966.html
Sent from the Solr - User mailing list archive at Nabble.com.
Why don't you boost during query time?
Something like q=superman&qf=title^2 subject
You can refer: http://wiki.apache.org/solr/SolrRelevancyFAQ
--
View this message in context:
http://lucene.472066.n3.nabble.com/Boosting-Documents-tp4064955p4064966.html
Sent from the Solr - Use
Hi everyone,
I have a small (I hope) issue, and I wish someone could point me to the
right direction.
I have been indexing some documents using Solr 4.1 and specifying
different "boost"s for different types of documents (boost for the whole
document). But when searching, I noticed that the s
Hi,
I would take a different approach. Track users' queries and their
clicks. Aggregate queries and start thinking of them as tags/labels.
Aggregate them and use top N to tag your docs.
Alternatively/additionally, extract significant terms and phrases from
clicked-to docs and use that to tag you
We have a number of queries that produce good results based on the textual
data, but are contextually wrong (for example, an "SSD hard drive" search
matches the music album "SSD hip hop drives us crazy".
Textually a fair match, but SSD is a term that strongly relates to technical
documents.
Well, the simplest would be to include the shard ID in the document
when you index it, then just boost on that field...
Best
Erick
On Thu, Aug 23, 2012 at 8:33 AM, Husain, Yavar wrote:
> I am aware that IDF is not distributed. Suppose I have to boost or give
> higher rank to documents which are
I am aware that IDF is not distributed. Suppose I have to boost or give higher
rank to documents which are matching in a specific/particular shard, how can I
accomplish that?
**
This message may contain conf
ot;^" suffix operator after
>>> a
>>> term/phrase)?
>>>
>>> -- Jack Krupansky
>>>
>>> -Original Message- From: Donald Organ
>>> Sent: Tuesday, May 01, 2012 3:59 PM
>>> To: solr-user
>>> Subject: Boosting documents based on search term/phrase
>>>
>>> Is there a way to boost documents based on the search term/phrase?
>>>
>>>
>
Hi,
Can you please give an example of what you mean?
Otis
Performance Monitoring for Solr / ElasticSearch / HBase -
http://sematext.com/spm
>
> From: Donald Organ
>To: solr-user
>Sent: Tuesday, May 1, 2012 3:59 PM
>Subject: Boosting
Here's some doc from Lucid:
http://lucidworks.lucidimagination.com/display/solr/The+Query+Elevation+Component
-- Jack Krupansky
-Original Message-
From: Donald Organ
Sent: Tuesday, May 01, 2012 5:23 PM
To: solr-user@lucene.apache.org
Subject: Re: Boosting documents based on s
k Krupansky
-Original Message- From: Donald Organ
Sent: Tuesday, May 01, 2012 3:59 PM
To: solr-user
Subject: Boosting documents based on search term/phrase
Is there a way to boost documents based on the search term/phrase?
//wiki.apache.org/solr/QueryElevationComponent>
>
> And besides explicit boosting by the user (the "^" suffix operator after a
> term/phrase)?
>
> -- Jack Krupansky
>
> -Original Message- From: Donald Organ
> Sent: Tuesday, May 01, 2012 3:59 PM
> To
012 3:59 PM
To: solr-user
Subject: Boosting documents based on search term/phrase
Is there a way to boost documents based on the search term/phrase?
Is there a way to boost documents based on the search term/phrase?
Thanks, will look into those.
Andu
On Mon, Oct 18, 2010 at 4:14 PM, Ahmet Arslan wrote:
>> I know but I can't figure out what
>> functions to use. :)
>
> Oh, I see. Why not just use {!boost b=log(vote)}?
>
> May be scale(vote,0.5,10)?
>
>
>
>
> I know but I can't figure out what
> functions to use. :)
Oh, I see. Why not just use {!boost b=log(vote)}?
May be scale(vote,0.5,10)?
I know but I can't figure out what functions to use. :)
On Mon, Oct 18, 2010 at 1:38 PM, Ahmet Arslan wrote:
>> I have a field in my schema which holds the number of votes
>> a document
>> has. How can I boost documents based on that number?
>
> you can do it with http://wiki.apache.org/solr/Func
> I have a field in my schema which holds the number of votes
> a document
> has. How can I boost documents based on that number?
you can do it with http://wiki.apache.org/solr/FunctionQuery
Hello all,
I have a field in my schema which holds the number of votes a document
has. How can I boost documents based on that number?
Something like the one which has the maximum number has a boost of 10,
the one with the smallest number has 0.5 and in between the values get
calculated automatic
On 8/12/07, Chris Hostetter <[EMAIL PROTECTED]> wrote:
> : I'm having the date boosting function as well. I'm using this function:
> : F = recip(rord(creationDate),1,1000,1000)^10. However, since I have around
> : 10,000 of documents added in one day, rord(createDate) returns very
> : different val
: I'm having the date boosting function as well. I'm using this function:
: F = recip(rord(creationDate),1,1000,1000)^10. However, since I have around
: 10,000 of documents added in one day, rord(createDate) returns very
: different values for the same createDate. For example, the last document
yo
We add around 10,000 docs during week days and 5,000 during weekends.
On 8/12/07, Pieter Berkel <[EMAIL PROTECTED]> wrote:
>
> Do you consistently add 10,000 documents to your index every day or does
> the
> number of new documents added per day vary?
>
>
> On 11/08/07, climbingrose <[EMAIL PROTEC
Do you consistently add 10,000 documents to your index every day or does the
number of new documents added per day vary?
On 11/08/07, climbingrose <[EMAIL PROTECTED]> wrote:
>
> I'm having the date boosting function as well. I'm using this function:
> F = recip(rord(creationDate),1,1000,1000)^10.
On 11/08/07, Chris Hostetter <[EMAIL PROTECTED]> wrote:
>
> i would agree with you there, this is where a more robust (ie:
> less efficient) DateField-ish class that supports configuration options
> to specify:
> 1) the output format
> 2) the input format(s)
> 3) the indexed format
> ...as Si
I'm having the date boosting function as well. I'm using this function:
F = recip(rord(creationDate),1,1000,1000)^10. However, since I have around
10,000 of documents added in one day, rord(createDate) returns very
different values for the same createDate. For example, the last document
added with
: Actually, just thinking about this a bit more, perhaps adding a function
: call such as parseDate() might add too much overhead to the actual query,
: perhaps it would be better to first convert the date to a timestamp at index
: time and store it in a field type slong? This might be more effic
Actually, just thinking about this a bit more, perhaps adding a function
call such as parseDate() might add too much overhead to the actual query,
perhaps it would be better to first convert the date to a timestamp at index
time and store it in a field type slong? This might be more efficient but
I've been using a simple variation of the boost function given in the
examples used to boost more recent documents:
recip(rord(creationDate),1,1000,1000)^1.3
While it seems to work pretty well, I've realised that this may not be quite
as effective as i had hoped given that the calculation is base
62 matches
Mail list logo
