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 wrote:
> On Thu, Feb 20, 2014 at 1:43 PM, Jamie Johnson wrote:
On Thu, Feb 20, 2014 at 1:43 PM, Jamie Johnson 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 c
: 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?
"limit" in what way? do you want to throw a parse error if they give you
"field_you_do_not
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?
