Files
scylladb/tests
Duarte Nunes 7ba944a243 service/migration_manager: Validate duplicate ID in time
We allow tables to be created with the ID property, mostly for
advanced recovery cases. However, we need to validate that the ID
doesn't match an existing one. We currently do this in
database::add_column_family(), but this is already too late in the
normal workflow: if we allow the schema change to go through, then
it is applied to the system tables and loaded the next time the node
boots, regardless of us throwing from database::add_column_family().

To fix this, we perform this validation when announcing a new table.

Note that the check wasn't removed from database::add_column_family();
it's there since 2015 and there might have been other reasons to add
it that are not related to the ID property.

Refs #2059

Signed-off-by: Duarte Nunes <duarte@scylladb.com>
Message-Id: <20181001230142.46743-1-duarte@scylladb.com>
2018-10-02 13:40:40 +03:00
..
2018-06-25 09:21:47 +01:00
2018-04-29 11:03:21 +03:00
2018-02-14 14:15:59 -05:00
2018-06-15 09:56:45 +01:00
2018-07-25 13:16:06 +02:00
2018-07-18 12:28:06 +01:00
2018-05-22 16:52:58 +02:00