makeset operation not preserve ordering?

Question

The following command does not produce a consistent ordering of items:

KubePodInventory
| where ClusterName == "mycluster"
| distinct Computer
| order by Computer asc
| summarize makeset(Computer)

But upon reading the documentation (see here) it states the following:

Like makelist, makeset also works with ordered data and will generate the arrays based on the order of the rows that are passed into it.

Is this a bug or am I doing something wroing?

If the answer works, please help mark it as an answer. It would help others. Thanks. — Ivan Glasenberg, Feb 15 '19 at 04:06

score 1 · Accepted Answer · answered Feb 05 '19 at 06:11

As per this issue @MohitVerma mentioned, makeset() should not support ordering, and they are planning to correct the doc : Like makelist, makeset also works with ordered data and will generate the arrays based on the order of the rows that are passed into it.

You can use makelist() as a workaround, which does support ordering as per my testing.

Mohit Verma · Answer 2 · 2019-02-07T18:21:59.897

Please check this answer for the similar type of operation.

How to order item in Makeset?

Below code worked for me-

requests | summarize makeset(client_City) by client_City | distinct client_City | order by client_City asc

You can follow this thread for the code snippet , marked the answer for closing this thread.

https://github.com/MicrosoftDocs/azure-docs/issues/24135#issuecomment-460185491

requests | summarize makeset(client_City) by client_City | distinct client_City | order by client_City asc | summarize makelist(client_City)

makeset operation not preserve ordering?

2 Answers2