BUG::max index number in lakeview table does not match number from SQL query

[Element115]

ISSUE:

The following code return 2,230,015:

SELECT MAX([Index])
FROM FACT_RWS;

But after sorting the index column in descending mode in the LH table view, we get a smaller number: 2,169,352.  

Even though the view only shows 1,000 rows, I am assuming that when sorting in descending order, it would return the top 1,000, that is, from the highest or max number down to the 1,000th lower number, just like on a SQL Server instance. But it does not.

[Anonymous]

Hi @Element115 

Can you explain the lakeview table in detail ? The data source you connected is a SQL DB ,right ? You searched the largest index in different places and got different answers, didn't you? Can you provide screenshots of the retrieval operation in two different places? Which is actually the exact value?

Best Regards,
Community Support Team _ Ailsa Tao

[Element115]

What kind of detail do you need about the lakehouse table???

The data source is the lakehouse table and the SQL query is done from the lakehosue SQL analytics endpoint.  So what SQL DB?  

The result of the SQL query is the correct one.  So this is an issue with properly displaying some column maximum when in the lakehouse table view.  Of course, the maximum of an int type.

Screenshot from lakehouse table view, which is incorrect:

and screenshot from the SQL query in the SQL analytics endpoint, which is correct (because I checked against the on-prem DB which is the ultimate source--all I do is transfer the data into a lakehouse from the on-prem DB, but that's not the issue):

[Element115]

@Anonymous Still waiting for your answer... what kind of detail are you requesting?