Just to clarify, the data that we're loading SSTables from (v1.0.3) doesn't have compression enabled on any of the CF's.
So in theory the compression should occur on the receiving end (v1.1.1) as we're going from uncompressed data to compressed data. So I'm not sure if the bug you mention is causing the behaviour we're seeing here. 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? -- View this message in context: http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/BulkLoading-SSTables-and-compression-tp7580849p7580938.html Sent from the cassandra-u...@incubator.apache.org mailing list archive at Nabble.com.
