> The QP should work like that: > (1) It parses the query, creating fragments > (2) It does some out-of-the-box handling of those fragments > > People should be able to override that handling of fragments. But people > should not touch (1).
In fact QP should work like that: (1) Tokenizer parses the query as if it was a string of text. Care must be taken to preserve query language operators, as this stage essentially replaces current QP's lexer stage. (2) QP's syntax parser kicks in, identifies operators (those that Tokenizer didn't treat as a part of word tokens) and does overridable out-of-the-box handling for them and tokens around them. The point is - it's hard to do correctly. That's why Lucene resorts to upside-down approach. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
