-
Notifications
You must be signed in to change notification settings - Fork 7
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
Query Cost Estimation with Dry Run #13
Comments
Really good to have BigQuery in VS Code, one of the only things missing for us is the ability to track the potential cost of the query (the dry run stats we would get in the GUI). |
Good job with the driver, I agree it would be really useful to see potential cost of the query before running it |
I'm trying to scope this effort: src/ls/driver.ts: src/extension.ts:
It will have to be executed using the command palette. At least in this first approach. |
The status bar seems like a pretty sensible place for the output.
You could also make the status bar element clickable to execute it I think? For example, before dry run the status bar could say We do a similar thing in the Evidence VSCode extension |
have anyone working on it? I'm interested in working on this issue, since the scope is clear enough and I really need this feature |
No, you are welcome to it! |
Currently I'm still trying on several alternatives. While I could add new method into the I have tried importing
can you point me to any other resources for the next step? |
I'm afraid I haven't looked into this in detail, so I'm not clear on the best strategy. I opened this issue on the main SQLtools repo, perhaps you could add some details and tag one of the maintainers? |
Do you have your code available so I can pull it down and look into this error? |
Dry run allows you to see how much data will be processed during your query
The text was updated successfully, but these errors were encountered: