sking?
>> >>
>> >> Maybe you simply need to read up on Lucene Query and its subclasses to
>> >> understand what that structure looks like.
>> >>
>> >> -- Jack Krupansky
>> >>
>> >> -Original Message- From: Davi
nd its subclasses to
> >> understand what that structure looks like.
> >>
> >> -- Jack Krupansky
> >>
> >> -Original Message- From: Davide Lorenzo Marino
> >> Sent: Thursday, October 04, 2012 11:36 AM
> >> To: solr-user@lucene.apac
tand what that structure looks like.
>>
>> -- Jack Krupansky
>>
>> -Original Message- From: Davide Lorenzo Marino
>> Sent: Thursday, October 04, 2012 11:36 AM
>> To: solr-user@lucene.apache.org
>> Subject: Re: Getting list of operators and terms for a quer
>
> Maybe you simply need to read up on Lucene Query and its subclasses to
> understand what that structure looks like.
>
> -- Jack Krupansky
>
> -Original Message- From: Davide Lorenzo Marino
> Sent: Thursday, October 04, 2012 11:36 AM
> To: solr-user@lucene.apa
-user@lucene.apache.org
Subject: Re: Getting list of operators and terms for a query
It's ok.. I did it and I took the query string.
The problem is convert the java.lang.string (query) in a list of term and
operators and doing it using the same parser used by Solr to execute the
queries.
2012/10/4 Mikhai
It's ok.. I did it and I took the query string.
The problem is convert the java.lang.string (query) in a list of term and
operators and doing it using the same parser used by Solr to execute the
queries.
2012/10/4 Mikhail Khludnev
> you've got ResponseBuilder as process() or prepare() argument,
you've got ResponseBuilder as process() or prepare() argument, check
"query" field, but your component should be registered after QueryComponent
in your requestHandler config.
On Thu, Oct 4, 2012 at 6:03 PM, Davide Lorenzo Marino <
davide.mar...@gmail.com> wrote:
> Hi All,
> i'm working in a new
