Kusto query limits

[stefanik]

Hi all,
accondingly to microsoft docs (https://docs.microsoft.com/bs-latn-ba/azure/data-explorer/kusto/concepts/querylimits )
Kusto query are allowed to return max 500000 rows or 64MB, as default parameters. 

With set truncationmaxrecords /set truncationmaxsize, we can override that defaults, but from my tests it
seems to be right only if i resize them down: if i try to use for instance set truncationmaxrecords = 600000, PowerBi desktop
retrieves only the first 500K (??? ... my test query has of course more than 500K rows). On the contrary, if i use set truncationmaxrecords = 100000, it gives me the first 100K (as expected). .

Same behaviour if i publish the report to the service. Is this the expected behaviour?
i mean, it is possible to go above the default ones?

Thx
Stefanik

[v-yuaj-msft]

Hi @stefanik ,

Could you kindly share some screessnhots around the issue please? This is not helping much.

Add error screesnhot as well which you are facing.

As far as I know, the default value (500000 rows or 64MB) is up to limit. 

Best Regards,

Yuna

[stefanik]

Thx for your reply.

In reality there isn't any error at all (or at least i'm not able to find it). No refresh error.

Simply, after the refresh, the number of rows are not that expected.

I run a Kusto query that return (from azure portal) 245K rows (this is another test case but the behaviour seems to be the same as my first post). The table in powerbi hold at max 32K rows! 

Each row has a field for a stack trace string that could be big, and i point to the limit of 64MB as the source of the "problem".

If i use set truncationmaxrecords = 10000, the query correctly returns 10K (instead of 32K), but if i set a value greter that 64MB (like for instance 127000000 about 125MB) nothing happen: only 32K rows.

If you say the limit has to be intended as up limit (as test seems to show), there was my misunderstand about them.

I'm asking because from the doc you can see an example like this:

set notruncation;

MyTable | take 1000000

that let me think i can go above the defaults!

Thx

Stefanik

p.s even with set notruncation; -> 32K rows