perf: Prune unused operations from sql

[TrevorBergeron]

Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

• Make sure to open an issue as a bug/issue before writing your code! That way we can discuss the change, evaluate designs, and agree on the general idea
• Ensure the tests and linter pass
• Code coverage does not decrease (if any source code was changed)
• Appropriate docs were updated (if necessary)

Fixes #<issue_number_goes_here> 🦕

[tswast]

I'll take a look, but one high-level thought: we should exclude operations from this that might have side effects. Specifically, remote function calls could do all sorts of things (send email, create files in GCS, etc.) without the return value being used.

[TrevorBergeron]

I'll take a look, but one high-level thought: we should exclude operations from this that might have side effects. Specifically, remote function calls could do all sorts of things (send email, create files in GCS, etc.) without the return value being used.

There is a lot that needs to be done to properly model intended side-effects. Lazy evaluation can result in side effects being repeated, while filter pushdown (client side or bigquery side) can remove calls. I think side-effects should probably be explicitly indicated through a special api (maybe with no-output consumer udfs?), and we can then model as its own node type.

[sycai]

This function seems to have no caller. Remove it?

[TrevorBergeron]

removed