Re: PatternReplaceFilterFactory problem

2019-01-29 Thread Chris Wareham
Thanks for the help - changing the field type of the destination for the copy fields to "text_en" solved the problem. I'd foolishly assumed that the analysis of the source fields was applied then the resulting tokens passed to the copy field, which doesn't really make sense now that I think

Re: PatternReplaceFilterFactory problem

2019-01-28 Thread Alexandre Rafalovitch
In Admin UI, there is an Analysis screen. You can enter your text and your query there and see what happens to it at every step of the processing pipeline. This should tell you whether the problem is in indexing, query, or somewhere else entirely (e.g. you are querying a different field as Scott

Re: PatternReplaceFilterFactory problem

2019-01-28 Thread Scott Stults
Hi Chris, You've included the field definition of type text_en, but in your queries you're searching the field "text", which is of type text_general. That may be the source of your problem, but if looking into that doesn't help send the definition of text_general as well. Hope that helps!

PatternReplaceFilterFactory problem

2019-01-28 Thread Chris Wareham
I'm trying to index some data which often includes domain names. I'd like to remove the .com TLD, so I have modified the text_en field type by adding a PatternReplaceFilterFactory filter. However, it doesn't appear to be working as a search for "text:(mydomain.com)" matches records but