e 63, D-28213 Bremen
>> http://www.thetaphi.de
>> eMail: u...@thetaphi.de
>>
>> ------------------------
>>
>> *From:* Adriano Crestani [mailto:adrianocrest...@gmail.com]
>> *Sent:* Monday, August 03, 2009 10
adrianocrest...@gmail.com]
*Sent:* Monday, August 03, 2009 10:00 PM
*To:* java-dev@lucene.apache.org
*Subject:* Re: basic questions on the new QueryParser
I see the "original" package, and the useful OriginalQueryParserHelper
within there, that are meant to ease the transition off of the old
OK I will open an issue to further iterate on this...
Mike
On Tue, Aug 4, 2009 at 1:34 AM, Adriano
Crestani wrote:
> The "original" and "helper" aren't that descriptive to users.
>
> It's named "helper" because it extends QueryParserHelper, that's the only
> reason. I think it's ok to rename "ori
The "original" and "helper" aren't that descriptive to users.
It's named "helper" because it extends QueryParserHelper, that's the only
reason. I think it's ok to rename "original" to something else. . I also
share Mike's opinion, I prefer "default" over "original".
Mike - isn't "fast forwarding
Mike - isn't "fast forwarding 3 years" means that the current QP will be
removed, together w/ the OriginalQPHelper and we'll have just one QP? And
I'd think we'll want to call it Default or something, so users can
distinguish between it (which parses the Lucene query syntax) and another
custom pars
Michael McCandless wrote:
OK thanks for the clarification... that makes sense. So the builder
should really be a "rote" translation of a query node into the
corresponding Query. All "interesting" work should instead be done by
the processors (or maybe the parser).
Hi Mike,
Only the Proce
On Mon, Aug 3, 2009 at 3:59 PM, Adriano
Crestani wrote:
> Yes, it's the Lucene's "default" query parser implemented using the new QP
> framework.
OK.
> Now, about moving it to oal.queryParser, I think it's a subjective decision.
> I like it inside oal.queryParser.original, because
> we can easil
If I read it correctly, the parsing of the query string is decoupled from
this. So somebody could also create another query syntax and reuse all
processors and builders?
Yes, as far as the processors know how to process the node your text parser
creates. The QP framework was really designed to hav
t: Re: basic questions on the new QueryParser
I see the "original" package, and the useful OriginalQueryParserHelper
within there, that are meant to ease the transition off of the old
QueryParser to the new one.
First question: is the original package also intended to be Lucene's
&
I see the "original" package, and the useful OriginalQueryParserHelper
within there, that are meant to ease the transition off of the old
QueryParser to the new one.
First question: is the original package also intended to be Lucene's
"default" QueryParser, going forward? Ie, most users will simp
10 matches
Mail list logo
