The other option would be a custom QParserPlugin.
-Yonik
On Tue, Mar 18, 2008 at 12:18 PM, Ben Sanchez <[EMAIL PROTECTED]> wrote:
> Shalin, Thanks a lot. I'll do that.
>
> On Tue, Mar 18, 2008 at 11:13 AM, Shalin Shekhar Mangar <
>
>
> [EMAIL PROTECTED]> wrote:
>
> > Hi Ben,
> >
> > If I had
Shalin, Thanks a lot. I'll do that.
On Tue, Mar 18, 2008 at 11:13 AM, Shalin Shekhar Mangar <
[EMAIL PROTECTED]> wrote:
> Hi Ben,
>
> If I had to do this, I would start by adding a custom
> javax.servlet.Filter into Solr. It should work fine since all you're
> doing is replacing characters in the
Hi Ben,
If I had to do this, I would start by adding a custom
javax.servlet.Filter into Solr. It should work fine since all you're
doing is replacing characters in the q parameter for requests coming
into /select handler. It's a bit hackish but that's exactly what
you're trying to do :)
Don't kno
Hi Shalin, thanks a lot for answering that fast.
Use Case:
I'm migrating from a proprietary index server (XYZ) to Solr. All my
applications and my customer's applications relay on the query specification
of XYZ. It would be hard to modify all those apps to use the Solr Query
Syntax (although, it
Shalin, thanks a lot for answering that fast.
Use Case:
I'm migrating from a proprietary index server (XYZ) to Solr. All my
applications and my customer's applications relay on the query specification
of XYZ. It would be hard to modify all those apps to use the Solr Query
Syntax (although, it wou
Hi Ben,
It would be nice if you can tell us your use-case so that we can be
more helpful.
Why does the normal query syntax not work well for you? What are you
trying to accomplish? Maybe there is an easier way.
On Tue, Mar 18, 2008 at 8:17 PM, Ben Sanchez <[EMAIL PROTECTED]> wrote:
> Hi solr use