We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
bin
It seems like the bin function declaration is incorrect since it declares ReturnTypeKind.Parameter0 and this doesn't match actual Kusto behavior.
ReturnTypeKind.Parameter0
print v = bin(10, 1.5)
Kusto.Language analysis of this query claims the result type is (v:long), but real Kusto produces (v:real).
(v:long)
(v:real)
In this case, the implications are more significant:
print v=bin(5, 0.8) | union (print v=1234.5)
Kusto.Language analysis of this query claims the result type is (v_long: long, v_real: real), but real Kusto produces (v:real).
(v_long: long, v_real: real)
Tested with Microsoft.Azure.Kusto.Language version 10.0.1. Used App Insights to verify Kusto behavior in case this is relevant.
Microsoft.Azure.Kusto.Language
10.0.1
The text was updated successfully, but these errors were encountered:
This one has also been fixed.
Sorry, something went wrong.
No branches or pull requests
It seems like the
bin
function declaration is incorrect since it declaresReturnTypeKind.Parameter0
and this doesn't match actual Kusto behavior.Trivial example:
Kusto.Language analysis of this query claims the result type is
(v:long)
, but real Kusto produces(v:real)
.Same issue, slightly more complex example
In this case, the implications are more significant:
Kusto.Language analysis of this query claims the result type is
(v_long: long, v_real: real)
, but real Kusto produces(v:real)
.More info
Tested with
Microsoft.Azure.Kusto.Language
version10.0.1
. Used App Insights to verify Kusto behavior in case this is relevant.The text was updated successfully, but these errors were encountered: