thanks guys, that worked
On 6 December 2013 23:55, Shawn Heisey wrote:
> On 12/6/2013 8:58 AM, Peri Stracchino wrote:
>
>> I'm trying to upgrade a solr installation from 1.4 (yes, really) to 4.6.0,
>> and I find our requesthandler was solr.DisMaxRequestHandler, which is now
>> not only deprecat
On 12/6/2013 8:58 AM, Peri Stracchino wrote:
I'm trying to upgrade a solr installation from 1.4 (yes, really) to 4.6.0,
and I find our requesthandler was solr.DisMaxRequestHandler, which is now
not only deprecated but deleted from solr-core-4.6.0.jar. Can anyone
advise on suitable alternatives,
Try edismax it's an improved dismax. Warning, though, it behaves a bit
differently than dismax so you'll have to look again at the results and
perhaps tweak.
Best,
Erick
On Dec 6, 2013 10:58 AM, "Peri Stracchino"
wrote:
> Hi
> I'm trying to upgrade a solr installation from 1.4 (yes, really) to
Hi
I'm trying to upgrade a solr installation from 1.4 (yes, really) to 4.6.0,
and I find our requesthandler was solr.DisMaxRequestHandler, which is now
not only deprecated but deleted from solr-core-4.6.0.jar. Can anyone
advise on suitable alternatives, or was there any form of direct
replacement
thanks a lot ;)
--
View this message in context:
http://lucene.472066.n3.nabble.com/Solr-4-4-problem-with-loading-DisMaxRequestHandler-tp4085842p4087449.html
Sent from the Solr - User mailing list archive at Nabble.com.
You must have upgraded from a very old release of Solr. There is no
DisMaxRequestHandler.
Just use the standard request handler for "/select" in the Solr example
config and then add a boolean for the "defType" parameter to set it to
dismax to enable the dismax que
In my dist folder I have all the defaults library and also in the lib folder
into my core
please, any suggests?
Thanks in advance.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Solr-4-4-problem-with-loading-DisMaxRequestHandler-tp4085842.html
Sent from the Solr - User mailing
; View this message in context:
> http://lucene.472066.n3.nabble.com/DismaxRequestHandler-tp903641p904142.html
> Sent from the Solr - User mailing list archive at Nabble.com.
>
Joe,
please, can you provide an example of what you are thinking of?
Subqueries with Solr... I've never seen something like that before.
Thank you!
Kind regards
- Mitch
--
View this message in context:
http://lucene.472066.n3.nabble.com/DismaxRequestHandler-tp903641p904142.html
Sent
en there are matches that are nowhere each other
>
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/DismaxRequestHandler-tp903641p903641.html
> Sent from the Solr - User mailing list archive at Nabble.com.
>
View this message in context:
http://lucene.472066.n3.nabble.com/DismaxRequestHandler-tp903641p903641.html
Sent from the Solr - User mailing list archive at Nabble.com.
Okay, I will do so in future, if another problem like this occurs.
At the moment, everything is fine after I followed your suggestions.
Kind regards
- Mitch
--
View this message in context:
http://lucene.472066.n3.nabble.com/Short-DismaxRequestHandler-Question-tp775913p820355.html
Sent from
: I got a fundamental understanding question that Mike's posting did not
: answer:
: You say "q=apple iPhone & qf=title^5 manufacturer & mm=100%" is correct.
: That means:
: title: "iphone" -> matches "iphone" but not "apple"
: manufacturer: "apple" -> matches "apple" but not "iphone"
: According
stopwords "and, the, in". But all the others do not.
If I would turn the stopword-filter on at index-time, but off at query-time,
would this make a difference?
If you don't like to answer this question, because I should try it out, no
problem. In this case I will do so at Thursday after my exams.
Thank you all very much.
Have a nice Sunday!
- Mitch
--
View this message in context:
http://lucene.472066.n3.nabble.com/Short-DismaxRequestHandler-Question-tp775913p787228.html
Sent from the Solr - User mailing list archive at Nabble.com.
e at least one field
>> didn’t have stopwords, there was a clause included for that stopword
>> you entered.
(the blog post makes an incorrect assumption after that -- but the
paragraph above is dead on)
: Let me be sure, that I have understood your part about how the
: DisMaxRequestHa
Btw: This thread helps a lot to understand the difference between qf and pf
:-)
http://lucene.472066.n3.nabble.com/Dismax-query-phrases-td489994.html#a489995
--
View this message in context:
http://lucene.472066.n3.nabble.com/Short-DismaxRequestHandler-Question-tp775913p783379.html
Sent from
Works.
Solr does not know about the relation, however with the 100%mm-definition, I
can tell Solr
something like this in a more easier way.
c) what types of URLs you've already tried
Those I have shown here. No more.
Let me be sure, that I have understood your part about how the
DisMaxReque
: I need a minimum should match only on some fields, not on all.
You need to elaborate more on how you want things to work -- you've only
provided one example doc and one example quer, and indicated that you want
them to match -- you haven't explained:
a) what docs should *not* match the quer
b.de]
Sent: Tuesday, May 04, 2010 6:36 PM
To: solr-user@lucene.apache.org
Subject: Short DismaxRequestHandler Question
Hello community,
I need a minimum should match only on some fields, not on all.
Let me give you an example:
title: "Breaking News: New information about Solr 1.5"
category: d
ment AND title:(solr
development)^10 OR category:(solr development)^2
Any other ideas are welcome.
Thank you for the discussion.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Short-DismaxRequestHandler-Question-tp775913p776446.html
Sent from the Solr - User mailing list archive at Nabble.com.
Thank you for responsing.
This would be possible. However, I wouldn't like to do so, because a match
in "title" should boost higher than a match in "category".
--
View this message in context:
http://lucene.472066.n3.nabble.com/Short-DismaxRequestHandler-Question-
I think you could combine the minimum set of fields into one field at
the time of indexing, for example, you could concatenate 'category' and
'tag' at the time of querying (if you are using a database).
On 05/04/2010 09:06 AM, MitchK wrote:
Hello community,
I need a minimum should match only on
Mitch
--
View this message in context:
http://lucene.472066.n3.nabble.com/Short-DismaxRequestHandler-Question-tp775913p775913.html
Sent from the Solr - User mailing list archive at Nabble.com.
On Mar 3, 2010, at 12:26 PM, Christopher Bottaro wrote:
I have a couple of questions regarding the bf and bq params to the
DisMaxRequestHandler.
1) Can I specify them more than once? Ex:
bf=log(popularity)&bf=log(comment_count)
Yes, you can use multiple bf parameters, each addin
Hello,
I have a couple of questions regarding the bf and bq params to the
DisMaxRequestHandler.
1) Can I specify them more than once? Ex:
bf=log(popularity)&bf=log(comment_count)
2) When using bq, how can I specify what score to use for documents
not returned by the query? In other w
: no but you can set a default for the qf parameter with the same value
good call...
https://issues.apache.org/jira/browse/SOLR-1776
-Hoss
no but you can set a default for the qf parameter with the same value
On 02/15/2010 01:50 AM, Steve Radhouani wrote:
Hi there,
Can the option be used by the DisMaxRequestHandler?
Thanks,
-Steve
Hi there,
Can the option be used by the DisMaxRequestHandler?
Thanks,
-Steve
On Jan 8, 2010, at 9:31 AM, Chantal Ackermann wrote:
I've copied the dismax configuration to the custom handler, and it
works fine, now.
I have different velocity templates (=>different custom handlers),
so from quickly reading through your other suggestion I think that
would work with only
Thank you for your quick answer, Erik!
I've copied the dismax configuration to the custom handler, and it works
fine, now.
I have different velocity templates (=>different custom handlers), so
from quickly reading through your other suggestion I think that would
work with only one template/vel
Chantal -
You'll have to copy the configuration to your various handlers.
However, with the VelocityResponseWriter, you can use your existing
handlers and simply set wt=velocity on them by default, or set it from
the client with &wt=velocity appended to the query string. The
VelocityResp
Dear all,
happy New Year!
For my custom searchHandler (called /list) that uses the
VelocityResponseWriter I would like to use the existing dismax
configuration. Therefore I did NOT specify ANY dismax configuration in
that custom handler.
In short: it's not using (my existing) dismax at all,
On Jan 7, 2010, at 10:18 PM, Andy wrote:
Oh I see.
Is "popularityboost" the name of the parameter?
{!boost b=$popularityboost v=$qq}
log(popularity)
popularityboost is entirely arbitrary here. Use whatever name you
like, it's a simple substitution in the q p
Oh I see.
Is "popularityboost" the name of the parameter?
{!boost b=$popularityboost v=$qq}
log(popularity)
--- On Thu, 1/7/10, Erik Hatcher wrote:
From: Erik Hatcher
Subject: Re: DisMaxRequestHandler bf configuration
To: solr-user@lucene.apach
On Jan 7, 2010, at 9:51 PM, Andy wrote:
Thanks.
Can I use the standard request handler for this purpose? So
something like:
Yes, but...
{!boost b=$popularityboost v=
$qq}&popularityboost=log(popularity)
Or do I still need the dismax handler?
popularityboost needs to
: Re: DisMaxRequestHandler bf configuration
To: solr-user@lucene.apache.org
Date: Thursday, January 7, 2010, 4:56 AM
it wouldn't be q.alt though, just q, in the config file.
q.alt is typically *:*, it's the fall back query when no q is provided.
though, in thinking about it, q.alt would work
onik Seeley
Subject: Re: DisMaxRequestHandler bf configuration
To: solr-user@lucene.apache.org
Date: Wednesday, January 6, 2010, 8:42 PM
On Wed, Jan 6, 2010 at 8:24 PM, Andy wrote:
I meant can I do it with dismax without modifying every single
query? I'm accessing Solr through haystack and a
10, Yonik Seeley wrote:
From: Yonik Seeley
Subject: Re: DisMaxRequestHandler bf configuration
To: solr-user@lucene.apache.org
Date: Wednesday, January 6, 2010, 8:42 PM
On Wed, Jan 6, 2010 at 8:24 PM, Andy wrote:
> I meant can I do it with dismax without modifying every single query? I'm
uments
and set defaults for everything except qq.
-Yonik
http://www.lucidimagination.com
> --- On Wed, 1/6/10, Yonik Seeley wrote:
>
> From: Yonik Seeley
> Subject: Re: DisMaxRequestHandler bf configuration
> To: solr-user@lucene.apache.org
> Date: Wednesday, January 6, 201
uery by default.
--- On Wed, 1/6/10, Yonik Seeley wrote:
From: Yonik Seeley
Subject: Re: DisMaxRequestHandler bf configuration
To: solr-user@lucene.apache.org
Date: Wednesday, January 6, 2010, 7:48 PM
On Wed, Jan 6, 2010 at 7:43 PM, Andy wrote:
> So if I want to configure Solr to turn every
On Wed, Jan 6, 2010 at 7:43 PM, Andy wrote:
> So if I want to configure Solr to turn every query q=foo into q={!boost
> b=log(popularity)}foo, dismax wouldn't work but edismax would?
You can do it with dismax it's just that the syntax is slightly
more convoluted.
Check out the section on boo
On Wed, 1/6/10, Yonik Seeley wrote:
From: Yonik Seeley
Subject: Re: DisMaxRequestHandler bf configuration
To: solr-user@lucene.apache.org
Date: Wednesday, January 6, 2010, 7:09 PM
On Wed, Jan 6, 2010 at 2:43 AM, Andy wrote:
> I'd like to boost every query using {!boost b=log(populari
On Wed, Jan 6, 2010 at 2:43 AM, Andy wrote:
> I'd like to boost every query using {!boost b=log(popularity)}. But I'd
> rather not have to prepend that to every query. It'd be much cleaner for me
> to configure Solr to use that as default.
>
> My plan is to make Di
I'd like to boost every query using {!boost b=log(popularity)}. But I'd rather
not have to prepend that to every query. It'd be much cleaner for me to
configure Solr to use that as default.
My plan is to make DisMaxRequestHandler the default handler and add the
following to
rocess the 'qf' ?
>
> did you read any of the docs on dismax?
>
> http://wiki.apache.org/solr/DisMaxRequestHandler
>
> did you look at the "mm" param?
>
> http://wiki.apache.org/solr/DisMaxRequestHandler#mm
>
>
> -Hoss
>
>
>
-
: The 'qf' parameter used in the dismax seems to work with a 'AND' separator.
: I have much more results without dixmax. Is there any way to keep the same
: amount of document and process the 'qf' ?
did you read any of the docs on dismax?
http://wiki.apache
smax
explicit
0.01
text^0.5 title_ac^4.0 name_ac^4.0 authors_list_sm^4.0
--
View this message in context:
http://www.nabble.com/Relevant-results-with-DisMaxRequestHandler-tp24716870p24903219.html
Sent from the Solr - User mailing list archive at Nabble.com.
sage in context:
http://www.nabble.com/Relevant-results-with-DisMaxRequestHandler-tp24716870p24903143.html
Sent from the Solr - User mailing list archive at Nabble.com.
On Jul 29, 2009, at 6:55 AM, Vincent Pérès wrote:
Using the following query :
http://localhost:8983/solr/others/select/?debugQuery=true&q=anna%20lewis&rows=20&start=0&fl=*&qt=dismax
I get back around 100 results. Follow the two first :
Person:151
Victoria Davisson
Person:37
Anna Lewis
And
come
from the name_s field...) ?
A second general question... is it possible to boost a field if the query
match exactly the content of a field?
Thank you !
Vincent
--
View this message in context:
http://www.nabble.com/Relevant-results-with-DisMaxRequestHandler-tp24716870p24716870.html
Sen
: Date: Tue, 16 Jun 2009 21:26:37 +
: From: siping liu
: Subject: DisMaxRequestHandler usage
: q=(field1:hello OR field2:hello) AND (field3:world)
:
: Can I use dismax handler for this (applying the same search term on
: field1 and field2, but keep field3 with something separate)? If it
Hi,
I have this standard query:
q=(field1:hello OR field2:hello) AND (field3:world)
Can I use dismax handler for this (applying the same search term on field1 and
field2, but keep field3 with something separate)? If it can be done, what's the
advantage of doing it this way over using the s
: Still search on any field (?q=searchTerm) gives following error
: "The request sent by the client was syntactically incorrect (Invalid Date
: String:'searchTerm')."
because "searchTerm" isn't a valid date string
: Is this valid to define *_dt (i.e. date fields ) in solrConfig.xml ?
if you re
Hi,
We are facing issues while using dismaxrequesthandler for date fields.
We have to define date fields in of solrConfig.xml.
..
productPublicationDate_product_dt^1.0
as soon as we add this in solrConfig.xml, dismax stops working for other
attributes.
?q=searchterm&am
.e. date fields ) in solrConfig.xml ?
prerna07 wrote:
>
> Hi,
>
> We are facing issues while using dismaxrequesthandler for date fields.
> We have to define date fields in of solrConfig.xml.
>
>
> productPublicationDate_product_dt^1.0
> productPublicationDate_product_dt[N
On Jan 14, 2009, at 8:24 AM, prerna07 wrote:
We are facing issues while using dismaxrequesthandler for date fields.
We have to define date fields in of solrConfig.xml.
productPublicationDate_product_dt^1.0
productPublicationDate_product_dt[NOW-45DAYS TO NOW]^1.0
as soon as we add this in
Hi,
We are facing issues while using dismaxrequesthandler for date fields.
We have to define date fields in of solrConfig.xml.
productPublicationDate_product_dt^1.0
productPublicationDate_product_dt[NOW-45DAYS TO NOW]^1.0
as soon as we add this in solrConfig.xml, dismax stops working for
: I found a thread in the archive were someone mentioned the idea of
: making this behaviour configurable (which characters to strip from the
: query parameter). Is someone working on this or is my best option
: currently to implement this behaviour by copying code from
: DisMaxRequestHandler and
Hi,
I'm rather new to Solr and for my current projects came to the
conclusion that DisMaxRequestHandler is exactly the tool I need, except
that it doesn't allow prefix queries.
I found a thread in the archive were someone mentioned the idea of
making this behaviour configura
: Is there any way to make the DisMaxRequestHandler a bit more forgiving with
: user queries, I'm only getting results when the user enters a close to
: perfect match. I'd like to allow near matches if possible, but I'm not sure
: how to add something like this when special que
Is there any way to make the DisMaxRequestHandler a bit more forgiving with
user queries, I'm only getting results when the user enters a close to
perfect match. I'd like to allow near matches if possible, but I'm not sure
how to add something like this when special query synta
Chris Hostetter wrote:
: :
: : text^0.5 features^1.0 name^1.2 manu^1.1
: :
: > if the q param is: albino elephant ... what would it mean that text and
: > feature are mandatory? do both words have to appear in text and in
: > feature, or just one in each?
: What I wanted
: :
: : text^0.5 features^1.0 name^1.2 manu^1.1
: :
: > if the q param is: albino elephant ... what would it mean that text and
: > feature are mandatory? do both words have to appear in text and in
: > feature, or just one in each?
: What I wanted is that 'albino' 'eleph
Chris Hostetter wrote:
: Is it possible to specify precisely one or more mandatory fields in a
: DismaxRequestHandler?
what would the semantics making a field mandatory mean? considering your
specific example...
:
: text^0.5 features^1.0 name^1.2 sku^1.5 id^10.0 manu^1.1 cat^1.4
?
On 7/30/07, Chris Hostetter <[EMAIL PROTECTED]> wrote:
>
>
> : Is it possible to specify precisely one or more mandatory fields in a
> : DismaxRequestHandler?
>
> what would the semantics making a field mandatory mean? considering your
> specific example...
>
> :
: Is it possible to specify precisely one or more mandatory fields in a
: DismaxRequestHandler?
what would the semantics making a field mandatory mean? considering your
specific example...
:
: text^0.5 features^1.0 name^1.2 sku^1.5 id^10.0 manu^1.1 cat^1.4
:
:
Hello,
Is it possible to specify precisely one or more mandatory fields in a
DismaxRequestHandler?
Something like that:
explicit
0.01
text^0.5 features^1.0 name^1.2 sku^1.5 id^10.0 manu^1.1 cat^1.4
text^0.2 features^1.1 name^1.5 manu^1.4 manu_exact
datory/prohibited?" that's where the "mm" option comes in.
: > http://wiki.apache.org/solr/DisMaxRequestHandler
i *just* updated that wiki page on friday with some specifics on the
params and usage ... but by all means anyone else out there using
dismax, *PLEASE* update i
The 1 and 100% did it. But I am not sure how I can do the exact combination
(phrase).
Could you tell me, please?
On 02/07/07, Paul Borgermans <[EMAIL PROTECTED]> wrote:
Hi
Take a look at the query parameters it supports:
http://wiki.apache.org/solr/DisMaxRequestHandler
An exact combi
Hi
Take a look at the query parameters it supports:
http://wiki.apache.org/solr/DisMaxRequestHandler
An exact combination (phrase), all of the words or one are possible:
you can use the mm parameter (100% and 1 for your case).
Part of a word is not possible, nor explicit query fields in the q
Not sure you can, but if it helps you can use boosting in the standard
request handler:
post AND lettre _val_:"recip(popularityRank,1,1000,1000)^2.5"
-Nick
On 7/2/07, Thierry Collogne <[EMAIL PROTECTED]> wrote:
Hello,
I have a couple questions about the DismaxRequestHandle
Hello,
I have a couple questions about the DismaxRequestHandler. I am using it,
because I want to use the boosting mechanism, but I can't get the following
to work :
We also have an advanced search where users can search for :
* An exact combination of words
* All the
as mentioned, the warning is missleading in the case where you sort by
socre, i filed a bug as a reminder to fix it (and so people searching for
it will understand what's going on)
patches welcome! :)
http://issues.apache.org/jira/browse/SOLR-270
: WARNING: Invalid sort "score desc" was specifi
A little background:
I originally conceived of query operation chains (based on some of my
previous hacking in mechanical investing stock screens: select all
stocks; take top 10% lowest PE; then take the top 20 highest growth
rate; then sort descending by 13 week relative strength).
So, I thought
Because "score desc" is the default Lucene & Solr behavior when no explicit
sort is specified, QueryParsing.parseSort() returns a null sort so that the
non-sort versions of the query execution routines get called. However the
caller SolrPluginUtils.parseSort issues that warning whenever it gets
Hello all,
This is a minor issue and does not affect Solr operation,
but I could not find it in the issue tracking.
To reproduce:
- I set up a Solr server with the example docs indexed by
following the Solr tutorial.
- I clicked on the following example search under the
"Sorting" section:
76 matches
Mail list logo
