support restoring tables from original keyspace to a new one

[tarzanek]

typical use case is to restore data to a new keyspace to do diffs or fixes compared to old keyspace

Scylla supports this and I think SM could too

It's mainly about a new target folder for restore of sstables. Manual workaround using agent download files is obvious, but tedious.

Please consider adding this feature. It'd help automate this common scenario.

[Michal-Leszczynski]

Is this feature request only about keyspace level 1-1 mapping (ksA -> ksB), or is it also about table level 1-1 mapping (ksA.T1 -> ksA.T2 or ksA.T1 -> ksB.T2)? Or perhaps we need more than 1-1 mappings in some cases?

[tarzanek]

I'd start with ks, this should be easier
but yes, table names might be next step

I don't think there are other combinations I saw in field, also anything else changes schema, but this would be a cheap table/ks rename option

[tarzanek]

@Michal-Leszczynski can you put this issue to some roadmap/prioritize it?
I have another occurrence where I need this and it's not possible to do so
(and it'd help a lot on current case)

[tarzanek]

(ref https://github.com/scylladb/scylla-manager/tasks/101962e4-1ad5-4238-9f86-dbb1ba5a7ffd?author=tarzanek )

[Michal-Leszczynski]

Sure, we will discuss it at the next week backlog refinement (cc: @karol-kokoszka).
I will also take a look at the ai generated fix.

[tarzanek]

PR: #4811

[tarzanek]

it looks easy enough, but I of course miss your architecture design, so it might not be fully OK

[kendrick-ren]

We just got another customer requesting the support of this use case of KS mapping, (cc @Michal-Leszczynski @karol-kokoszka )