-
Notifications
You must be signed in to change notification settings - Fork 590
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(mssql-cdc): enrich tests and small refactor #18081
Conversation
* | ||
) from mssql_source table 'dbo.sqlserver_all_data_types'; | ||
|
||
sleep 5s |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What's the intention of the sleep here? create - sleep - drop looks a little weird.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Previously, I found if the types found by (*)
are wrongly converted to RW types, RW will crash explicitly when consuming the data in the upstream table. I've fixed the found mismatch in this PR. This test sleep 5s
is to ensure the data is consumed and the mismatch is encountered so that it can be exposed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Shall we pick this PR to release-2.0? |
Yes, I think so. I'll confirm with jianwei. |
Co-authored-by: Kexiang Wang <[email protected]>
I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
Add tests for
INCLUDES
Refactor:
SELECT * FROM {} WHERE 1 = 0
toINFORMATION_SCHEMA.COLUMNS
-based SQL.Checklist
./risedev check
(or alias,./risedev c
)Documentation
Release note
If this PR includes changes that directly affect users or other significant modifications relevant to the community, kindly draft a release note to provide a concise summary of these changes. Please prioritize highlighting the impact these changes will have on users.