[
https://issues.apache.org/jira/browse/LUCENE-6155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Smiley updated LUCENE-6155:
---------------------------------
Attachment: LUCENE-6155_Payloads_in_MemoryIndex.patch
This patch adds optional payload support to MemoryIndex. BytesRefArray was
useful here.
I added a configuration flag setting to Highlighter's QueryScorer and
WeightedSpanTermExtractor so it gets propagated thru. There are tests at the
highlighter level and MemoryIndex level.
The only nocommit here is related to the maxReusedBytes option introduced by
[~simonw] ... I didn't incorporate that. Perhaps BytesRefArray should have a
constructor to provide one's own ByteBlockPool? Can we re-use the existing
ByteBlockPool in MemoryIndex for this purpose?
> Payload support for MemoryIndex
> -------------------------------
>
> Key: LUCENE-6155
> URL: https://issues.apache.org/jira/browse/LUCENE-6155
> Project: Lucene - Core
> Issue Type: New Feature
> Components: modules/highlighter
> Reporter: David Smiley
> Assignee: David Smiley
> Fix For: 5.0
>
> Attachments: LUCENE-6155_Payloads_in_MemoryIndex.patch
>
>
> MemoryIndex could be enhanced to support payloads. It should be optional,
> defaulting to false.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
