-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
fix_client_abort: Resolve Client Abortion When Using KQL Table function #63992
Conversation
…Function in Interactive Mode
This is an automated comment for commit fd322df with description of existing statuses. It's updated for the latest CI running ❌ Click here to open a full report in a separate page
Successful checks
|
@kashwy, I don't understand the whole idea of
|
Let's imagine that someone implemented a table function The queries could look like
Neither ClickHouse Lexer nor Parser should take care of gibberish. |
The idea of the kql table function originates from our clients. They wanted the capability to run Kusto queries within SQL.
|
Changelog category (leave one):
Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md):
(Low-quality third-party Kusto Query Language). Resolve Client Abortion Issue When Using KQL Table Function in Interactive Mode
When typing a statement to call the KQL table function in interactive mode, the client aborts midway. This issue began occurring after the syntax highlighting feature was introduced (version 24.4 , 24.5). For example, if you type:
select * from kql(t
the client aborts unexpectedly
This PR fix the issue