Identify unsupported datatypes and bail out with error
Open
- Dominant language
- Go
- Stars
- 13.6k
- Forks
- 1.4k
- Avg merge
- 2h 31m
- Merged PRs (30d)
- 4
Description
Currently `gh-ost` doesn't support `JSON` and `POINT` data types.
Support for `JSON` is imminent, since https://github.com/siddontang/go-mysql/issues/87 is already fixed (but I haven't updated the library). Not sure about `POINT`.
Anyhow, if `gh-ost` _knows_ about an unsupported datatype, it should _say so_.
Related: https://github.com/github/gh-ost/issues/360#issuecomment-277926201
Contributor guide
Research direction
Start by tracing how gh-ost identifies and handles MySQL column datatypes, then inspect the existing error paths and related tests. The work is done when known-unsupported JSON and POINT datatypes produce an explicit error instead of continuing silently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, mysql
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100