Re: CREATE INDEX without IF NOT EXISTS when snapshoting

Double check your patches apply cleanly to the current branch HEADs, since they are a few months old (CHANGES.txt conflicts and any others you find) and update patches. You're doing the right thing asking for a reviewer/committer to get a little attention. Conflict-free patches help that person. I

Re: CREATE INDEX without IF NOT EXISTS when snapshoting

Guys, Hope you are all doing fine. Is there any news about this trivial issue ? Are you considering to include it in next release? Or there is something I should do? Thanks! Javier. 2017-10-05 10:41 GMT-03:00 Javier Canillas : > Well, > >

RE: CREATE INDEX without IF NOT EXISTS when snapshoting

Ganesh From: Javier Canillas [mailto:javier.canil...@gmail.com] Sent: 05 October 2017 14:42 To: u...@cassandra.apache.org Cc: Cassandra DEV Subject: Re: CREATE INDEX without IF NOT EXISTS when snapshoting Well, Patches submitted for version 3.0, 3.11 and trunk (although 3.0 patch can be applied to

Re: CREATE INDEX without IF NOT EXISTS when snapshoting

Well, Patches submitted for version 3.0, 3.11 and trunk (although 3.0 patch can be applied to 3.11). Feel free to review and comment. Thanks! 2017-10-04 16:41 GMT-03:00 Javier Canillas : > Kurt, > > Thanks for your response. Created this ticket >

Re: CREATE INDEX without IF NOT EXISTS when snapshoting

Kurt, Thanks for your response. Created this ticket . Feel free to add anything to it that seems legit. Downloading Cassandra code right now. Fix seems quite simple. Expect a pull-request soon xD 2017-10-03 20:19 GMT-03:00 kurt greaves : >

Re: CREATE INDEX without IF NOT EXISTS when snapshoting

Certainly would make sense and should be trivial. here is where you want to look. Just create a ticket for it and prod here for a reviewer once

CREATE INDEX without IF NOT EXISTS when snapshoting

Hi everyone, I came across something that bothers me a lot. I'm using snapshots to backup data from my Cassandra cluster in case something really bad happens (like dropping a table or a keyspace). Exercising the recovery actions from those backups, I discover that the schema put on the file "sche