Seems unlikely, they both run through the same classes which determine their compression strategy via configuration.
The only thing I can think of is that the upgradesstables option follows a
slightly different path to the bulk uploader when it comes to generating the
sstables that have been flushed to disk?
However, prior to running the "upgradesstables" command, the total size of
all the SSTables was 27GB and afterwards its 12GB.
Do you have some of the log messages written when upgrade tables ran ? They will be from compaction and come in pairs you can correlate to same thread, one about what file is being compacted and another about how big the new file is.
Do you have secondary indexes defined on the target CF ?
On 3/07/2012, at 12:32 AM, jmodha wrote: