On Tue, Jan 29, 2013 at 3:42 AM, Andrew Gilmartin <and...@andrewgilmartin.com> wrote: > When I first started using Lucene, Lucene's Query classes where not suitable > for use with the Visitor pattern and so I created my own query class > equivalants and other more specialized ones. Lucene's classes might have > changed since then (I do not know)
On that subject, the infrastructure behind StandardQueryParser is along those lines. Query itself is still not very flexible, but QueryNode is much more convenient and there are processors for walking the tree to do transformations. We ended up using ANTLR to do the syntax parsing for our stuff and then using most of the standard transformations as-is, decorated in some cases (either to customise or to work around bugs.) Of course we had to add our own for all the new features, but we got a fair bit of reuse out of the new framework. TX --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org For additional commands, e-mail: java-user-h...@lucene.apache.org
