Please provide changelog

[cmenzi]

We just had the issue that after upgrading to 13.3.3 we get an error KS206 that now the case statement, needs to have an orderable datatype. Several of our customers used it like in the screenshot and as we use monaco and also validating queries in our backend, a lot queries are invalid now after the update and couldn't be saved anymore.

But the queries with this error can still be executed even the library reports severity "error".

Therefore, I have some questions and suggestions:

• Does the Kusto Engine at some point also reject those queries?
• Or is the Kusto Engine tolerant and KS206 is actually not an error and it's more a warning?
• Is there a way to find out if this diagnostic is actually not really an error (maybe some error should have another severity)?
• Could you please provide a changelog for library to better keep track what has changed and introduced?
  • For us this was a BREAKING change and didn't assumed a new patch version, will introduce such a big issue.

@avneraa

[mattwar]

This is a bug in the semantic analysis for the case function. If the type of Value is dynamic, the case function is returning type dynamic, when it should be returning type real corresponding to the other non-dynamic argument. The max aggregate is complaining that its argument is typed as dynamic.

[mattwar]

This has been fixed.