Before this change:
Data files were read in the order they appeared in the snapshot, which sometimes led to new data appearing at the top of the table instead of at the bottom.
This PR:
Fixes the ordering of data files to reflect the commit sequence, ensuring that newer data appears at the end of the table, as expected.
Also, allows comparison between different TableLocationKey implementations using fully qualified class names as a falback.
Before this change: Data files were read in the order they appeared in the snapshot, which sometimes led to new data appearing at the top of the table instead of at the bottom.
This PR:
TableLocationKeyimplementations using fully qualified class names as a falback.