[
https://issues.apache.org/jira/browse/OAK-3866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tommaso Teofili updated OAK-3866:
---------------------------------
Description:
Executing a query like
{noformat}
/jcr:root/content/foo//*[(@sling:resourceType = 'x' or @sling:resourceType =
'y') and jcr:contains(., 'bar*~')] order by jcr:content/@jcr:primaryType
descending
{noformat}
would assume sorting on the _jcr:primaryType_ property of resulting nodes'
_jcr:content_ children.
That is currently not supported in Solr, while it is in Lucene as the latter
supports index time aggregation.
We should inspect if it's possible to extend support for Solr too, most
probably via index time aggregation.
The query should not fail but at least log a warning about that limitation for
the time being.
was:
Executing a query like
{noformat}
/jcr:root/content/foo//*[(@sling:resourceType = 'x' or @sling:resourceType =
'y') and jcr:contains(., 'bar*~')] order by jcr:content/@jcr:primaryType
descending
{noformat}
would assume sorting on the _jcr:primaryType_ property of resulting nodes'
children.
That is currently not supported in Solr, while it is in Lucene as the latter
supports index time aggregation.
We should inspect if it's possible to extend support for Solr too, most
probably via index time aggregation.
The query should not fail but at least log a warning about that limitation for
the time being.
> Sorting on relative properties doesn't work in Solr
> ---------------------------------------------------
>
> Key: OAK-3866
> URL: https://issues.apache.org/jira/browse/OAK-3866
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: solr
> Affects Versions: 1.3.13
> Reporter: Tommaso Teofili
> Assignee: Tommaso Teofili
> Fix For: 1.4
>
>
> Executing a query like
> {noformat}
> /jcr:root/content/foo//*[(@sling:resourceType = 'x' or @sling:resourceType =
> 'y') and jcr:contains(., 'bar*~')] order by jcr:content/@jcr:primaryType
> descending
> {noformat}
> would assume sorting on the _jcr:primaryType_ property of resulting nodes'
> _jcr:content_ children.
> That is currently not supported in Solr, while it is in Lucene as the latter
> supports index time aggregation.
> We should inspect if it's possible to extend support for Solr too, most
> probably via index time aggregation.
> The query should not fail but at least log a warning about that limitation
> for the time being.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
