CASSANDRA-3492 fixed the interpretation of chunk_length_kb as a size in bytes but infortunately forgot to convert it back to kb when returning it for thrift/avro. In particular, this means that a describe cf would return things like chunk_length_kb: 65535.
I'm afraid that because migration uses Avro this is kind of a problem. One may have to issue an 'update column family' with the right chunk_length_kb to be sure to be in a safe place.
|Transition||Time In Source Status||Execution Times||Last Executer||Last Execution Date|
|26m 19s||1||Sylvain Lebresne||02/Dec/11 12:26|
|4d 5m||1||Pavel Yaskevich||06/Dec/11 12:31|
|Workflow||patch-available, re-open possible [ 12749299 ]||reopen-resolved, no closed status, patch-avail, testing [ 12756918 ]|
|Workflow||no-reopen-closed, patch-avail [ 12644318 ]||patch-available, re-open possible [ 12749299 ]|
|Status||Patch Available [ 10002 ]||Resolved [ 5 ]|
|Resolution||Fixed [ 1 ]|
|Status||Open [ 1 ]||Patch Available [ 10002 ]|