Open jlorberblatt opened 6 years ago
@jlorberblatt thank you!
The existing --aliyun-rds
is a declarative flag, which does not necessarily imply skipping the port check (related: https://github.com/github/gh-ost/issues/631). Perhaps tomorrow Aliyun RDS would imply different checks. So I would not want to couple --skip-port-check
with --aliyun-rds
.
Instead, I suggest adding a --gcp
flag, which incidentally will do same thing as --aliyun-rds
does.
Addressed by #634 . @jlorberblatt would you care to test #634 on GCP?
Verified that this works as expected.
Closed by #634
When executing against a gcp 1st generation sql instance gh-ost fails with the following error:
The value of @@global.port is checked at two points in the code:
the following command demonstrates the port value internal to mysql:
To ignore this value and use the one supplied or default to 3306 which is already being done for other cloud providers I supplied a vendor agnostic command line parameter -skip-port-check in my branch: https://github.com/jlorberblatt/gh-ost/commit/1f7b4087f4a7c1136939427e10c93f2876809970 which I have tested and works.