Yonik
Thanks for the tip.However, from what I can see, I still need to return
a TermQuery specific to each data type. Does anyone know how to convert
a string value to TermQuery for each data type?
Jamie
On 2012/07/11 3:42 PM, Yonik Seeley wrote:
On Wed, Jul 11, 2012 at 9:34 AM, Jamie wro
On Wed, Jul 11, 2012 at 9:34 AM, Jamie wrote:
> I am busying attempting to integrate Lucene 4.0 Alpha into my code base. I
> have a custom QueryParser that extends QueryParser and overrides
> newRangeQuery and newTermQuery
Random pointer: for most special case field handling, one would want
to ov
Hi Everyone
I am busying attempting to integrate Lucene 4.0 Alpha into my code base.
I have a custom QueryParser that extends QueryParser and overrides
newRangeQuery and newTermQuery to support typed fields.
I think I've figured out the newRangeQuery method translation (shown
further down belo
On 22-Nov-07, at 8:49 AM, Nicolas Lalevée wrote:
Le jeudi 22 novembre 2007, Matthijs Bierman a écrit :
Hi Nicolas,
Why can't you extend the QueryParser and override the methods you
want
to modify?
Because the query parser I would like to have is a very basic user
one, ala
google. The s
apache.org:8080/hudson/job/Lucene-Nightly/javadoc/org
> >/apache/lucene/queryParser/QueryParser.html#getFieldQuery(java.lang.String
> >, %20java.lang.String)
> >
> > So is there any proper way to create a custom query parser without
> > duplicating the code ?
> >
> >
reate a custom query parser without duplicating
the code ?
cheers,
Nicolas
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROT
/Lucene-Nightly/javadoc/org/apache/lucene/queryParser/QueryParser.html#getFieldQuery(java.lang.String,
%20java.lang.String)
So is there any proper way to create a custom query parser without duplicating
the code ?
cheers,
Nicolas
-
To
