Evan Elias

Currently Skeema only supports this cleanly if the desired end-state is having the *exact same* set of tables on multiple databases, i.e. traditional sharding schemes. In that case, there are...

> you won't be able to tell which 'shards' are sharing a definition by looking at `some_common_table1.sql`. You would have to find every symlink that points to it True, although...

It's possible in theory, but my initial reaction is it sounds dangerous. Can you describe your use-case/workflow in more detail please? My thinking is that alters which reduce the size...

I see, that makes sense, thanks! I can confirm that two of these are bugs (i.e. the safety check is being *too* careful), which I should be able to fix...

Just to follow up, the two cases here where the unsafe-check was overly careful are now fixed in master in 901df30aa8c, along with a bunch of other related cases. Thanks...

Jetpants doesn't have support for hot-copy yet, but it is high on the priority list. Most likely it will wrap xtrabackup for this purpose. Currently though all cloning is cold-copy,...

Good catch. The example is just out-of-date. Looks like it wasn't updated to reflect support for multiple shard pools. ("shardname" in your example should be more like "shard_pool_name")

That's odd, it's definitely not a failure mode I've ever seen before. `skeema init` is fairly simple so it doesn't have any extra debug logging. The --debug option is pretty...

Thanks, that's informative -- if you're seeing the exact same behavior even with the wrong password, it means the problem might be located in the Golang mysql driver. To be...

Very strange. So initially I was thinking this was networking-related, but on further thought it might be filesystem-related. `skeema init` does some verification of your current working directory (to ensure...