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

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 1.6.1, 1.7.6, 1.8.0
• Component/s: lucene
• Labels: excerpt
• Epic Link: indexer resilience
• Assignee: Chetan Mehrotra
• Reporter: Dirk Rudolph
• Created: 29/Aug/17 20:58
• Updated: 23/Jun/21 18:58

Description

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:

/content/foo [test:Page]
 + bar (String)
 - jcr:content [test:PageContent]
  + bar (String)

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.

Issue Links

• is blocked by: OAK-7070 rep:excerpt selector broken as regression of OAK-6750
• is blocked by: OAK-6598 LuceneIndexAggregationTest2 doesn't get executed by mvn test
• links to: #76
• links to: GitHub Pull Request #76