You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As we look to bring more users onto vitess, one area we can smooth over is helping the new user easily validate whether vitess will work in their system. There are a few areas I think any new person should concern themselves with:
Query compatibility
Sharding methodology
Load testing
When I was doing this process a few months ago, I wrote a binary called vtparse that could do all of the validation parts for the first item and output any errors found. This got the job done, but was clunky and is now outdated.
@sougou believes vtcombo could handle the first 2 parts. We'd need to provide some ease-of-access improvements to it:
Allow calling with a single query or a sql file filled with queries.
Allow loading existing schema into it with a sql file
Aggregate output a bit, such as group errors by type (parse error, plan error, etc). It would also be nice to output how many queries were single shard vs multi-shard/db.
Finally, all of this should be documented in an Onboarding document.
As we look to bring more users onto vitess, one area we can smooth over is helping the new user easily validate whether vitess will work in their system. There are a few areas I think any new person should concern themselves with:
When I was doing this process a few months ago, I wrote a binary called vtparse that could do all of the validation parts for the first item and output any errors found. This got the job done, but was clunky and is now outdated.
@sougou believes
vtcombo
could handle the first 2 parts. We'd need to provide some ease-of-access improvements to it:Finally, all of this should be documented in an Onboarding document.
cc @o1egl @derekperkins
The text was updated successfully, but these errors were encountered: