[
https://issues.apache.org/jira/browse/OAK-2538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14383608#comment-14383608
]
Tommaso Teofili commented on OAK-2538:
--------------------------------------
Current options are using very same stuff done by [~chetanm] for _oak-lucene_
(see {{Aggregate}} class) or doing something different by means of _block join_
capability in Lucene / Solr, see
https://cwiki.apache.org/confluence/display/solr/Uploading+Data+with+Index+Handlers#UploadingDatawithIndexHandlers-NestedChildDocuments
and
https://cwiki.apache.org/confluence/display/solr/Other+Parsers#OtherParsers-BlockJoinQueryParsers
.
> Support index time aggregation in Solr index
> --------------------------------------------
>
> Key: OAK-2538
> URL: https://issues.apache.org/jira/browse/OAK-2538
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: oak-solr
> Reporter: Tommaso Teofili
> Assignee: Tommaso Teofili
> Fix For: 1.2
>
>
> Solr index is only able to do query time aggregation while that "would not
> perform well for multi term searches as each term involves a separate call
> and with intersection cursor being used the operation might result in reading
> up all match terms even when user accesses only first page", therefore it'd
> be good to implement index time aggregation like in Lucene index. (/cc
> [~chetanm])
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
