jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "fabrizio giustina (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (JCR-3375) Excerpts not available with xpath queries filtered by path in JR 2.4
Date Wed, 04 Jul 2012 13:28:35 GMT

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

fabrizio giustina updated JCR-3375:
-----------------------------------

    Affects Version/s: 2.4
    
> Excerpts not available with xpath queries filtered by path in JR 2.4
> --------------------------------------------------------------------
>
>                 Key: JCR-3375
>                 URL: https://issues.apache.org/jira/browse/JCR-3375
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>    Affects Versions: 2.4
>            Reporter: fabrizio giustina
>            Priority: Minor
>
> Moving from jackrabbit 2.2 to 2.4 some of the queries were I was retrieving an excerpt
stopped working (same list of results but no excerpts returned).
> After some debugging I found out that with jackrabbit 2.4 excerpts are only returned
when the xpath queries are not filtered by path, e.g. using:
> //*[( (@jcr:primaryType='my:nodetype')  and  ( jcr:contains(., 'keyword') )  )]  order
by  @jcr:score descending
> I can successfully extract excerpts, while using:
> //something//*[( (@jcr:primaryType='my:nodetype')  and  ( jcr:contains(., 'keyword')
)  )]  order by  @jcr:score descending
> or
> /jcr:root//*[( (@jcr:primaryType='my:nodetype')  and  ( jcr:contains(., 'keyword') )
 )]  order by  @jcr:score descending
> (or anything different from //*)
> ... doesn't give any excerpt in jackrabbit 2.4, while it works with 2.2 (same identical
configuration, tested by switching several time between the two versions).
> Is this intended? I cound't find any note about similar limits or related changes in
JR 2.4.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message