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

Vijay Sekhri commented on SOLR-5743:
------------------------------------

 I saw the blog few times before already. Thank you for writing it Mikhail .  I 
am not sure it cover the searching uses cases. Searching and filtering are two 
different use cases. 
 For example say you have these in your solrconfig as one of the requesthandler 
. As you can see it would search in a lot fields and boost based on which 
fields matches. Plus if you declare  pf field for proximity and mm field for 
must match , relevancy kicks in . All of this I am not sure how can be still 
used just by mere filter. Searching return relevant docs with accounting for 
boosts. Filter remove docs that matches criteria. 
 
        <code>
         <str name="qf">
                 primaryLnames^5.0 partnumber^11.0 itemnumber^11.0 
description^0.5  fullmfpartno^5.0 mfpartno^5.0 xref^10.0 
storeOriginSearchable^3.0 nameSearchable^10.0 brandSearchable^5.0  
searchPhrase^1.0 searchableAttributesSearchable^1.0
            </str>
            <str name="pf">
                                primaryLnames^0.5 nameSearchable^1.0 
description^0.1 storeOriginSearchable^0.3 brandSearchable^0.5  xref^1.1 
searchableAttributesSearchable^0.1
                         </str>
            <str name="fl">*</str>
            <str name="mm">
                2<-1 5<-2 6<-50%
            </str>
                        
                </code>
                
Let me know if there is a way to still search, not filter and still use 
ToParentBlockJoinQuery . Real world scenarios would return parent docs based on 
some order of relevancy and boost criteria. 

> Faceting with BlockJoin support
> -------------------------------
>
>                 Key: SOLR-5743
>                 URL: https://issues.apache.org/jira/browse/SOLR-5743
>             Project: Solr
>          Issue Type: New Feature
>          Components: faceting
>            Reporter: abipc
>            Assignee: Mikhail Khludnev
>              Labels: features
>             Fix For: 5.5
>
>         Attachments: SOLR-5743.patch, SOLR-5743.patch, SOLR-5743.patch, 
> SOLR-5743.patch, SOLR-5743.patch, SOLR-5743.patch, SOLR-5743.patch, 
> SOLR-5743.patch, SOLR-5743.patch, SOLR-5743.patch, SOLR-5743.patch, 
> SOLR-5743.patch, SOLR-5743.patch, SOLR-5743.patch, SOLR-5743.patch
>
>
> For a sample inventory(note - nested documents) like this -   
>  <doc>
> <field name="id">10</field>
> <field name="type_s">parent</field>
> <field name="BRAND_s">Nike</field>
> <doc>
> <field name="id">11</field>
> <field name="COLOR_s">Red</field>
> <field name="SIZE_s">XL</field>
> </doc>
> <doc>
> <field name="id">12</field>
> <field name="COLOR_s">Blue</field>
> <field name="SIZE_s">XL</field>
> </doc>
> </doc>
> Faceting results must contain - 
> Red(1)
> XL(1) 
> Blue(1) 
> for a "q=*" query. 
> PS : The inventory example has been taken from this blog - 
> http://blog.griddynamics.com/2013/09/solr-block-join-support.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to