That's true, but it does not sound like a real problem to me.. Maybe someone else can shed some light upon this.
2012/3/27 samal <samalgo...@gmail.com> > > > On Tue, Mar 27, 2012 at 1:47 AM, R. Verlangen <ro...@us2.nl> wrote: > >> " but any schema change will break it " >> >> How do you mean? You don't have to specify the columns in Cassandra so it >> should work perfect. Except for the "skill~" is preserverd for your list. >> > > In case skill~ is decided to change to skill:: , it need to be handle at > app level. Or otherwise had t update in all row, read it first, modify it, > insert new version and delete old version. > > -- With kind regards, Robin Verlangen www.robinverlangen.nl
