Now we have a SynonymGraphFilter but also need other filters to be graph-aware. I was already thinking about a ShingleGraphFilter. But if a ShingleGraphFilter outputs a graph and is located before SynonymGraphFilter where is the advantage? The SynonymGraphFilter cannot consume arbitrary graphs.
Do we need as first step a util method for reading an inputTokenStream and give back a graph? It can be called by any xxxGraphFilter as first step. Is this a stupid idea? How about the resulting outputTokenStream, does it make sense to have a util method producing an outputTokenStream from a graph? It would generalize the input/output handling of any xxxGraphFilter and only leave the filter work to the GraphFilter. What do you think? Regards Bernd --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org For additional commands, e-mail: java-user-h...@lucene.apache.org
