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 "Chetan Mehrotra (JIRA)" <ji...@apache.org> on 2017/12/06 09:53:00 UTC

[jira] [Commented] (OAK-6597) rep:excerpt not working for content indexed by aggregation in lucene

    [ https://issues.apache.org/jira/browse/OAK-6597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16279939#comment-16279939 ] 

Chetan Mehrotra commented on OAK-6597:
--------------------------------------

Not sure on the approach to take here so moving this to 1.10

> rep:excerpt not working for content indexed by aggregation in lucene
> --------------------------------------------------------------------
>
>                 Key: OAK-6597
>                 URL: https://issues.apache.org/jira/browse/OAK-6597
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: lucene
>    Affects Versions: 1.6.1, 1.7.6
>            Reporter: Dirk Rudolph
>            Assignee: Chetan Mehrotra
>              Labels: excerpt
>             Fix For: 1.10
>
>         Attachments: excerpt-with-aggregation-test.patch
>
>
> I mentioned that properties that got indexed due to an aggregation are not considered for excerpts (highlighting) as they are not indexed as stored fields.
> See the attached patch that implements a test for excerpts in {{LuceneIndexAggregationTest2}}.
> It creates the following structure:
> {code}
> /content/foo [test:Page]
>  + bar (String)
>  - jcr:content [test:PageContent]
>   + bar (String)
> {code}
> where both strings (the _bar_ property at _foo_ and the _bar_ property at _jcr:content_) contain different text. 
> Afterwards it queries for 2 terms ("tinc*" and "aliq*") that either exist in _/content/foo/bar_ or _/content/foo/jcr:content/bar_ but not in both. For the former one the excerpt is properly provided for the later one it isn't.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)