[
https://issues.apache.org/jira/browse/SOLR-8998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16463988#comment-16463988
]
Cassandra Targett commented on SOLR-8998:
-----------------------------------------
[~mkhludnev], sorry for the delay taking a look at this. Just to make sure I
understand what you asked me to look at...Some documentation was done with the
code changes last week, but then there are some additional doc changes that are
proposed in the {{SOLR-8998-doc.patch}}, is that correct?
I haven't reviewed in much depth yet, but one thing that jumped out at me right
away is if you look at the BlockJoin Faceting page as it's built
(https://builds.apache.org/view/L/view/Lucene/job/Solr-reference-guide-master/javadoc/blockjoin-faceting.html)
there are two warnings near the top of the page. The one that was added with
this issue says the functionality is deprecated, but the next one that's been
there for a while says it's experimental. Those statements on the status
conflict, I think - "experimental" would indicate to me that future development
is likely, but "deprecated" says no more development should be expected. I
think we could merge those statements with something like:
{noformat}
This functionality is considered deprecated. Users are encouraged to use
uniqueBlock(_root_) aggregation under terms facet in JSON Facet API.
If this component is used, it must be explicitly enabled for a request handler
in solrconfig.xml, in the same way as any other search component.
{noformat}
Does that seem reasonable and an accurate reflection of the status of
{{BlockJoinFacetComponent}}?
> 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
> Assignee: Mikhail Khludnev
> Priority: Major
> Fix For: 7.4, master (8.0)
>
> Attachments: SOLR-8998-api-doc.patch, SOLR-8998-doc.patch,
> SOLR-8998.patch, SOLR-8998.patch, SOLR-8998.patch, SOLR_8998.patch,
> SOLR_8998.patch, SOLR_8998.patch
>
>
> 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.
> [~mkhludnev] says
> {quote}
> The bottom line is to introduce {{uniqueBlock(\_root_)}} aggregation, which
> is supposed to be faster than {{unique(\_root_)}} and purposed for blocked
> index only. For now it it supports singlevalue string fields, docValues
> usually make sense.
> {quote}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
