You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Davide Giannella (JIRA)" <ji...@apache.org> on 2019/04/15 09:20:11 UTC

[jira] [Closed] (OAK-8072) Aggregate jcr:content result nodes as their parent

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

Davide Giannella closed OAK-8072.
---------------------------------

bulk close 1.12.0

> Aggregate jcr:content result nodes as their parent 
> ---------------------------------------------------
>
>                 Key: OAK-8072
>                 URL: https://issues.apache.org/jira/browse/OAK-8072
>             Project: Jackrabbit Oak
>          Issue Type: Task
>          Components: solr
>            Reporter: Tommaso Teofili
>            Assignee: Tommaso Teofili
>            Priority: Major
>             Fix For: 1.12.0, 1.8.13, 1.10.3
>
>
> Until the time we'll be able to work on the index time aggregation for Solr, we should make it possible to aggregate search results of _/foo/bar/jcr:content_ nodes as their parents _/foo/bar_ as that's what nowadays often done in Lucene index configuration and therefore useful for feature parity.
> We can disabled this as soon as we switch oak-solr to depend on oak-search and therefore Solr index gains the index time aggregation feature consequently.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)