Sorry, but it looks like the SolrEntityProcessor does a raw split on commas
of its "fq" parameter, with no provision for escaping.
You should be able to combine the fq into the query parameter as a nested
query which does not have the split issue.
-- Jack Krupansky
-----Original Message-----
From: Dirceu Vieira
Sent: Thursday, September 20, 2012 4:16 PM
To: solr-user@lucene.apache.org
Subject: Re: Problems with SolrEnitityProcessor + frange filterQuery
Hi guys,
Has anybody got any idea about that?
I'm really open for any suggestions....
Thanks!
Dirceu
On Thu, Sep 20, 2012 at 11:58 AM, Dirceu Vieira <dirceu...@gmail.com> wrote:
Hi,
I'm attempting to write a filter query for my SolrEntityProcessor using
{frange} over a function.
It works fine when I'm testing it on the admin, but once I move it into my
data-config.xml the query blows up because of the commas in the function.
The problem is that fq parameter can be a comma separated list, which
means that if I have commas within my query, it'll try to split it into
multiple filter queries.
Does anybody knows a way of escaping the comma or another way I can work
around that?
I've been using SolrEntityProcessor to import filtered data from a core to
another, here's the queries:
query="status:1 AND NOT priority:\-1"
fq="{!frange l=3000 u=5000}max(sum(suser_count), sum(user_count))"
I'm using Solr-4.0.0-BETA.
Best regards,
--
Dirceu Vieira Júnior
-------------------------------------------------------------------
+47 9753 2473
dirceuvjr.blogspot.com
twitter.com/dirceuvjr
--
Dirceu Vieira Júnior
-------------------------------------------------------------------
+47 9753 2473
dirceuvjr.blogspot.com
twitter.com/dirceuvjr
