I am having a problem when searching for Phrases. Here is a bit about my environment:
using v4.7.2
The indexer is using "StandardAnalyzer".
IndexSet has nothing special other than excluding some node types.
Now, what is really concerning for me is that the phrase search doesn't even work on Luke. When I open the index I try to do the following simple search:
(bodyText: "input 910")
this returns nothing... I know for a fact this text string exists on the field.
From my code what I am doing is something like this:
does the text input 910 appear in that order or do you have the word input then some other text then 910 appearing? If so then phrase wont work as phrase is looking for input 910 however if you did or search it would match.
Examine - Phrase search not working...
Hello everyone,
I am having a problem when searching for Phrases. Here is a bit about my environment:
From my code what I am doing is something like this:
does the text input 910 appear in that order or do you have the word input then some other text then 910 appearing? If so then phrase wont work as phrase is looking for input 910 however if you did or search it would match.
Regards
Ismail
Covo,
I just did the following on an index using luke using standard analyser. Did search for lawn tennis. The words appear after each other
contents:lawn contents:tennis - get results around 10
then did phrase
contents:"lawn tennis" - get results only 2
Regards
Ismail
Ismail,
Thanks for your replies. Yes, the phrase appears exactly in that order ("input 910").
So if do:
bodyText:input bodyText:910 - I get around 20 results.
If I do:
bodyText:"input 910" - Nothing.
Do you know if there is anything special I need to do in the config files?
Thanks,
Ricardo,
Can you try it with another phrase without number in see if that works.
Regards
Ismail
Hello Ismail,
THanks for following in up. Upon more digging I noticed that the index is creating the phrase as follow "input 910".
I am not sure why the " " is getting in there, because the actual HTML doesn't have it.
I also see a lot of "\n" there.
I think this is what is creating a problem. Do you know if any work around that.
Again, thanks a lot for all your help,
-Covo
is working on a reply...