Thinking about http://lucene.markmail.org/message/mef4cdo7m3s6i3fc?q=background+merge+exception
, it occurred to me that we probably should refactor Solr's offering
of compression. Currently, we rely on Field.COMPRESS from Lucene, but
this really isn't considered best practice, see http://www.nabble.com/Need-Lucene-Compression-help----can-pay-nominal-fee-to11001907.html#a11013878
, because it only offers the highest level of compression, which is
also the slowest.
Obviously, Solr needs to handle the compression on the server side. I
think we should have Solr do the compression, allowing users to set
the level of compression (maybe even make it pluggable to put in your
own compression techniques) and then just use Lucene's binary field
capability. Granted, this is lower priority since I doubt many people
use compression to begin with, but, still it would be useful.
-Grant
- Solr's use of Lucene's Compression field Grant Ingersoll
-