lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jamie Johnson <jej2...@gmail.com>
Subject Re: Limiting the fields a user can query on
Date Fri, 21 Feb 2014 00:07:43 GMT
I would be fine with throwing a parse exception or excluding the particular
clause.  I will look at the StandardQueryNodeProcessorPipeline as well as
Hoss' suggestion.  Thank you very much!


On Thu, Feb 20, 2014 at 4:20 AM, Trejkaz <trejkaz@trypticon.org> wrote:

> On Thu, Feb 20, 2014 at 1:43 PM, Jamie Johnson <jej2003@gmail.com> wrote:
> > Is there a way to limit the fields a user can query by when using the
> > standard query parser or a way to get all fields/terms that make up a
> query
> > without writing custom code for each query subclass?
>
> If you mean StandardQueryParser, you could subclass
> StandardQueryNodeProcessorPipeline and add one more processor into the
> pipeline which looks for instances of FieldableNode. That should cover
> any kind of query node which can have a field on it.
>
> TX
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
> For additional commands, e-mail: java-user-help@lucene.apache.org
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message