You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Daniel Collins (JIRA)" <ji...@apache.org> on 2016/06/16 10:56:05 UTC
[jira] [Updated] (LUCENE-7340) MemoryIndex.toString is broken if
you enable payloads
[ https://issues.apache.org/jira/browse/LUCENE-7340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Collins updated LUCENE-7340:
-----------------------------------
Attachment: LUCENE-7340.diff
This patches toString() so that it works and adds some tests to verify that.
What it doesn't do is actually add a field with payloads into the MI to validate the resulting format.... Still trying to work out how to do that.
> MemoryIndex.toString is broken if you enable payloads
> -----------------------------------------------------
>
> Key: LUCENE-7340
> URL: https://issues.apache.org/jira/browse/LUCENE-7340
> Project: Lucene - Core
> Issue Type: Bug
> Components: modules/highlighter
> Affects Versions: 5.4.1, 6.0.1, master (7.0)
> Reporter: Daniel Collins
> Priority: Minor
> Attachments: LUCENE-7340.diff
>
>
> Noticed this as we use Luwak which creates a MemoryIndex(true, true) storing both offsets and payloads (though in reality we never put any payloads in it).
> We used to use MemoryIndex.toString() for debugging and noticed it broke in Lucene 5.x and beyond. I think LUCENE-6155 broke it when it added support for payloads?
> Creating default memoryindex (as all the tests currently do) works fine, as does one with just offsets, it is just the payload version which is broken.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org