Skip to content
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

Clickhouse SQL 'GLOBAL IN' not support #554

Closed
xiao321 opened this issue Jan 15, 2024 · 3 comments · Fixed by #593
Closed

Clickhouse SQL 'GLOBAL IN' not support #554

xiao321 opened this issue Jan 15, 2024 · 3 comments · Fixed by #593
Labels
bug Something isn't working parser something that requires a strict/validating SQL parser

Comments

@xiao321
Copy link

xiao321 commented Jan 15, 2024

Clickhouse SQL 'GLOBAL IN' not support

sqllineage -f ./sql-global-ck.sql --dialect=clickhouse

SELECT id, name FROM distributed_table WHERE id GLOBAL IN (SELECT id FROM local_table);

Line 1, Position 49: Found unparsable section: 'GLOBAL IN (SELECT id FROM local_table)'

Python 3.8
Sqllineage 1.5.0

@xiao321 xiao321 added the bug Something isn't working label Jan 15, 2024
@maoxingda
Copy link
Contributor

This is not supported by the underlying sqlfluff, not by sqllineage.

@reata
Copy link
Owner

reata commented Jan 15, 2024

Upstream issue sqlfluff/sqlfluff#5256 as reference.

Once they fix the issue and release a new version, we can upgrade the dependency and get this done.

@reata reata added the parser something that requires a strict/validating SQL parser label Feb 4, 2024
@reata
Copy link
Owner

reata commented Feb 19, 2024

Upstream issue is fixed in sqlfluff==3.0.0a5. Since 3.0.0a5 is an alpha release, we will not upgrade sqllineage dependency and will wait for 3.0.0 instead. But you can manually upgrade your sqlfluff to get unblocked.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working parser something that requires a strict/validating SQL parser
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants