Accidental rename of _ghc or _gho should cause gh-ost fatally exit.
Open
enhancement
- Dominant language
- Go
- Stars
- 13.6k
- Forks
- 1.4k
- Avg merge
- 2h 31m
- Merged PRs (30d)
- 4
Description
We had a situation today where we accidentally renamed the _ghc and _gho tables, however, gh-ost continued to run with just an error saying that the tables didn't exist. The removal, rename, or otherwise loss of the ghost tables, I would think, should cause the process to die a most horrible death. I looked around, and since I don't know `go`, I wasn't able to provide a PR. Please take a look. Thanks.
```
2019-07-15 13:42:50 ERROR Error 1146: Table 'a_database._a_table_ghc' doesn't exist
2019-07-15 13:42:50 ERROR Error 1146: Table 'a_database._a_table_gho' doesn't exist; query=
... snip ...
```
Contributor guide
Assessment
This issue has not been assessed yet.