Please consider to offer the option of sorting by "Rowindex" without having to create one explicitly. The current sorter only offers to sort by "RowKey" (called RowID everywhere else), and in the current string-based row naming scheme without leading zeroes this leads to the "order" of Row1, Row10, Row1000, Row2, ...
How should it work when there are different naming schemes of the row keys? (Like: versicolor_21, Versicolor_3, versicolor.21, ...) (Sort by row index would be no change in case of ascending (as row index is always the index from the first row) or the reverse in case of descending.)
Indeed special naming makes sense sometimes, but all these (frequent) times that I just need to put a table back into its original order I'd love to have the RowIndex, gladly in addition to the RowKey/RowId.
good things come to those who wait: on behalf of our developers (praise goes to @hotzm !), I’m happy to announce that a alphanumeric sort order has been implemented in the sorter node, the table view, and most other places where sorting is done. Of course, backward compatibility is not broken, so e.g. the GroupBy/Pivot Nodes still sort strings the old fashioned way. Also, this was already available in 4.7.0 in case you didn’t notice Check it out in the new KNIME Version 4.7.1!