lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Muir (JIRA)" <>
Subject [jira] [Updated] (LUCENE-4090) PerFieldPostingsFormat cannot use name as suffix
Date Wed, 30 May 2012 17:15:24 GMT


Robert Muir updated LUCENE-4090:

    Attachment: LUCENE-4090.patch

attached is a patch for trunk.

tests pass (obviously TestBackCompat fails, its a 4.0 index and we need to fix this there
too before releasing).

I changed the IDHashMap to HashMap, but i didnt implement hashCode/equals on any postingsformats
yet (though, i tested this on Lucene40PostingsFormat).

I think we should do that separately? its optional and a new optimization: today they all
just implement Object.equals which means it works like it did before I broke it :)
> PerFieldPostingsFormat cannot use name as suffix
> ------------------------------------------------
>                 Key: LUCENE-4090
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Bug
>          Components: core/index
>    Affects Versions: 4.0
>            Reporter: Robert Muir
>            Assignee: Robert Muir
>         Attachments: LUCENE-4090.patch
> Currently PFPF just records the name in the metadata, which matches up to the segment
suffix. But this isnt enough, e.g. someone can use Pulsing(1) on one field and Pulsing(2)
on another field.
> See Mark Harwood's examples struggling with this on LUCENE-4069.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message