Using Ghost Table for migration
- Dominant language
- Go
- Stars
- 13.6k
- Forks
- 1.4k
- Avg merge
- 2h 31m
- Merged PRs (30d)
- 4
Description
Hello Team,
I have a question based on **GH-OST** tool working.
Firstly, from the documents, and my testing I see that this is creating a separate table, applying changes to the same and then renaming this to the Original table and deleting the old table. Please correct me here, if my understanding is wrong.
So my question here are:
1. Is there a switch or command that I can use to make sure ghost-table is not dropped?
2. Is there a possibility that the created ghost table can be used to migrate it to a different database via third party tools(Eg. Attunity).
3. If there is a way to retain the **ghost table**, then if I again execute a ADD COLUMN command, can this same gh-ost table be used?
Kindly review and please share your comments.
Thanks and Regards,
Abhinav Singh
Contributor guide
Assessment
This issue has not been assessed yet.