lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Uwe Schindler (JIRA)" <j...@apache.org>
Subject [jira] Commented: (LUCENE-652) Compressed fields should be "externalized" (from Fields into Document)
Date Fri, 20 Mar 2009 17:38:50 GMT

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

Uwe Schindler commented on LUCENE-652:
--------------------------------------

Is an index compressed with Store.COMPRESS still readable? Can i uncompress fields compressed
using the old tools also by retrieving the byte array and using CompressionTools? There should
be some documentation about that.

Another question: Compressing was also used for string fields, maybe CompressionTols also
suplies a method to compress strings (and convert them to UTF-8 during that to be backwards
compatible). This would prevent people from calling String.getBytes() without charset and
then wondering, why they cannoit read their index again...

> Compressed fields should be "externalized" (from Fields into Document)
> ----------------------------------------------------------------------
>
>                 Key: LUCENE-652
>                 URL: https://issues.apache.org/jira/browse/LUCENE-652
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: Index
>    Affects Versions: 1.9, 2.0.0, 2.1
>            Reporter: Michael McCandless
>            Assignee: Michael McCandless
>            Priority: Minor
>             Fix For: 2.9
>
>         Attachments: LUCENE-652.patch
>
>
> Right now, as of 2.0 release, Lucene supports compressed stored fields.  However, after
discussion on java-dev, the suggestion arose, from Robert Engels, that it would be better
if this logic were moved into the Document level.  This way the indexing level just stores
opaque binary fields, and then Document handles compress/uncompressing as needed.
> This approach would have prevented issues like LUCENE-629 because merging of segments
would never need to decompress.
> See this thread for the recent discussion:
>     http://www.gossamer-threads.com/lists/lucene/java-dev/38836
> When we do this we should also work on related issue LUCENE-648.

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


Mime
View raw message