lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Simon Willnauer (JIRA)" <j...@apache.org>
Subject [jira] Commented: (LUCENE-2741) Several Codecs use the same files - PerFieldCodecWrapper can not hold two codec using the same files
Date Mon, 15 Nov 2010 17:09:13 GMT

    [ https://issues.apache.org/jira/browse/LUCENE-2741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12932114#action_12932114
] 

Simon Willnauer commented on LUCENE-2741:
-----------------------------------------

For the record : this is also a file format change and requires reindexing if somebody uses
indexes build with Lucene-Trunk

> Several Codecs use the same files - PerFieldCodecWrapper can not hold two codec using
the same files
> ----------------------------------------------------------------------------------------------------
>
>                 Key: LUCENE-2741
>                 URL: https://issues.apache.org/jira/browse/LUCENE-2741
>             Project: Lucene - Java
>          Issue Type: Bug
>          Components: Index
>    Affects Versions: 4.0
>            Reporter: Simon Willnauer
>            Assignee: Simon Willnauer
>             Fix For: 4.0
>
>         Attachments: LUCENE-2741.patch
>
>
> Currently we have a rather simple file naming scheme which prevents us from using more
than one codec in a segment that relies on the same file.  For instance pulsing and standard
codec can not be used together since they both need the .frq .tii .tis etc. To make this work
we either need to write distinct per codec files or set a per field / codec file ID. While
the first solution seems to be quiet verbose the second one seems to be more flexible too.
> One possibility to do that would be to assign a unique id to each SegmentsWriteState
when opening the FieldsConsumer and write the IDs into the segments file to eventually load
it once the segment is opened. Otherwise our PerFieldCodec feature will not be really flexible
nor useful though.  

-- 
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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message