COPY data between tables, keyspaces, and clusters

[Lyky35]

Add ability to copy the data. *(or maybe correct name would export/import wizard)
Functionality wise its likely best if it would make a local copy of table/keyspace that user wants to copy to another table/keyspace/cluster ?maybe in json?
Then use it to insert into another table, keyspace or even cluster. *local copy would allow you to copy data between clusters.
It should give you ability to rename the table/keyspace before you decide to paste it in.
Need ability adjust schema of keyspace in case of different dc's.

Copy table/keyspace to another/new table/keyspace but only if schema matches, or destination doesn't exist.
Different insert methods:

• Upsert to existing data,
• Clean (i.e. drop existing data, and insert the data).
• Copy to new 'table/keyspace'
  *should offer local backup or/& snapshot, as well as ability to specify TTL for the data.
  *should offer running repair on the table/keyspace after copy process is completed.

Load created will be large as you will have to run select * with quorum to ensure you have data from multiple dc if table/keyspace is located in multiple dc's.
Big tables/keyspaces, might work fine for small - it cannot break during copy of large data - pause feature would be also needed, if its taking too much time or can only run during specific hours. Paging copy would be nice, with ability to specify throughput.
What to do if you run out of space; Local and destination.

[millerjp]

Thanks @Lyky35, appreciate the request!

I think copying schema is relatively easy, but the functionality to do copying large amounts of data is more of a serverside exercise than something via a desktop app. But what your suggesting is useful for sure.