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

Dirk Rudolph edited comment on OAK-6597 at 12/19/17 9:51 AM:
-------------------------------------------------------------

There is still the risk, that duplications appear in the excerpt because there 
is a highlighting hit in :fulltext and one for example in full:bar. To prevent 
that, it probably makes sense to first do the highlighting on :fulltext fields 
when analyzeFulltext is enabled and only if that hasn't been success full we 
fallback to the logic of highlighting full: fields. wdyt?


was (Author: diru):
There is still the risk, that duplication appear in the excerpt because there 
is a highlighting hit in :fulltext and one for example in full:bar. To prevent 
that, it probably makes sense to first do the highlighting on :fulltext fields 
when analyzeFulltext is enabled and only if that hasn't been success full we 
fallback to the logic of highlighting full: fields. wdyt?

> 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, 1.8
>            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)

Reply via email to