rch faster returning less results ?
>>>> This is not going to work, as you need to score all of them as Erick
>>>> explained.
>>>>
>>>> Function query ( as Mikhail specified) will run on a per document basis (
>>>> if
>>>> I am correct), so if your idea was to speed up the things, this is not
>>>> going
>>>> to work.
>>>>
>>>> It makes much more sense to refine your system to improve relevancy if your
>>>> concern is to have more relevant docs.
>>>> If your concern is just to not show that many pages, you can limit that
>>>> client side.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> -
>>>> ---
>>>> Alessandro Benedetti
>>>> Search Consultant, R&D Software Engineer, Director
>>>> Sease Ltd. - www.sease.io
>>>> --
>>>> View this message in context: http://lucene.472066.n3.
>>>> nabble.com/Filtering-results-by-minimum-relevancy-score-
>>>> tp4329180p4329295.html
>>>> Sent from the Solr - User mailing list archive at Nabble.com.
>>>>
>>>
>>>
text:
http://lucene.472066.n3.nabble.com/Filtering-results-by-minimum-relevancy-score-tp4329180p4329715.html
Sent from the Solr - User mailing list archive at Nabble.com.
oncern is to have more relevant docs.
If your concern is just to not show that many pages, you can limit that
client side.
-
---
Alessandro Benedetti
Search Consultant, R&D Software Engineer, Director
Sease Ltd. - www.sease.io
--
View this message in context: http://luc
Thank you! That worked.
From: Ahmet Arslan
Date: Wednesday, April 12, 2017 at 3:15 PM
To: "solr-user@lucene.apache.org" , David Kramer
Subject: Re: Filtering results by minimum relevancy score
Hi,
I cannot find it. However it should be something like
q=hello&fq={!frange
relevant docs.
> > If your concern is just to not show that many pages, you can limit
> that
> > client side.
> >
> >
> >
> >
> >
> >
> > -
> > ---
> > Alessandro Benedetti
> > Search Consultant, R&D Software Engineer, Director
> > Sease Ltd. - www.sease.io
> > --
> > View this message in context: http://lucene.472066.n3.
> > nabble.com/Filtering-results-by-minimum-relevancy-score-
> > tp4329180p4329295.html
> > Sent from the Solr - User mailing list archive at Nabble.com.
> >
>
>
>
>
>
>
> -
> ---
> Alessandro Benedetti
> Search Consultant, R&D Software Engineer, Director
> Sease Ltd. - www.sease.io
> --
> View this message in context: http://lucene.472066.n3.
> nabble.com/Filtering-results-by-minimum-relevancy-score-
> tp4329180p4329295.html
> Sent from the Solr - User mailing list archive at Nabble.com.
>
your concern is just to not show that many pages, you can limit that
>> client side.
>>
>>
>>
>>
>>
>>
>> -
>> ---
>> Alessandro Benedetti
>> Search Consultant, R&D Software Engineer, Director
>> Sease Ltd. - www.sease.io
>> --
>> View this message in context: http://lucene.472066.n3.
>> nabble.com/Filtering-results-by-minimum-relevancy-score-
>> tp4329180p4329295.html
>> Sent from the Solr - User mailing list archive at Nabble.com.
>>
>
>
> If your concern is just to not show that many pages, you can limit that
> client side.
>
>
>
>
>
>
> -
> ---
> Alessandro Benedetti
> Search Consultant, R&D Software Engineer, Director
> Seas
is just to not show that many pages, you can limit that
> client side.
>
>
>
>
>
>
> -
> ---
> Alessandro Benedetti
> Search Consultant, R&D Software Engineer, Director
> Sease Ltd. - www.sease.io
> --
> View this message in context: http://lucen
Well, just because ES has it doesn't mean it's A Good Thing. IMO, it's
just a "feel good" kind of thing for people who don't really
understand scoring.
>From that page: "Note, most times, this does not make much sense, but
is provided for advanced use cases."
I've written enough weasel-worded cav
On 4/10/2017 8:59 AM, David Kramer wrote:
> I’ve done quite a bit of searching on this. Pretty much every page I
> find says it’s a bad idea and won’t work well, but I’ve been asked to
> at least try it to reduce the number of completely unrelated results
> returned. We are not trying to normalize
tor
> Sease Ltd. - www.sease.io
> --
> View this message in context: http://lucene.472066.n3.
> nabble.com/Filtering-results-by-minimum-relevancy-score-
> tp4329180p4329489.html
> Sent from the Solr - User mailing list archive at Nabble.com.
>
Consultant, R&D Software Engineer, Director
Sease Ltd. - www.sease.io
--
View this message in context:
http://lucene.472066.n3.nabble.com/Filtering-results-by-minimum-relevancy-score-tp4329180p4329489.html
Sent from the Solr - User mailing list archive at Nabble.com.
---
> Alessandro Benedetti
> Search Consultant, R&D Software Engineer, Director
> Sease Ltd. - www.sease.io
> --
> View this message in context: http://lucene.472066.n3.
> nabble.com/Filtering-results-by-minimum-relevancy-score-
> tp4329180p4329295.html
> Sent from the Solr - User mailing list archive at Nabble.com.
>
concern is just to not show that many pages, you can limit that
client side.
-
---
Alessandro Benedetti
Search Consultant, R&D Software Engineer, Director
Sease Ltd. - www.sease.io
--
View this message in context:
http://lucene.472066.n3.nabble.com/Filtering-results-by-min
Here we go
https://cwiki.apache.org/confluence/display/solr/Other+Parsers#OtherParsers-FunctionRangeQueryParser
.
But it's %100 YAGNI. You'd better tweak search to be more precise.
On Mon, Apr 10, 2017 at 7:12 PM, Ahmet Arslan
wrote:
> Hi,
> I remember that this is possible via frange query pars
Hi,
I remember that this is possible via frange query parser.But I don't have the
query string at hand.
Ahmet
On Monday, April 10, 2017, 9:00:09 PM GMT+3, David Kramer
wrote:
I’ve done quite a bit of searching on this. Pretty much every page I find says
it’s a bad idea and won’t work well, but
Well, that's rather the point, the low-scoring docs aren't unrelated,
someone just thinks they are.
Flippancy aside, the score is, as you've researched, a bad gauge.
Since Lucene has to compute the score of a doc before it knows the
score, at any point in the collection process you may get a doc t
I’ve done quite a bit of searching on this. Pretty much every page I find says
it’s a bad idea and won’t work well, but I’ve been asked to at least try it to
reduce the number of completely unrelated results returned. We are not trying
to normalize the number, or display it as a percentage, an
Thanks a lot for both of your answers! The QParserPlugin is probably
what I meant, but join queries also look interesting and like the could
maybe solve my use case, too, without any custom code.
However, since this would make it impossible (I think) to have a score
for the results but I do want
It depends on your use case. What is you custom criteria how is stored etc.
For example I had two tables, lets say items and permissions tables.
Permissions table was holding itemId,userId pairs. Meaning userId can see this
itemId. My initial effort was index items and add a multivalued field
What you're looking for is a QParserPlugin. Here is an example:
http://svn.apache.org/viewvc/lucene/dev/tags/lucene_solr_4_6_0/solr/core/src/java/org/apache/solr/search/FunctionRangeQParserPlugin.java?revision=1544545&view=markup
You're probably want to implement the QParserPlugin as PostFilter.
Hi,
I'm currently looking at writing my first Solr plugin, but I could not
really find any "overview" information about how a Solr request works
internally, what the control flow is and what kind of plugins are
available to customize this at which point. The Solr wiki page on
plugins [1], in
Thanks Yonik!!
The join functionality is proving extremely useful for us in a specific use
case - we're really looking forward to join and other cool features coming
in Solr4!!
Mike
On Wed, Feb 1, 2012 at 3:30 PM, Yonik Seeley wrote:
> Thanks for your persistence in tracking this down Mike!
> I
Thanks for your persistence in tracking this down Mike!
I'm going to start looking into this now...
-Yonik
lucidimagination.com
On Thu, Jan 26, 2012 at 11:06 PM, Mike Hugo wrote:
> I created issue https://issues.apache.org/jira/browse/SOLR-3062 for this
> problem. I was able to track it down
I've been looking into this a bit further and am trying to figure out why
the FQ isn't getting applied.
Can anyone point me to a good spot in the code to start looking at how FQ
parameters are applied to query results in Solr4?
Thanks,
Mike
On Thu, Jan 26, 2012 at 10:06 PM, Mike Hugo wrote:
>
I created issue https://issues.apache.org/jira/browse/SOLR-3062 for this
problem. I was able to track it down to something in this commit -
http://svn.apache.org/viewvc?view=revision&revision=1188624 (LUCENE-1536:
Filters can now be applied down-low, if their DocIdSet implements a new
bits() metho
Hello,
I'm trying out the Solr JOIN query functionality on trunk. I have the
latest checkout, revision #1236272 - I did the following steps to get the
example up and running:
cd solr
ant example
java -jar start.jar
cd exampledocs
java -jar post.jar *.xml
Then I tried a few of the sample queries
Good luck, and let us know what the results are. About dropping the cache.. That
shouldn't be a problem, it should just be computed when your
component is called
the first time, so starting the server (or opening a new searcher)
should re-compute
it. Your filters shouldn't be very big, just maxDoc
On Thu, Aug 18, 2011 at 02:32:48PM -0400, Erick Erickson wrote:
> Hmmm, I'm still not getting it...
>
> You have one or more lists. These lists change once a month or so. Are
> you trying
> to include or exclude the documents in these lists?
In our specific case to include *only* the documents ha
Hmmm, I'm still not getting it...
You have one or more lists. These lists change once a month or so. Are
you trying
to include or exclude the documents in these lists? And do the authors you want
to include or exclude change on a per-query basis or would you be all set if you
just had a filter tha
On Thu, Aug 18, 2011 at 08:36:08AM -0400, Erick Erickson wrote:
> How does this list of authors get selected? The reason I'm asking is
> I'm wondering
> if you can "define the problem away". In other words, I'm wondering if this
> is an XY problem (http://people.apache.org/~hossman/#xyproblem).
:-
How does this list of authors get selected? The reason I'm asking is
I'm wondering
if you can "define the problem away". In other words, I'm wondering if this
is an XY problem (http://people.apache.org/~hossman/#xyproblem).
I can't imagine you expect a user to specify up to 2k authors, so there mu
On Tue, Aug 16, 2011 at 07:56:51AM +, tomas.zer...@axelspringer.de wrote:
> Hello, Solrs
>
> we are trying to filter out documents written by (one or more of) the authors
> from
> a mediumish list (~2K). The document set itself is in the millions.
[...]
Sorry. Forgot to say that we are usin
Hello, Solrs
we are trying to filter out documents written by (one or more of) the authors
from
a mediumish list (~2K). The document set itself is in the millions.
Apart from the obvious approach of building a huge OR-list and appending it
to the query, it seems that writing a Lucene[1] filter (
I've seen references to score filtering in the list archives with frange
being the suggested solution, but I have a slightly different problem that I
don't think frange will solve. I basically want to drop a portion of the
results based on their score in relation to the other scores in the result
s
> As part of solr results i am able to get the max score.If i
> want to filter
> the results based on the max score, let say the max
> score is 10 And i need
> only the results between max score to 50 % of max
> score.This max score is
> going to change dynamically.How can we implement this?Do we
customize the solr?Please any suggestions.
Regards,
JS
--
View this message in context:
http://lucene.472066.n3.nabble.com/Filtering-results-based-on-score-tp1819769p1819769.html
Sent from the Solr - User mailing list archive at Nabble.com.
> Hi
> I want to add a filter to my query which takes documents
> whose "city"
> field has either Bangalore of cochin or Bombay. how do i do
> this?
>
> fq=city:bangalore&fq=city:bombay& fq=city:cochin
> will take the
> intersection. I need the union.
fq=city:(bangalore OR cochin OR bombay)
sam
Hi
I want to add a filter to my query which takes documents whose "city"
field has either Bangalore of cochin or Bombay. how do i do this?
fq=city:bangalore&fq=city:bombay& fq=city:cochin will take the
intersection. I need the union.
Please help
Thanks
t; To: solr-user@lucene.apache.org
>> Sent: Thursday, September 18, 2008 7:35:43 PM
>> Subject: Re: Filtering results
>>
>> Otis,
>>
>> Would be reasonable to run a query like this
>>
>> http://localhost:8280/solr/select/?q=terms_x&version=2.2&
-- Lucene - Solr - Nutch
- Original Message
> From: ristretto.rb <[EMAIL PROTECTED]>
> To: solr-user@lucene.apache.org
> Sent: Thursday, September 18, 2008 7:35:43 PM
> Subject: Re: Filtering results
>
> Otis,
>
> Would be reasonable to run a query like thi
l requirements, but running
>> 1+10 queries doesn't sound good to me from scalability/performance point of
>> view.
>>
>> Otis
>> --
>> Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch
>>
>>
>>
>> - Original Mess
1+10 queries doesn't sound good to me from scalability/performance point of
> view.
>
> Otis
> --
> Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch
>
>
>
> - Original Message
>> From: ristretto.rb <[EMAIL PROTECTED]>
>> To: solr-user
-
Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch
- Original Message
> From: ristretto.rb <[EMAIL PROTECTED]>
> To: solr-user@lucene.apache.org
> Sent: Tuesday, September 16, 2008 6:45:02 PM
> Subject: Re: Filtering results
>
> thanks. very interesting
thanks. very interesting. The plot thickens. And, yes, I think
field collapsing is exactly what I'm after.
I'm am considering now trying this patch. I have a solr 1.2 instance
on Jetty. I looks like I need to install the patch.
Does anyone use that patch? Recommend it? The wiki page
(http:/
: 1. Identify all records that would match search terms. (Suppose I
: search for 'dog', and get 450,000 matches)
: 2. Of those records, find the distinct list of groups over all the
: matches. (Suppose there are 300.)
: 3. Now get the top ranked record from each group, as if you search
: just
Thanks for the reply Erik
Sorry for being vague. To be clear we have 1-2 million records, and
rough 12000-14000 groups.
Each record is in one and only one group.
I see it working something like this
1. Identify all records that would match search terms. (Suppose I
search for 'dog', and get 45
Personally, I'd send three requests for solr, one for each group.
&rows=1&fq=category:A ... and so on.
But that'd depend on how many groups you have.
One can always hack custom request handlers to do this sort of thing
all as a single request, but I'd guess it ain't that much slower to
ju
Hello All,
I'm looking for a way to filter results by some ranking mechanism.
For example...
Suppose you have 30 docs in an index, and they are in groups of 10, like this
A, 1
A, 2
:
A, 10
B, 1
B, 2
:
B, 10
C, 1
C, 2
:
C, 10
I would like to get 3 records back such that I get a single, "best"
50 matches
Mail list logo
