used, and then get replaced
by Solr code.
Many thanks,
Markus
-Original message-
> From:Markus Jelsma
> Sent: Thursday 22nd November 2018 15:39
> To: solr-user@lucene.apache.org; solr-user
> Subject: RE: KeywordRepeat, stemming, (single term) synonyms and minimum
&g
kus Jelsma
> Sent: Sunday 18th November 2018 23:21
> To: solr-user@lucene.apache.org; solr-user
> Subject: RE: KeywordRepeat, stemming, (single term) synonyms and minimum
> should match (edismax)
>
> Hello,
>
> Apologies for bothering you all again, but i really need
arkus
-Original message-
> From:Markus Jelsma
> Sent: Tuesday 13th November 2018 9:52
> To: solr-user
> Subject: KeywordRepeat, stemming, (single term) synonyms and minimum should
> match (edismax)
>
> Hello, apologies for this long winded e-mail.
>
> O
Hello, apologies for this long winded e-mail.
Our fields have KeywordRepeat and language specific filters such as a stemmer,
the final filter at query-time is SynonymGraph. We do not use
RemoveDuplicatesFilter for those of you wondering why when you see the parsed
queries below, this is due to
Anomaly Detection
Solr & Elasticsearch Consulting Support Training - http://sematext.com/
> On 13 Nov 2017, at 11:22, Vincenzo D'Amore wrote:
>
> Hi All,
>
> Not sure if what I'm asking is possible, but I'm looking for a way to
> define minimum should match (&
Best,
Erick
On Mon, Nov 13, 2017 at 2:22 AM, Vincenzo D'Amore wrote:
> Hi All,
>
> Not sure if what I'm asking is possible, but I'm looking for a way to
> define minimum should match ("mm") only for few fields in a query.
>
> And if possibile, is there a
Hi All,
Not sure if what I'm asking is possible, but I'm looking for a way to
define minimum should match ("mm") only for few fields in a query.
And if possibile, is there any chance to configure this behaviour in a
request handler in solrconfig.xml?
Best regards,
Vincenzo
Hi Myron,
Can you give me an example of this?
http://grokbase.com/t/lucene/solr-user/105jjpxa2x/minimum-should-match-on-subquery-level
<http://grokbase.com/t/lucene/solr-user/105jjpxa2x/minimum-should-match-on-subquery-level>
Regards,
Rahul
e someone else can confirm this.
On Wed, 16 Dec 2015, 16:56 Ron van der Vegt
wrote:
Hi,
I'm currently searching with the following query: q="sony+led+tv".
The minimum should match setting is set on: mm=2<65%.
So when there are more then two terms, at least 65% of the t
van der Vegt
> wrote:
>
>> Hi,
>>
>> I'm currently searching with the following query: q="sony+led+tv".
>> The minimum should match setting is set on: mm=2<65%.
>> So when there are more then two terms, at least 65% of the terms should
>> match.
n Wed, 16 Dec 2015, 16:56 Ron van der Vegt
wrote:
> Hi,
>
> I'm currently searching with the following query: q="sony+led+tv".
> The minimum should match setting is set on: mm=2<65%.
> So when there are more then two terms, at least 65% of the terms should
> mat
Hi,
I'm currently searching with the following query: q="sony+led+tv".
The minimum should match setting is set on: mm=2<65%.
So when there are more then two terms, at least 65% of the terms should
match.
I'm not using the StopFilterFactory.
When turnin
: Thanks Chris. That worked.. just one correction instead of *df -> qf *
if you're using multiple fields (with optional boosts) then yes, you need
qf ... but in your examle you knew exactly which (one) field you wanted,
and df should work fine for that -- because qf defaults to df.
-Hoss
{!dismax df=features mm=2}power ipod
> fq = {!dismax df=cat mm=2}electronics connector
>
>
>
> -Hoss
>
>
> --
> If you reply to this email, your message will be added to the discussion
> below:
>
> http://lucene.472066.n3.
: query something like
:
:
http://localhost:8983/solr/select?q=(category:lcd+OR+category:led+OR+category:plasma)+AND+(manufacture:sony+OR+manufacture:samsung+OR+manufacture:apple)&facet.field=category&facet.field=manufacture&fl=id&mm=2
Here's an example of something similar using the Solr 4.3 e
h+for+Simple+Queries
-- Jack Krupansky
-Original Message-
From: anand_solr
Sent: Monday, June 17, 2013 11:30 PM
To: solr-user@lucene.apache.org
Subject: Re: mm (Minimum 'Should' Match)
Thank Jack. Do you have any link to documents where I can refer for more?
I saw one of
gt; The LucidWorks Search query parser does support minMatch at any level,
> such
> as:
>
> (...)~2 AND (...)~2
>
> -- Jack Krupansky
>
> -Original Message-
> From: anand_solr
> Sent: Monday, June 17, 2013 10:14 PM
> To: [hidden email] <http://user/SendEm
riginal Message-
From: anand_solr
Sent: Monday, June 17, 2013 10:14 PM
To: solr-user@lucene.apache.org
Subject: mm (Minimum 'Should' Match)
I am not sure if this is supported out of box in Solr.
Search by giving multiple facet fields and query containing set of values
for each facet fie
I am not sure if this is supported out of box in Solr.
Search by giving multiple facet fields and query containing set of values
for each facet field & minimum should match parameter for each facets. The
result should be document contains facets with minimum match.
Eg: solr documents of
: Seem to have a solution but I am still trying to figure out how/why it works.
:
: Addition of "defType=edismax" in the boost query seem to honor "MM" and
: correct boosting based on external file source.
You didn't bost enough details in your original question to be 100%
certain (would have
amp;qq=hot chicken wings
--
View this message in context:
http://lucene.472066.n3.nabble.com/Minimum-Should-Match-not-enforced-with-External-Field-Function-Query-with-boost-tp2985564p3032143.html
Sent from the Solr - User mailing list archive at Nabble.com.
Hello
"Minimum Should Match" does not seem to be working when I am using the boost
with external field scoring (I followed
http://dev.tailsweep.com/solr-external-scoring/ example to implement
external field scoring.)
I am using a month old solr trunk build (4.0).
Thanks for help.
A
Thanks a lot for reply.
But I've already figured out that nested queries can help me to implement
what I was looking for.
-Myron
2010/5/28 Chris Hostetter
>
> : I need to use Lucene's `minimum number should match` option of
> BooleanQuery
> : on Solr.
>
> unfortunately, the Lucene QueryParser
: I need to use Lucene's `minimum number should match` option of BooleanQuery
: on Solr.
unfortunately, the Lucene QueryParser doesn't support any way of
manipulating the minNumberSHouldMatch property of BooleanQueries specified
in that syntax.
I'm not sure of anyway to do what you're looking
Hi All
I need to use Lucene's `minimum number should match` option of BooleanQuery
on Solr.
Actually I need to do the same as DisMaxRequestHandler's `mm` parameter does
but to use it on subquery level,
i.e. I have complex query which consists of several Boolean subqueries and I
need to specify di
: thank you for joining the discussion :).
Heh ... no problem, i was a little behind on my mail for a while there ...
but i'm catching up.
: 2) If I understood the API-documentation right, the behaviour of the
: FieldQParser depends exactly on what I've defined in my analyzer.
right ... it's
re two another understanding - questions:
What does WDF mean and what does HTE stand for?
Thank you very much!
Kind regards
- Mitch
--
View this message in context:
http://lucene.472066.n3.nabble.com/Minimum-Should-Match-the-other-way-round-tp694867p742797.html
Sent from the Solr - User mailing list archive at Nabble.com.
: However, maybe I missunderstood your point:
: "- Pick MAX_LEN Based On Number Of Query Clauses From Super"
: since I thought, that the number of query clauses depends on the number of
: whitespaces in my query. If I am wrong, and it depends on the result of my
: analyzer-chain, there is no prob
Does this number already consider the number of clauses (or what I really
mean: token) after the analyzer has worked on them?
It would be really nice to feel certain of that.
Kind regards
- Mitch
--
View this message in context:
http://n3.nabble.com/Minimum-Should-Match-the-other-way-round-tp694867
r Of Query Clauses From Super"
since I thought, that the number of query clauses depends on the number of
whitespaces in my query. If I am wrong, and it depends on the result of my
analyzer-chain, there is no problem. But I am not sure, if this is the case
or not.
Thank you for
: However, I got some doubts on this: What about queries that should be
: filtered with the WordDelimiterFilter. This could make a large difference to
: a none-delimiter-filtered MAX_LEN *and* it has got a protwords param. I
: can't instantiate a new WordDelimiterFilter everytime I do a query, so
way, I will try to implement it next
time.
- Mitch
--
View this message in context:
http://n3.nabble.com/Minimum-Should-Match-the-other-way-round-tp694867p703353.html
Sent from the Solr - User mailing list archive at Nabble.com.
On Apr 7, 2010, at 7:40 AM, MitchK wrote:
I can't believe that Solr isn't caching data like the synonym.txt's
etc.
Solr does cache these, look at the implementation of
SynonymFilterFactory where it keeps SynonymMap.
Are there no ideas how to access them?
There is a public getSynonymMap
I can't believe that Solr isn't caching data like the synonym.txt's etc.
Are there no ideas how to access them?
- Mitch
--
View this message in context:
http://n3.nabble.com/Minimum-Should-Match-the-other-way-round-tp694867p702761.html
Sent from the Solr - User mailing
stopwords.txt or protwords.txt, I want to access those (as I
understood cached) ressources.
- Mitch
--
View this message in context:
http://n3.nabble.com/Minimum-Should-Match-the-other-way-round-tp694867p698796.html
Sent from the Solr - User mailing list archive at Nabble.com.
is message in context:
http://n3.nabble.com/Minimum-Should-Match-the-other-way-round-tp694867p698683.html
Sent from the Solr - User mailing list archive at Nabble.com.
: > However, I am searching for a solution that does something like: "this is my
: > query" and the document has to consist of this query plus maximal - for
: > example - two another terms?
...
: Not quite following. It sounds like you are saying you want to favor
: docs that are shorter,
On Apr 3, 2010, at 10:18 AM, MitchK wrote:
>
> Hello,
>
> I want to tinkle a little bit with Solr, so I need a little feedback:
> Is it possible to define a Minimum Should Match for the document itself?
>
> I mean, it is possible to say, that a query "this is my qu
Hello,
I want to tinkle a little bit with Solr, so I need a little feedback:
Is it possible to define a Minimum Should Match for the document itself?
I mean, it is possible to say, that a query "this is my query" should only
match a document, if the document matches 3 of the four que
Thanks Christ. I probably have to repost this in Lucene mailing list.
On Sun, Mar 23, 2008 at 9:49 AM, Chris Hostetter <[EMAIL PROTECTED]>
wrote:
>
> the topic has come up before on the lucene java lists (allthough i can't
> think of any good search terms to find the old threads .. I can't reall
the topic has come up before on the lucene java lists (allthough i can't
think of any good search terms to find the old threads .. I can't really
remember how people have discribed this idea in the past)
I don't remember anyone ever suggesting/sharing a general purpose
solution intrinsicly mor
Hi all,
I thought many people would encounter the situation I'm having here.
Basically, we'd like to have a PhraseQuery with "minimum should match"
property similar to BooleanQuery. Consider the query "Senior Java
Developer":
1) I'd like to do a PhraseQuery on
: Is there a default "mm" value (minimum should match) for the DisMaxReqHandler?
yeah ... it's "100%" (a more sensible default then "1" was my
justification at the time i believe.)
: should match? Is this a bug, or an undocumented feature? That is, shou
Is there a default "mm" value (minimum should match) for the
DisMaxReqHandler? I have two optional clauses and I have not declared
any mm value in my config and I am not getting results, despite
knowing that both clauses return results individually. In debugging,
Solr, is
44 matches
Mail list logo
