Re: FlattenGraphFilter Eliminates Tokens - Can't match "Can't"

2019-12-05 Thread Paras Lehana
Hi Michael, I think you only want to use FlattenGraphFilter *once* in the indexing > analysis chain I had been doing this for a long time before I finally shifted to use FGF after every GraphFilterFactory. Although I don't know much about it on the code level, are you sure that all the

Re: FlattenGraphFilter Eliminates Tokens - Can't match "Can't"

2019-12-05 Thread Eric Buss
Thanks for the reply, I wouldn't be surprised if the issue you linked is related, I also found another similar issue: https://issues.apache.org/jira/browse/LUCENE-8723 You are absolutely right that the FlattenGraphFilter should only be used once, but as you noted the issue I am experiencing

Re: FlattenGraphFilter Eliminates Tokens - Can't match "Can't"

2019-12-05 Thread Michael Gibney
I wonder if this might be similar/related to the underlying problem that is intended to be addressed by https://issues.apache.org/jira/browse/LUCENE-8985? btw, I think you only want to use FlattenGraphFilter *once* in the indexing analysis chain, towards the end (after all components that emit

FlattenGraphFilter Eliminates Tokens - Can't match "Can't"

2019-11-25 Thread Eric Buss
Hi all, I have been trying to solve an issue where FlattenGraphFilter (FGF) removes tokens produced by WordDelimiterGraphFilter (WDGF) - consequently searches that contain the contraction "can't" do not match. This is on Solr version 7.7.1. The field in question is defined as follows: And