Michal-Leszczynski

> in the output, in this order. There are no timestamps, but whoever repeats these commands in this order will reach a situation like you wanted to reach - we...

> It should state something like "Provide a way to restore a single keyspace from an incremental backup as per our documentation procedure". Why would this issue target only incremental...

So this example (tested with Scylla 5.4.0 and raft schema) should illustrate the reason why even when `DESC SCHEMA` includes the `ADD/DROP cf` it can't be used by SM when...

> Do you (or anyone else reading this) know if load-and-stream has some special reconciliation logic which is different from what normal Scylla does? I don't think so. Here is...

AFAIU current state of `DESCRIBE SCHEMA WITH INTERNALS` **CANNOT** be safely used for restore purposes. I already presented an [example](https://github.com/scylladb/scylladb/issues/16482#issuecomment-1867527026) in which dropping and adding ~table~ column before backup might...

@mikliapko could you describe the test scenario? In general, it's not possible to restore schema from backup = 6.0. After taking a look at the implementation, it is also not...

Ref https://github.com/scylladb/scylla-enterprise/issues/4560#issuecomment-2296346862

> To achieve this, the agent is expected to start a background goroutine that periodically checks Scylla's config and updates the cached config. So then SM would still need to...

This test fails on parsing Scylla node logs. From what I see in the logs, this test is run against master Scylla version (`unstable/master:2024-04-24T19:11:44Z`), so maybe there were some changes...

All SM backup metrics visible in this picture are labeled by: - cluster ID - keyspace - table - host This would mean that there is about 2381 tables in...