-
Notifications
You must be signed in to change notification settings - Fork 240
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
doesn't support analyzing statement type [set_statement] for SQL: set hive.execution.engine=mr; #504
Comments
This is already supported in master branch via #501 |
Yes, or you can install from master branch if you need it now. |
Hello, I have maked install from master, but it can't support # -*- coding: utf-8 -*-
from sqllineage.runner import LineageRunner
def test_create_as():
sql = """
set hive.execution.engine=mr;
insert into db1.table1 select * from db2.table2;
"""
# result = LineageRunner(sql)
result = LineageRunner(sql, 'hive')
result.print_column_lineage()
print(result.source_tables)
print(result.target_tables)
if __name__ == "__main__":
test_create_as() |
use |
Yes, sqlfluff hive dialect is flawed in parsing set_statement. When set value is string, it's only parsable when quoted.
We need to fix sqlfluff to get this supported then. |
Describe the bug
To Reproduce
Expected behavior
In our Hive SQL file, excute task need change engine (Tez or MR). Ignore set statement during parsing .
Python version (available via
python --version
)SQLLineage version (available via
sqllineage --version
):The text was updated successfully, but these errors were encountered: