Schema changes I assume you guys are talking about different create table or alter table statements. What if multiple threads issue same exact create table if not exists statement? Will that cause issues?
Sent from my iPhone > On Jan 27, 2018, at 11:41 AM, Carlos Rolo <r...@pythian.com> wrote: > > Don't do that. Worst case you might get different schemas in flight and no > agreement on your cluster. If you are already doing that, check "nodetool > describecluster" after you do that. > > Like Jeff said, it is likely to cause problems. > > Regards, > > Carlos Juzarte Rolo > Cassandra Consultant / Datastax Certified Architect / Cassandra MVP > > Pythian - Love your data > > rolo@pythian | Twitter: @cjrolo | Skype: cjr2k3 | Linkedin: > linkedin.com/in/carlosjuzarterolo > Mobile: +351 918 918 100 > www.pythian.com > >> On Sat, Jan 27, 2018 at 7:25 PM, Jeff Jirsa <jji...@gmail.com> wrote: >> It’s not LWT. Don’t do programmatic schema changes that can race, it’s >> likely to cause problems >> >> >> -- >> Jeff Jirsa >> >> >> > On Jan 27, 2018, at 10:19 AM, Kant Kodali <k...@peernova.com> wrote: >> > >> > Hi All, >> > >> > What happens if multiple processes send create table if not exist >> > statement to cassandra? will there be any data corruption or any other >> > issues if I send "create table if not exist" request often? >> > >> > I dont see any entry in system.paxos table so is it fair to say "IF NOT >> > EXISTS" doesn't automatically imply LWT? >> > >> > Thanks! >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org >> For additional commands, e-mail: user-h...@cassandra.apache.org >> > > > -- > > > >
