check out the videos on this website TROO.TUBE don't be such a
sheep/zombie/loser/NPC. Much love!
https://troo.tube/videos/watch/aaa64864-52ee-4201-922f-41300032f219
On Sat, May 9, 2020 at 4:29 PM Steven White wrote:
>
> Never mind, I found the answer. WordDelimiterFilterFactory is
> deprecated
Never mind, I found the answer. WordDelimiterFilterFactory is
deprecated and is replaced by WordDelimiterGraphFilterFactory.
Steve
On Sat, May 9, 2020 at 5:22 PM Steven White wrote:
> Hi everyone,
>
> Why I cannot find the filter solr.WordDelimiterFilterFactory at
> https://lucene.apache.org/
hi jack,
It worked with dismax. I was using a our search partner provided wrapper
around dismax and it seems like it has a bug.
I switched to dismax and all is working fine now.
Thanks for help
--
View this message in context:
http://lucene.472066.n3.nabble.com/solr-WordDelimiterFilterFactory-
To: solr-user@lucene.apache.org
Subject: Re: solr.WordDelimiterFilterFactory query time
hi jack,
thanks, i figured out the issue. It was settings during query and index time
--
View this message in context:
http://lucene.472066.n3.nabble.com/solr-WordDelimiterFilterFactory-query-time
hi jack,
thanks, i figured out the issue. It was settings during query and index time
--
View this message in context:
http://lucene.472066.n3.nabble.com/solr-WordDelimiterFilterFactory-query-time-tp3950045p3951811.html
Sent from the Solr - User mailing list archive at Nabble.com.
onday, April 30, 2012 11:56 AM
To: solr-user@lucene.apache.org
Subject: Re: solr.WordDelimiterFilterFactory query time
hi jack,
tried &qs=10 but unfortunately it does not seem to help.
Not sure what else could be wrong
abhay
--
View this message in context:
http://lucene.472066.n3.nabbl
hi jack,
tried &qs=10 but unfortunately it does not seem to help.
Not sure what else could be wrong
abhay
--
View this message in context:
http://lucene.472066.n3.nabble.com/solr-WordDelimiterFilterFactory-query-time-tp3950045p3951083.html
Sent from the Solr - User mailing list archive at Nabbl
hi jack,
tried &qs=10 but unfortunately it does not seem to help.
Not sure what else could be wrong
abhay
--
View this message in context:
http://lucene.472066.n3.nabble.com/solr-WordDelimiterFilterFactory-query-time-tp3950045p3951082.html
Sent from the Solr - User mailing list archive at Nabbl
hi jack & erick,
Thanks
I do have qs set in solrconfig for query handler dismax settings.
10
Still does not work
abhay
--
View this message in context:
http://lucene.472066.n3.nabble.com/solr-WordDelimiterFilterFactory-query-time-tp3950045p3951038.html
Sent from the Solr - User mailing list a
The &qs=1 request parameter should work for the dismax query parser as well
as edismax.
-- Jack Krupansky
-Original Message-
From: Erick Erickson
Sent: Monday, April 30, 2012 10:58 AM
To: solr-user@lucene.apache.org
Subject: Re: solr.WordDelimiterFilterFactory query time
See Ja
See Jack's comments about phrases, all your parsed
queries are phrases, and your indexed terms aren't
next to each other.
Best
Erick
On Mon, Apr 30, 2012 at 10:54 AM, abhayd wrote:
> hi Erick,
> autoGeneratePhraseQueries="false" is set for field type. And it works fine
> for standard query parse
hi Erick,
autoGeneratePhraseQueries="false" is set for field type. And it works fine
for standard query parser.
Problem seem to be when i start using dismax. As u suggested i checked
analysis tool and even after word delimiter is applied i see search term as
"blackberry 9801" so i dont think it s
When WDF filters blackberry9810 it will treat it as a sequence of tokens but
as if it were a phrase, like "blackberry 9810", with the two terms adjacent,
at least with the edismax query parser. I'm not sure what the other query
parsers do.
If you are using edismax, you can set the QS (query sl
Try attaching &debugQuery=on to your query and seeing if that helps
you understand what's going on. If that doesn't help, also look at
admin/analysis. If all that doesn't help, post your schema definition
for the field type and the results of &debugQuery=on (you might
look at: http://wiki.apache.or
blem... but
> it still seems to me that something isn't working the way it is supposed to
> in this particular case.
>
> - Demian
>
> > -Original Message-
> > From: Robert Muir [mailto:rcm...@gmail.com]
> > Sent: Friday, April 09, 2010 12:05 PM
> &g
sage-
> From: Robert Muir [mailto:rcm...@gmail.com]
> Sent: Friday, April 09, 2010 12:05 PM
> To: solr-user@lucene.apache.org
> Subject: Re: solr.WordDelimiterFilterFactory problem with hyphenated
> terms?
>
> but this behavior is correct, as you have position increments enabled.
&
gt; title:"love customs in in eighteenthcentury spain"
>
> (note the duplicate "in").
>
> - Demian
>
> > -Original Message-
> > From: Erick Erickson [mailto:erickerick...@gmail.com]
> > Sent: Thursday, April 08, 2010 11:20 AM
> >
cceeds:
title:"love customs in in eighteenthcentury spain"
(note the duplicate "in").
- Demian
> -Original Message-
> From: Erick Erickson [mailto:erickerick...@gmail.com]
> Sent: Thursday, April 08, 2010 11:20 AM
> To: solr-user@lucene.apache.org
> Su
Thanks, that'll keep me from running down the wrong path
Erick
On Thu, Apr 8, 2010 at 11:22 AM, Robert Muir wrote:
> right, its fixed only in the "new trunk":
> http://svn.apache.org/repos/asf/lucene/dev/trunk/
>
> nothing has been changed with regards to the solr 1.5 branch yet.
>
> On Thu
right, its fixed only in the "new trunk":
http://svn.apache.org/repos/asf/lucene/dev/trunk/
nothing has been changed with regards to the solr 1.5 branch yet.
On Thu, Apr 8, 2010 at 10:01 AM, Erick Erickson wrote:
> Your're right, it sure looks related. But according to that JIRA, it's
> fixed
>
to examine). Would you agree with this
> assessment? If not, what possible negative side effects am I forgetting
> about?
>
> thanks,
> Demian
>
> > -Original Message-
> > From: Erick Erickson [mailto:erickerick...@gmail.com]
> > Sent: Wednesday, April
sment? If not, what possible negative side effects am I forgetting about?
thanks,
Demian
> -Original Message-
> From: Erick Erickson [mailto:erickerick...@gmail.com]
> Sent: Wednesday, April 07, 2010 10:04 PM
> To: solr-user@lucene.apache.org
> Subject: Re: solr.WordDelimiterFi
Your're right, it sure looks related. But according to that JIRA, it's
fixed
in trunk and I'm pretty sure I have a very recent version that I built from
code I updated within the last few days.
I'll update tonight and double check. If it's still a problem I'll see if
I can write a test case illust
Erick, this sounds like https://issues.apache.org/jira/browse/SOLR-1852
On Wed, Apr 7, 2010 at 10:04 PM, Erick Erickson wrote:
> Well, for a quick trial using trunk, I had to remove the
> UnicodeNormalizationFactory, is that yours?
>
> But with that removed, I get the results you do, ASSUMING tha
Well, for a quick trial using trunk, I had to remove the
UnicodeNormalizationFactory, is that yours?
But with that removed, I get the results you do, ASSUMING that you've set
your default operator to AND in schema.xml...
Believe it or not, it all changes and all your queries return a hit if you
d
Hello. It has been a few weeks, and I haven't gotten any responses. Perhaps
my question is too complicated -- maybe a better approach is to try to gain
enough knowledge to answer it myself. My gut feeling is still that it's
something to do with the way term positions are getting handled by th
On Thu, Nov 20, 2008 at 9:20 AM, Daniel Rosher <[EMAIL PROTECTED]> wrote:
> I'm trying to index some content that has things like 'java/J2EE' but with
> solr.WordDelimiterFilterFactory and parameters [generateWordParts="1"
> generateNumberParts="0" catenateWords="0" catenateNumbers="0"
> catenateAl
: I'm trying to index some content that has things like 'java/J2EE' but with
: solr.WordDelimiterFilterFactory and parameters [generateWordParts="1"
: generateNumberParts="0" catenateWords="0" catenateNumbers="0"
: catenateAll="0" splitOnCaseChange="0"] this ends up tokenized as
: 'java','j','2',E
On 20-Nov-08, at 6:20 AM, Daniel Rosher wrote:
Hi,
I'm trying to index some content that has things like 'java/J2EE'
but with
solr.WordDelimiterFilterFactory and parameters [generateWordParts="1"
generateNumberParts="0" catenateWords="0" catenateNumbers="0"
catenateAll="0" splitOnCaseChange
29 matches
Mail list logo