You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently when using any dialect other than non-validating, namely sqlfluff parse implementation, SQLLineage needs to know the statement type before analyzing it.
For example, SelectExtractor supports statement type of ["select_statement", "set_expression", "bracketed"]. And we have a special-purpose NoopExtractor to whitelist a bunch of statement types where no lineage can be extracted.
This whitelist approach solves a problem from non-validating dialect, where we don't know what statement we support. And when user reports a exception, it's hard to tell whether it's a bug or feature.
However, this comes at cost that for statement type we haven't included in the whitelist an UnsupportedStatementException will be thrown. Catch the exception is one way.
In this proposal we'd also like to introduce a new silent_mode option to throw warnings instead of exception.
The text was updated successfully, but these errors were encountered:
Currently when using any dialect other than non-validating, namely sqlfluff parse implementation, SQLLineage needs to know the statement type before analyzing it.
For example, SelectExtractor supports statement type of
["select_statement", "set_expression", "bracketed"]
. And we have a special-purpose NoopExtractor to whitelist a bunch of statement types where no lineage can be extracted.This whitelist approach solves a problem from non-validating dialect, where we don't know what statement we support. And when user reports a exception, it's hard to tell whether it's a bug or feature.
However, this comes at cost that for statement type we haven't included in the whitelist an UnsupportedStatementException will be thrown. Catch the exception is one way.
In this proposal we'd also like to introduce a new silent_mode option to throw warnings instead of exception.
The text was updated successfully, but these errors were encountered: