Only way to know is to try! ;)
You have a typo on “noika”.I’d use ‘bf’ instead of bq so as to specify the
function without the _val_ stuff.
Erik
> On Dec 7, 2018, at 02:19, Midas A wrote:
>
> Thanks Erik.
> Please confirm
> if keyword = "nokia"
> *bq=_val_:%22payload(vals_dpf,noika)%
Thanks Erik.
Please confirm
if keyword = "nokia"
*bq=_val_:%22payload(vals_dpf,noika)%22&defType=edismax*
*wil this query work for me ?.*
On Fri, Dec 7, 2018 at 12:12 PM Erik Hatcher wrote:
> This blog I wrote will help. Let us know how it goes.
>
> https://lucidworks.com/2017/09/14/s
This blog I wrote will help. Let us know how it goes.
https://lucidworks.com/2017/09/14/solr-payloads/
Erik
> On Dec 7, 2018, at 01:31, Midas A wrote:
>
> I have a field at my schema named *val_dpf* . I want that *val_dpf* should
> have payloaded values. i.e.
>
> noika|0.46
: Boost Query (bq) accepts lucene queries. E.g. bq=price:[50 TO 100]^100
: boost and bf parameters accept Function queries, e.g. boost=log(popularity)
while these statements are both true, they don't tell the full story.
for example you can also specify a function as a query using the
appropri
Hi Sara,
Boost Query (bq) accepts lucene queries. E.g. bq=price:[50 TO 100]^100
boost and bf parameters accept Function queries, e.g. boost=log(popularity)
Ahmet
On Tuesday, January 19, 2016 12:41 PM, Binoy Dalal
wrote:
You use boost functions when you wish to perform certain operations, lik
You use boost functions when you wish to perform certain operations, like
mathematical (reciprocal, sq. root etc.) on the actual field value during
boosting.
In boost queries, all you can do is specify a field optionally along with a
particular value to boost on.
On Tue, 19 Jan 2016, 14:22 shruti
Hi,
Both the query affect solr scoring but for relevancy we use boost query as
we can provide additional weights to a boost query but not to a function
query.
-
Regards
Shruti
--
View this message in context:
http://lucene.472066.n3.nabble.com/Boost-query-vs-function-query-in-edismax-query
is the readability that is stopping you to use the bq parameter with
all your roles ?
A custom function is off course a way, but why you think is going to
satisfy better your requirement in comparison with the bq ?
Cheers
On 13 November 2015 at 18:41, Andrea Open Source <
andrearoggerone.o.
Hi Alessandro,
Thanks for answering. Unfortunately bq is not enough as I have several roles
that I need to score in different ways. I was thinking of building a custom
function that reads the weights of the roles from solr config and applies them
at runtime. I am a bit concerned about performanc
ehehe your request is kinda delicate :
1) I can't store the
payload at index time
2) Passing all the weights at query time is not an option
So you seem to exclude all the possible solutions ...
Anyway, just thinking loud, have you tried the edismax query parser and the
boost query feature?
1) th
Thanks a lot Jack, it makes total sense. I check the config and default q.op
was set to OR, which was influencing the query.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Boost-Query-bq-syntax-usage-tp4161989p4162169.html
Sent from the Solr - User mailing list archive at N
dismax and then specify edismax for bq using the localParam notation.
-- Jack Krupansky
-Original Message-
From: Jack Krupansky
Sent: Tuesday, September 30, 2014 8:19 PM
To: solr-user@lucene.apache.org
Subject: Re: Boost Query (bq) syntax/usage
The "+" signs in the parsed b
solr-user@lucene.apache.org
Subject: Re: Boost Query (bq) syntax/usage
Thanks a lot Jack, makes sense. Just curios, if we used the following bq
entry in solrconfig xml
Source2:sfdc^6 Source2:downloads^5 Source2:topics^3
will it always be treated as an AND query ? Some of local results suggests
Thanks a lot Jack, makes sense. Just curios, if we used the following bq
entry in solrconfig xml
Source2:sfdc^6 Source2:downloads^5 Source2:topics^3
will it always be treated as an AND query ? Some of local results suggests
otherwise.
--
View this message in context:
http://lucene.472066.n3
A boost is basically an "OR" operation - it doesn't select any more or fewer
documents. So, three separate bq's are three OR terms. But your first bq is
a single query that ANDs three terms, and that AND-ed query is OR-ed with
the original query, so it only boosts documents that contain all thre
All of them work like a charm! Thanks, Chris.
On Mon, Mar 3, 2014 at 1:28 PM, Chris Hostetter wrote:
>
> : But this query does not work:
> :
> : q={!boost
> : b=if(exists(query({!v='user_type:ADMIN'})),10,1)}id:1&rows=1&fl=*,score
> : It gives an error like this:
>
> The problem is the way you a
: But this query does not work:
:
: q={!boost
: b=if(exists(query({!v='user_type:ADMIN'})),10,1)}id:1&rows=1&fl=*,score
: It gives an error like this:
The problem is the way you are trying to nest queries inside of each other
w/o any sort of quoting -- the parser has no indication that the "b"
gy.com]
> Sent: Tuesday, February 18, 2014 9:58 AM
> To: solr-user@lucene.apache.org
> Subject: Re: Boost Query Example
>
> Add debugQuery=true to your queries and look at the scoring in the "explain"
> section. From the intermediate scoring by field, you should be ab
al Message-
From: EXTERNAL Taminidi Ravi (ETI, Automotive-Service-Solutions)
Sent: Tuesday, February 18, 2014 9:50 AM
To: solr-user@lucene.apache.org ; michael.della.bi...@appinions.com
Subject: RE: Boost Query Example
Hi Michael, Thanks for the information.
Now I am trying with the query , bu
From: EXTERNAL Taminidi Ravi (ETI, Automotive-Service-Solutions)
Sent: Tuesday, February 18, 2014 9:50 AM
To: solr-user@lucene.apache.org ; michael.della.bi...@appinions.com
Subject: RE: Boost Query Example
Hi Michael, Thanks for the information.
Now I am trying with the query , but I am n
ache.org
Subject: Re: Boost Query Example
Hi,
Filter queries don't affect score, so boosting won't have an effect there.
If you want those query terms to get boosted, move them into the q parameter.
http://wiki.apache.org/solr/CommonQueryParameters#fq
Hope that helps!
Michael Della B
Hi,
Filter queries don't affect score, so boosting won't have an effect there.
If you want those query terms to get boosted, move them into the q
parameter.
http://wiki.apache.org/solr/CommonQueryParameters#fq
Hope that helps!
Michael Della Bitta
Applications Developer
o: +1 646 532 3062
app
final boost query will be.
For now I will try to avoid using dismax and will continue to play around with
it.
Thanks again,
Will
-Original Message-
From: Jan Høydahl [mailto:jan@cominvent.com]
Sent: Saturday, March 23, 2013 7:51 PM
To: solr-user@lucene.apache.org
Subject: Re: Boost
grant,institution,investigator,investigatoraffiliation,keywordheading,keywords,nlmjournalname,origtitle,otherabstract,personname,primaryauthor,protocolconcept,spaceflight,substance,title
> product(10,query({!dismax qf="title"
> v="treatment"},0))
> true
>
013 8:07 PM
To: solr-user@lucene.apache.org
Subject: Re: Boost query parameter with Lucid parser and using query
FunctionQuery
Why would you use dismax for the query() when you want to match a simple term
to one field?
If you share &echoParams=all the answer may lie somewhere therein?
--
Jan
Why would you use dismax for the query() when you want to match a simple term
to one field?
If you share &echoParams=all the answer may lie somewhere therein?
--
Jan Høydahl, search solution architect
Cominvent AS - www.cominvent.com
Solr Training - www.solrtraining.com
23. mars 2013 kl. 00:07
You'll have to contact Lucid's support for questions about their code. (I've
been away from that code too long to recall much about it.)
-- Jack Krupansky
-Original Message-
From: Miller, Will Jr
Sent: Friday, March 22, 2013 7:07 PM
To: solr-user@lucene.apache.org
Subject: Boost query
I tried that, didn't seem to affect anything.
I think it only works between fields and not within a field.
On Thu, Dec 8, 2011 at 10:00 AM, Marc SCHNEIDER
wrote:
> Hi,
>
> Maybe you could have a look at this :
> http://wiki.apache.org/solr/DisMaxQParserPlugin#tie_.28Tie_breaker.29
>
> Marc.
>
> O
Hi,
Maybe you could have a look at this :
http://wiki.apache.org/solr/DisMaxQParserPlugin#tie_.28Tie_breaker.29
Marc.
On Wed, Dec 7, 2011 at 5:48 PM, John wrote:
> I have a complex edismax query:
>
>
> facet=true&facet.mincount=0&qf=title^0.08+categorysearch^0.05+abstract^0.03+body^0.1&wt=java
On Jun 18, 2009, at 10:54 AM, Vicky_Dev wrote:
is there any way to boost fields in standard query parser itself?
You can boost terms using field:term^2.0 syntax
See http://wiki.apache.org/solr/SolrQuerySyntax and down into http://lucene.apache.org/java/2_4_0/queryparsersyntax.html
for more
Hi Hossman,
We are also facing similar issue:
is there any way to boost fields in standard query parser itself?
~Vikrant
hossman wrote:
>
>
> : The reason I brought the question back up is that hossman said:
> ...
> : I tried it and it didn't work, so I was curious if I was still do
: The reason I brought the question back up is that hossman said:
...
: I tried it and it didn't work, so I was curious if I was still doing
: something wrong.
no ... i'm just a foolish foolish man who says things with a lot of
authority even though i clearly don't know what i'm talking
nk it might help if you send the actual URL you are using.
>>
>>
>> Otis
>> --
>> Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch
>>
>>
>>
>>
>>
>> From: CameronL <[EMAIL PROTECTED]>
>> To: solr-user@
D]>
To: solr-user@lucene.apache.org
Sent: Tuesday, November 11, 2008 9:12:28 PM
Subject: Re: Boost Query effect with Standard Request Handler
So the bq parameter works with the standard request handler (I don't
have to
specify defType=dismax)??
I've been running a few tests and it doesn't s
Nutch
From: CameronL <[EMAIL PROTECTED]>
To: solr-user@lucene.apache.org
Sent: Tuesday, November 11, 2008 9:12:28 PM
Subject: Re: Boost Query effect with Standard Request Handler
So the bq parameter works with the standard request handler (I don't have to
specify defType=dismax)??
I&#
So the bq parameter works with the standard request handler (I don't have to
specify defType=dismax)??
I've been running a few tests and it doesn't seem to be picking up the bq.
I've boosted one of the values very high (like 1000) compared to the other
fields and it doesn't seem to be affecting
: I'm trying to create the boost query (bq parameter) effect with the standard
: request handler. Unfortunately, going to the dismax handler isn't really an
: option for me, so I'm trying to create a similar effect.
as of SOlr 1.3 -- the "SearchHandler" (which superclasses and replaces the
old
37 matches
Mail list logo
