Skip to content
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

SQL Smith Awareness of Stream User Errors #7827

Open
Tracked by #7329
jon-chuang opened this issue Feb 10, 2023 · 3 comments
Open
Tracked by #7329

SQL Smith Awareness of Stream User Errors #7827

jon-chuang opened this issue Feb 10, 2023 · 3 comments
Assignees

Comments

@jon-chuang
Copy link
Contributor

jon-chuang commented Feb 10, 2023

Is your feature request related to a problem? Please describe.

Currently, we are only aware of batch errors. Once we have stream errors collection setup, SQL smith should report those errors to us.

To do so, we should fail CI if there are ANY errors not in the ignore list (user error whitelist).

Then, we should print out a list of all the error types and messages that occured. Unfortunately, according to the current plan, we may not be able to get a backtrace.

Describe the solution you'd like

No response

Describe alternatives you've considered

No response

Additional context

No response

@fuyufjh
Copy link
Member

fuyufjh commented Feb 21, 2023

👀 Does SQL smith support streaming queries?

@jon-chuang
Copy link
Contributor Author

It does. cc @kwannoel

To my understanding, we construct some base tables, MVs, and then several streaming queries and batch queries on top of these in a sequential fashion.

@kwannoel
Copy link
Contributor

It does. cc @kwannoel

To my understanding, we construct some base tables, MVs, and then several streaming queries and batch queries on top of these in a sequential fashion.

Yes that is correct.

@fuyufjh fuyufjh modified the milestones: release-0.18, release-0.19 Mar 22, 2023
@fuyufjh fuyufjh modified the milestones: release-0.19, release-1.1 Jul 14, 2023
@fuyufjh fuyufjh removed this from the release-1.1 milestone Aug 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants