Add accept_none to SQLTableCheckOperator

[mag3141592]

Description

Right now, SQLColumnCheckOperator has an accept_none parameter that allows a test to pass if the table is empty. For parity, I think this functionality should be available on the SQLTableCheckOperator.

Use case/motivation

I have a table, that may or may not have data in it on a give day.

If it has data in it, I would like it to pass the test I set but if it doesn't I don't want it to fail by default.

Related issues

No response

Are you willing to submit a PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

[denimalpaca]

@josh-fell this can be assigned to me

@mag3141592 if accept_none is True, we still need a default behavior for how the operator handles the tests in its check dict. I don't think marking all the tests True is correct behavior, but False is also probably not correct behavior, as the tests are simply not running. Should the operator simply return here?

I can see a case where the OpenLineage extractor breaks if no boolean value is given to the success field of the check dict, so I do think some default behavior there is warranted.