-
Notifications
You must be signed in to change notification settings - Fork 292
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
test: add fuzz tests for column data type alteration #4076
Conversation
Thanks! Would you like to add the target to CI cfg greptimedb/.github/workflows/develop.yml Line 144 in f024054
and greptimedb/.github/workflows/develop.yml Line 286 in f024054
|
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #4076 +/- ##
==========================================
- Coverage 85.47% 85.17% -0.30%
==========================================
Files 991 991
Lines 173053 173141 +88
==========================================
- Hits 147913 147470 -443
- Misses 25140 25671 +531 |
This comment was marked as outdated.
This comment was marked as outdated.
Cool, I got you
Interesting, it works on my machine.
What does the directory structure and .env file look like? (Don't submit any secrets) |
The content is the same as file .env.example, only GT_MYSQL_ADDR=127.0.0.1:4002 |
I don't have any idea about this👀 |
Got it, a little problem, maybe I should restart my machine 🐶 |
We can't to close the #3973 now. We need to insert some values before the alteration and validate the inserted values after the alteration. However, it could be done in another PR. |
I hereby agree to the terms of the GreptimeDB CLA.
Refer to a related PR or issue link (optional)
#3973
What's changed and what's your intention?
Just add fuzz test for
Alter Table <table_name> MODIFY COLUMN <column_name> <column_type>
Checklist