Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

What unsorted data really implies #100

Open
nickitat opened this issue Dec 2, 2024 · 2 comments
Open

What unsorted data really implies #100

nickitat opened this issue Dec 2, 2024 · 2 comments

Comments

@nickitat
Copy link

nickitat commented Dec 2, 2024

Hi 👋🏼
I'd like to ask for some clarification. Does the unsorted mode implies that no particular sorting is required (so we're free to use none or any of our choice) or that it is required to have no ordering (or sort-based index etc)?
Thx.

@Tmonster
Copy link
Collaborator

From what I have gathered, sorted mode applied only to data generation, meaning you can generate sorted input data.

If the order of the output data is different, it should not affect result verification, since that is done by calculating aggregate values over the answer table.

@nickitat
Copy link
Author

From what I have gathered, sorted mode applied only to data generation, meaning you can generate sorted input data.

If the order of the output data is different, it should not affect result verification, since that is done by calculating aggregate values over the answer table.

Let me clarify a bit what I really meant to ask: Is it OK to create tables with indexes (e.g., with ordering by join columns) in the unsorted mode? I thought it might not be really fair in case those indexes would improve performance.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants