Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@lucene.apache.org
Date: Wed, 17 Oct 2012 19:04:03 +0000 (UTC)
From: "Hoss Man (JIRA)" <jira@apache.org>
To: dev@lucene.apache.org
Message-ID: <2145156912.59440.1350500643681.JavaMail.jiratomcat@arcas>
In-Reply-To: <1888110805.58160.1350488404494.JavaMail.jiratomcat@arcas>
Subject: [jira] [Commented] (SOLR-3960) Searching: PostFilter plugins
 ignored by solr cloud
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/SOLR-3960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13478249#comment-13478249 ] 

Hoss Man commented on SOLR-3960:
--------------------------------

Nathan: just to clarify, you said...

bq. When specifying the cloud options (-DzkRun -DnumShards=n) in solr startup parameters, solr search does not consider any PostFilters.

but then you go on to say...

bq. I debugged and figured out that org.apache.solr.search.Grouping.execute() method is called by the non cloud instance. This considers pf.PostFilter which is the collection of all PostFilters whereas org.apache.solr.search.grouping.CommandHandler.execute() 

which makes it sound like this problem is specific to using the _grouping_ features combined with distributed search (ie: solr cloud) and not a general problem with all distributed search.

can you please confirm/clarify that? when you do a regular search, w/o using grouping, then do you see your postfilter used in solrcloud?

It would also help if you could provide a simple example of the problem you are seeing that didn't require using your custom component QParserPlugin -- so we can rule out that there isn't anything odd in how your custom code.  a JUnit test would be ideal, but even providing an example URL using the example configs that are included with solr showing the problem would be helpful. (eg: the frange qparser can be used as a PostFilter)


> Searching: PostFilter plugins ignored by solr cloud
> ---------------------------------------------------
>
>                 Key: SOLR-3960
>                 URL: https://issues.apache.org/jira/browse/SOLR-3960
>             Project: Solr
>          Issue Type: Bug
>          Components: search, SolrCloud
>    Affects Versions: 4.0-BETA
>         Environment: Linux / jre 1.6
>            Reporter: Nathan Visagan
>              Labels: patch
>
> When specifying the cloud options (-DzkRun -DnumShards=n) in solr startup parameters, solr search does not consider any PostFilters.
> For example, I have implemented a PostFilter and wrapped that in my QParserPlugin sub class. Then in the solr query I am using fq to apply post filtering by specifying fq={!pf1} where pf1 is the name of my QParserPlugin. This all works well in solr and not in solr cloud. 
> I debugged and figured out that org.apache.solr.search.Grouping.execute() method is called by the non cloud instance. This considers pf.PostFilter which is the collection of all PostFilters whereas org.apache.solr.search.grouping.CommandHandler.execute() which is called by the solr cloud instance ignores the pf.PostFilter.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org