Hi Jack,
Thanks for the expalnation
--
View this message in context:
http://lucene.472066.n3.nabble.com/struggling-with-solr-WordDelimiterFilterFactory-tp4085021p4085661.html
Sent from the Solr - User mailing list archive at Nabble.com.
8 AM
To: solr-user@lucene.apache.org
Subject: Re: struggling with solr.WordDelimiterFilterFactory
Hi Jack,
As mentioned earliear a part of the issue was resolved by the two fixes I
mentioned above and for the query u mentioned I am getting the same result
as yours.
What is not working though is
Hi Jack,
As mentioned earliear a part of the issue was resolved by the two fixes I
mentioned above and for the query u mentioned I am getting the same result
as yours.
What is not working though is the query *q=content:"speedPost"* with the
text enclosed in inverted commas
--
View this message
Returns all five docs, as expected.
Note: the default for q.op is "OR".
So, please try the same experiment yourself, and then tell us how your
config/schema is different than this test case.
-- Jack Krupansky
-Original Message-
From: vicky desai
Sent: Tuesday, August 20, 20
Hi Erik,
I was going to come to that. Now if I have the word *speedpost* in the index
and if I dont use catenation at the query end then query for the word
speedPost wont fetch me the results. It would then might make sense to
remove the entire WDFF from query and search for a few possible combina
OK, here's where you can drive yourself mad with the subtle
variations between how WordDelimiterFilterFactory splits and
recombines the tokens. Take a look at the stock distro, you'll
see that the index time and query time settings for WEFF
are slightly different.
The idea is that if you do things
Hi All,
There were two fixes for the issue I was facing
1. By changing the version in schema form* 1.1* to *1.5*
OR
2. keeping the version to 1.1 and adding *autoGeneratePhraseQueries*="false"
to the field type
However the issue is not completely resolved yet
on searching for content:speedPost th
Hi Aloke,
After taking the schema.xml and solrconfig.xml with the changes u mentioned
it worked fine. However simply making this changes in schema.xml doesnt
work. So seems like there is an issue in some configuration in
solrconfig.xml. I will figure that out and post it here.
Anyways thanks a lo
Location of the schema.xml:
http://svn.apache.org/repos/asf/lucene/dev/tags/lucene_solr_4_2_1/solr/example/solr/collection1/conf/schema.xml
On Mon, Aug 19, 2013 at 6:52 PM, Aloke Ghoshal wrote:
> Here you go, it is the default 4.2.1 schema.xml (
> http://svn.apache.org/repos/asf/lucene/dev/tags
Here you go, it is the default 4.2.1 schema.xml (
http://svn.apache.org/repos/asf/lucene/dev/tags/lucene_solr_4_2_1/solr/example/solr/solr.xml),
with the following additions:
Test with the field *ContTest*.
Regards,
Aloke
On Mon,
Hi Aloke,
I have multiple fields in my schema which are of type text. i tried the
same case on all the fields. Not working for me on any of them. If possible
for u can u please post your dummy solrconfig.xml and schema.xml. I can
replace them and check
--
View this message in context:
http:/
Hi Vicky,
Please check you if you have a second "multiValued" field by the name
"content" defined in your schema.xml. It is typically part of the default
schema definition & is different from the one you had initially posted had
"Content" with a capital C.
Here's the debugQuery on my system (wit
Hi,
Another observation while testing
Docs having the value for content field as below
1. content:speedPost
2. content:sPeedpost
3. content:speEdpost
4. content:speedposT
matches the query q=content:speedPost. So basically if in the entire word
there is one 1 letter that is camel cased then it m
Hi Erik,
These are the request handlers defined in solrconfig.xml
--
View this message in context:
http://lucene.472066.n3.nabble.com/struggling-with-solr-WordDelimiterFilterFactory-tp4085021p4085417.html
Sent from the Solr - User mailing list arc
Well, the case of your parsedQuery field _name_ (i.e. content) does not
match
the case of your field definition, (i.e. Content). This may just be an
artifact
however.
That said, the MultiPhraseQuery is probably coming from your request
handler definition. Can we see that too?
Erick
On Mon, Aug
Hi,
I have created a new index. So reindexing shouldnt be the issue.
Analysis page shows me correct result and match should be found as per the
analysis page.But no output on actual query
The Output of debug query is as follows
content:speedPost
content:speedPost
MultiPhraseQuery(content:"(speedp
Vicky:
Both examples work fine for me. Can you show us the results of adding
&debug=query?
It does NOT work if I search content:speedPost rather than
Content:speedPost though,
are you sure the casing of your field name case matches exactly?
Also, be sure to re-index your data. Use the admin/analy
Hi,
That's correct the Analyzers will get applied to both Index & Query time.
In fact I do get results back for speedPost with this field definition.
Regards,
Aloke
On Fri, Aug 16, 2013 at 5:21 PM, vicky desai wrote:
> Hi,
>
> Another Example I found is q=Content:wi-fi doesn't match for docume
the generated parse
query looks like.
-- Jack Krupansky
-Original Message-
From: vicky desai
Sent: Friday, August 16, 2013 7:51 AM
To: solr-user@lucene.apache.org
Subject: Re: struggling with solr.WordDelimiterFilterFactory
Hi,
Another Example I found is q=Content:wi-fi doesn't
Hi,
Another Example I found is q=Content:wi-fi doesn't match for documents with
word wifi. I think it is not catenating the query keywords correctly
--
View this message in context:
http://lucene.472066.n3.nabble.com/struggling-with-solr-WordDelimiterFilterFactory-tp4085021p4085030.html
Sent f
Hi Aloke,
I am using the same analyzer for indexing as well as quering so
LowerCaseFilterFactory should work for both, right?
--
View this message in context:
http://lucene.472066.n3.nabble.com/struggling-with-solr-WordDelimiterFilterFactory-tp4085021p4085025.html
Sent from the Solr - User mai
Hi,
Based on your WhitespaceTokenizerFactory & due to the
LowerCaseFilterFactory the words actually indexed are:
speed, post, speedpost
You should get results for: q:Content:speedpost
So either remove the LowerCaseFilterFactory or add the
LowerCaseFilterFactory to as a query time Analyzer as wel
Hi All,
I have a query regarding the use of wordDelimiterFilterFactory. My schema
definition for the text field is as follows
hello,
>>
Or does your field in schema.xml have anything like
autoGeneratePhraseQueries="true" in it?
<<
there is no reference to this in our production schema.
this is extremely confusing.
i am not completely clear on the issue?
reviewing our previous messages - it looks like the data is bein
Hmmm, Try looking at either anything you've done in solrconfig.xml
where to the request handler (probably called "search") with
default="true" set.
Or does your field in schema.xml have anything like
autoGeneratePhraseQueries="true" in it?
Best
Erick
On Thu, Feb 9, 2012 at 12:02 PM, geeky2 wrot
>>
OK, first question is why are you searching on two different values?
Is that intentional?
<<
yes - our users have to be able to locate a part or model number (that may
or may not have periods in that number) even if they do NOT enter the number
with the embedded periods.
example:
actual
OK, first question is why are you searching on two different values?
Is that intentional? If I'm reading your problem right, you should
be able to get/not get any response just by toggling whether the
period is in the search URL, right?
But assuming that's not the problem, there's something you're
hello,
thanks for sticking with me on this ...very frustrating
ok - i did perform the query with the debug parms using two scenarios:
1) a successful search (where i insert the period / dot) in to the itemNo
field and the search returns a document.
itemNo:BP2.1UAA
http://hfsthssolr1.intra.sea
Hmmm, that all looks correct, from the output you pasted I'd expect
you to be finding the doc.
So next thing: add &debugQuery=on to your query and look at
the debug information after the list of documents, particularly
the "parsedQuery" bit. Are you searching against the fields you
think you are?
hello,
thank you for the reply.
yes - i did re-index after the changes to the schema.
also - thank you for the direction on using the analyzer - but i am not sure
if i am interpreting the feedback from the analyzer correctly.
here is what i did:
in the Field value (Index) box - i placed this:
Hmmm, seems OK. Did you re-index after any
schema changes?
You'll learn to love admin/analysis for questions like this,
that page should show you what the actual tokenization
results are, make sure to click the "verbose" check boxes.
Best
Erick
On Tue, Feb 7, 2012 at 10:52 PM, geeky2 wrote:
> h
hello all,
i am struggling with getting solr.WordDelimiterFilterFactory to behave as is
indicated in the solr book (Smiley) on page 54.
the example in the books reads like this:
>>
Here is an example exercising all options:
WiFi-802.11b to Wi, Fi, WiFi, 802, 11, 80211, b, WiFi80211b
<<
essentia
32 matches
Mail list logo
