Comment by 0cf8612b2e1e
3 days ago
This behavior has repeatedly frustrated me. I am writing some new transformation, want to see the results, and my first few sentinel rows are nowhere to be seen because they have been shuffled.
I do not think of a dataframe as a set, but an ordered collection of rows. My source csv had the rows in this order and I want that maintained unless I choose maximum performance.
Why not slap an order_by on the end of the query and you're all good? If that's expensive maybe you can add a limit clause to your source.
Sure, I can change what I get, I just disagree that my ordered table is not guaranteed to stay ordered.
Neither R nor Pandas will shuffle results by default.