-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
[CT-1664] [Feature] Add a new UnsupportedException
exception
#6448
Comments
UnsupportedException
exceptionUnsupportedException
exception
here's an example of how Ibis uses a support registry concept for each backend. Then registry objects can be invoked to generate Ibis's backend feature support matrix. |
We do have a dbt-core/core/dbt/exceptions.py Lines 428 to 432 in c39ea80
(in the same spirit of https://docs.python.org/3/library/exceptions.html#NotImplementedError) Let's use that in favor of a new Some doubts in conversation about the guarantees we'd be able to get from this approach, in terms of automating the creation / update of the original ask:
|
This issue has been marked as Stale because it has been open for 180 days with no activity. If you would like the issue to remain open, please comment on the issue or else it will be closed in 7 days. |
Although we are closing this issue as stale, it's not gone forever. Issues can be reopened if there is renewed community interest. Just add a comment to notify the maintainers. |
re-opening because of #8648 |
UnsupportedException
exceptionTagging @VersusFacit and @emmyoop
Original ask from @dataders : "to build out a feature compatibility matrix across all of our adapters"
The text was updated successfully, but these errors were encountered: