Forum Discussion
BUG::LAKEHOUSE PREVIEW::Sort Descending doesn't work
ISSUE:
On first selecting the Sort Descending on an index column, the column gets sorted in ascending order. Try a second time, and the order becomes descending BUT the sequence of value is not contiguous (it should be) ie missing values. Here are screenshots illustrating the correct ordering in the SQL endpoint (which matches that of the on-prem SQL Server) and the lakehouse view (missing values).
SQL endpoint:
Lakehouse view:
4 Replies
- AnonymousNot applicable
Hi Element115 ,
Thanks for using Fabric Community.
At this time, we are reaching out to the internal team to get some help on this .
We will update you once we hear back from them.- AnonymousNot applicable
Hi Element115 ,
Team would like to understand what are you trying to achieve with a full sort in the Lakehouse UI? Why are you doing it? And why in the Lakehouse data preview?- Element115
Memorable Member
What does it matter? Wrong questions all because this is how any DB client works: You click on the sort widget of a column, and of course you expect the column (for whatever amount of rows are in view) to be sorted accordingly. That's standard UI behavior, be it on a Power BI table, or a DB client such as DBeaver or DBForger etc...
So if you want to check what the latest index number is in a LH, thus this shows what came in from the most recent ingest, you can't because in the LH view the sort does not work and does not guarantee a consistent ordering. For this, you need to drop down to the SQL Analytics endpoint.
Is that clearer?