Forum Discussion
pivot problem
Ok. I cannot quite get the use case as from math point of view this is working fine. I would assume you can implement some logic in your queries to check first if you have any rows returned at all do the evaluation but if you do not have return something else. Other option is if you do not have results to populate some dummy results so the evaluation operation can have something to work with. If you have to implement that in every query won't be pretty though. You can probably also do a union with dymmy values to make sure you have something to work with. If anyone else can propose a better solution I would be happy to hear it
- I’m aware of the workarounds. I can declare scalar variables of the same names as the columns I know will pivot out of the data. I’m suggesting that the language itself should not require this because it could short circuit when the pipeline has no rows in it. As I’ve pointed out in other posts, evaluate pivot is a fragile function.
Ok. Apologies. I was not aware that is a request. As this is related to the query language it might be best to address this request towards Azure Data Explorer service as they own the query language. They probably also have user voice or you can use whatever channel that you are aware to reach them.
- These days it is hard to tell what is “Azure Log Analytics” and what is “Azure Data Explorer”... or “Azure Monitor logs” and wither Kusto? Things seem to be in the middle of a rebrand. But yes, I’m trying to report bugs in kusto.
https://docs.microsoft.com/en-us/azure/azure-monitor/azure-monitor-rebrand