You'd have to check ColumnFamilyStore.open to see for sure. It might work
that way, but if it does it's an accident -- seems totally fair for it to
assume that there are no SSTables for a newly created CF.
On Wed, Aug 3, 2011 at 9:25 PM, Todd Nine wrote:
> **
> Hi Johnathan,
> One more questi
Hi Johnathan,
One more question. I'm experimenting with the chef recipes for brisk.
Upon the initial installation, the brisk recipe removes the existing
system Keyspace if it's present. The new cluster will not have the"
Spidertracks" keyspace in it's meta data, and will be a completely
vanil
Yes, that should work. For better/worse, CF metadata is stored in the
system schema, not individual sstables.
On Tue, Aug 2, 2011 at 10:00 PM, Todd Nine wrote:
> Hi Johnathan. Are these the correct steps for the upgrade?
>
> 1. Copy SSTable from 0.7.4 snapshot
> 2. Drop CFS in all nodes in 0.7.
Hi Johnathan. Are these the correct steps for the upgrade?
1. Copy SSTable from 0.7.4 snapshot
2. Drop CFS in all nodes in 0.7.4 cluster
3. Upgrade to 0.8.2 and start cluster (with no clients connected)
4. Create CFs using cli in cluster
5. Shutdown all nodes
6. Move the SSTables into place on al
If the bytes are compatible why not just use the existing sstable
files after redefining the schema?
On Tue, Aug 2, 2011 at 8:06 PM, Todd Nine wrote:
> Hi all,
> I seem to have backed myself into a corner and I cannot easily upgrade
> from a custom 0.7.4 installation to the default 0.8.2. Any
