2

I have a function which returns huge number of rows. I need to paginate this data so that I can efficiently render on the UI. I tried to implement using Stored query results. But unfortunately its in preview mode as per the below link, and shouldn't be used in production.

https://learn.microsoft.com/en-us/azure/data-explorer/kusto/management/stored-query-results#pagination

Based on all these restrictions what is the right way to implement pagination without V3 engine or stored query results?

Justin Mathew
  • 950
  • 8
  • 34

1 Answers1

1

Stored Query Results is the right path to go.

It's not in Preview anymore, it's a mistake in the documentation, and we'll fix it (you'll see the change within a few days). The feature is GA, and you can definitely use it in Production.

Slavik N
  • 4,705
  • 17
  • 23
  • 1
    Great you saved our day. @Slavik can you please take a look at this question? https://stackoverflow.com/questions/65501902/kusto-row-cumsum-modifying-the-term-if-term-reaches-a-point – Justin Mathew Apr 07 '21 at 04:53
  • 1
    https://learn.microsoft.com/en-us/azure/data-explorer/kusto/management/stored-query-results still says "Preview" – Usul Jun 16 '21 at 07:27
  • Slavik Still in the documentation it is Preview mode, when we contact support team, even they are also saying its preview mode. We are facing a hard time getting approval to build a poc because of this silly documentation issue. :( – Justin Mathew Jul 14 '21 at 09:48
  • 1
    Hi Justin, please check again in a few days ;) – Slavik N Jul 14 '21 at 10:46
  • 1
    @JustinMathew stored query results is GA now. – Michael Spector Jul 18 '21 at 12:09