[prev in list] [next in list] [prev in thread] [next in thread] 

List:       lucene-user
Subject:    Re: Limiting the fields a user can query on
From:       Jamie Johnson <jej2003 () gmail ! com>
Date:       2014-02-21 0:07:43
Message-ID: CAL3VrCfXPn2F4PRuZ_4Yi-2wZaG8jgVGae18xJjbpCZ41JTC6Q () mail ! gmail ! com
[Download RAW message or body]


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
>
>


[prev in list] [next in list] [prev in thread] [next in thread]