-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Make sample query compatible with views #50437
base: master
Are you sure you want to change the base?
Make sample query compatible with views #50437
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
@@ -9,7 +9,7 @@ data: | |||
connectorSubtype: database | |||
connectorType: source | |||
definitionId: 435bb9a5-7887-4809-aa58-28c27df0d7ad | |||
dockerImageTag: 3.10.0-rc.4 |
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.
i wondered why did we use rc tag in the previous version.. we could just use the minor version ...
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.
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.
yes, this is why
What
One part of the table sample query was returning a null for a view, which is chosen as the
GREATEST
by another part of the query, leading to incorrect identification of an empty table.How
Ensuring that a view is sampled correctly by using mysql's
COALESCE()
function.User Impact
Views should be read correctly. A refresh of a view stream us recommended.
Can this PR be safely reverted and rolled back?