[ 
https://issues.apache.org/jira/browse/SOLR-10657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yonik Seeley updated SOLR-10657:
--------------------------------
    Description: 
A contrived example... facet by user, and then have that users reviews as a 
sub-facet.  For each bucket, the join.to (user) field will have a single exact 
value and the join query can be optimized to a field query.

[code}
myfacet : {
  type: terms,
  field : user,
  facet : {
    genres : {
      type: terms, field:genre
      domain : { join:{from: user, to: review_user} },
   }
}
{code}

Related: another thing I've thought about in the past is ways to use the 
current bucket "value" (or a parents bucket value) in queries for example.  A 
late-binding context sensitive term query (or query parser) is one potential 
way to implement some of this.

  was:
A contrived example... facet by user, and then have that users reviews as a 
sub-facet.  For each bucket, the join.to (user) field will have a single exact 
value and the join query can be optimized to a field query.

{
  type: terms,
  field : user,
  facet : {
    genres : {
      type: terms, field:genre
      domain : { join:{from: user, to: review_user} },
   }
}


> optimize join domain switch when join field has already been narrowed
> ---------------------------------------------------------------------
>
>                 Key: SOLR-10657
>                 URL: https://issues.apache.org/jira/browse/SOLR-10657
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: Facet Module
>            Reporter: Yonik Seeley
>
> A contrived example... facet by user, and then have that users reviews as a 
> sub-facet.  For each bucket, the join.to (user) field will have a single 
> exact value and the join query can be optimized to a field query.
> [code}
> myfacet : {
>   type: terms,
>   field : user,
>   facet : {
>     genres : {
>       type: terms, field:genre
>       domain : { join:{from: user, to: review_user} },
>    }
> }
> {code}
> Related: another thing I've thought about in the past is ways to use the 
> current bucket "value" (or a parents bucket value) in queries for example.  A 
> late-binding context sensitive term query (or query parser) is one potential 
> way to implement some of this.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

Reply via email to