The sorting seems to be correct for all the fields. Please let me know what makes you think otherwise and I can fix it.
The purpose of this jira is to put back sorting on data nodes tab. Since it was easy to enable sorting on other tables using the plugin, sorting and pagination was added to those tables as well.
The processing is done completely on the client side and so there is no impact on the server side. At this point, the process of enabling sorting pagination for a table is simple and uniform. To give up this simplicity, there should be some noticeable delay with the current approach.
Tested with 6,000 files. It took time to render 6,000 items irrespective of sorting is enabled or not.
If pagination is set , then items are painted instantly.
In any case, no noticeable delay is caused by sorting. So I am not sure whether there is any point in optimizing this client side logic.
One enhancement which enables the page to render fast , will be to set the default pagination to reasonably higher number like 200. In cases where there are 10,000+ items to paint, the pages gets rendered fast if page size is 200 items. If the user wants all items, then he can select "All" display all files. Or User can search for the file in other pages.I will update the patch with page size set to 200 items for all tables.