[
https://issues.apache.org/jira/browse/LUCENE-1465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated LUCENE-1465:
--------------------------------
Attachment: LUCENE-1465.patch
Bah. Its even worse than that. Even after you get down to a min match, it might
not meet the slop requirements! You have to load the payloads and then dump
them if the slop is not met.
I don't like all this extra payload loading. Come to think of it, if you don't
use the getPayload, your still paying for it! I don't have a way around it,
but I don't like it. In this case, not only do you pay for loading, you also
pay for loading the payloads of a bunch of possible matches that don't end up
being a match!
Over a large index with lots of hits, its a lot of payloads to load...
I havn't thought about any of it at a high level, but I think this has to be
addressed somehow...maybe you have to turn on payload collecting first, or it
doesnt do it? We need something...
but until then, I think this still has to be fixed, and we are loading them one
way or another now...might as well add a few more "possible" wrong loads (this
last patch added a couple as well) to make the behavior correct - somewhat
useless otherwise :)
> NearSpansOrdered.getPayload does not return the payload from the minimum
> match span
> -----------------------------------------------------------------------------------
>
> Key: LUCENE-1465
> URL: https://issues.apache.org/jira/browse/LUCENE-1465
> Project: Lucene - Java
> Issue Type: Bug
> Components: Search
> Affects Versions: 2.4
> Reporter: Mark Miller
> Assignee: Mark Miller
> Priority: Minor
> Fix For: 2.9
>
> Attachments: LUCENE-1465.patch, LUCENE-1465.patch, LUCENE-1465.patch
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
