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 <[email protected]> wrote: > On Thu, Feb 20, 2014 at 1:43 PM, Jamie Johnson <[email protected]> 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: [email protected] > For additional commands, e-mail: [email protected] > >
