[
https://issues.apache.org/jira/browse/SOLR-8998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15360550#comment-15360550
]
Mikhail Khludnev commented on SOLR-8998:
----------------------------------------
following this way:
bq. field facet (a sub-facet) on the parents (including any rollups)
from [the
comment|http://blog-archive.griddynamics.com/2016/03/block-join-faceting-implementation.html?showComment=1464018514676],
that's how it may work
{code}
curl http://localhost:8983/solr/collection1/query -d 'q={!parent
which=type_s:parent}type_s:child&rows=0&
json.facet={
filter_by_children: {
type:query,
q:"type_s:child",
domain: { blockChildren : "type_s:parent" },
facet:{
colors:{
type : terms,
field : COLOR_s,
facet: {
productsCount: "unique(_root_)"
}
},
sizes:{
type : terms,
field : SIZE_s,
facet: {
productsCount: "unique(_root_)"
}}}}}
{code}
[[email protected]],
Here's my obvious proposal for improvement, let's introduce
{{rollup(type_s:parent)}} as a specialized alternative to {{unique(_root_)}}?
My expectation, that checking next bit in parents' bitset is faster than
getting {{_root_}} values.
Does it deserve a separate issue or it can be counted step toward this one?
> JSON Facet API child roll-ups
> -----------------------------
>
> Key: SOLR-8998
> URL: https://issues.apache.org/jira/browse/SOLR-8998
> Project: Solr
> Issue Type: New Feature
> Components: Facet Module
> Reporter: Yonik Seeley
>
> The JSON Facet API currently has the ability to map between parents and
> children ( see http://yonik.com/solr-nested-objects/ )
> This issue is about adding a true rollup ability where parents would take on
> derived values from their children. The most important part (and the most
> difficult part) will be the external API.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
