Hey guys,

I have the following situation:

- I have a sentence, for example "This is my %%sentence%% I want to search for" 
and I would like to query for the term %%sentence%% (could be in any property)
- The default built-in full text oak lucene index uses the Standard Analyzer, 
which parses out the %%.
- I could use the WhitespaceAnalyzer, which would index the sentence as This, 
is, my , %%sentence%%, I, ...
- By using this analyzer but also putting it on nt:base, I would go against the 
docs which state I should not create a second index that also uses the same 
nodetype

So my question here is, how could I solve this? Is it possible to specify that 
this index should not be used for normal querying, and then doing a rep-native 
where I specify the functionName of that specific index so that I can query it 
anyway? Any other solutions would be helpful too

Thanks,
Roy

Reply via email to