Am 29.01.2013 00:24, schrieb Trejkaz:
> On Tue, Jan 29, 2013 at 3:42 AM, Andrew Gilmartin
> 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.
On Tue, Jan 29, 2013 at 3:42 AM, Andrew Gilmartin
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
Uwe Schindler wrote:
there is no need to extend Lucene's QueryParser. Lucene by
itself does not need a Query Parser at all and it does not
use it, it is just a convenience class. If you have worked
with Antlr to generate a grammar, just use it and build
the final org.apache.lucene.search.Quer
code.
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
> From: Carsten Schnober [mailto:schno...@ids-mannheim.de]
> Sent: Monday, January 28, 2013 4:44 PM
> To: java-user
> Subject: Custom
Hi,
for our project, we have to implement a custom query language that does
have much in common with the built-in Lucene query language. We have a
formal grammar for that language, formalized with Antlr.
I am not sure about the best way to build/generate a Lucene-based
QueryParser object that is p
