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

aggregate_test_100_with_order is not itself ordered #6850

Closed
mustafasrepo opened this issue Jul 5, 2023 · 0 comments · Fixed by #6852
Closed

aggregate_test_100_with_order is not itself ordered #6850

mustafasrepo opened this issue Jul 5, 2023 · 0 comments · Fixed by #6852
Labels
bug Something isn't working

Comments

@mustafasrepo
Copy link
Contributor

Describe the bug

In explain.slt file we create a table with following statement

statement ok
CREATE EXTERNAL TABLE aggregate_test_100_with_order (
        c1  VARCHAR NOT NULL,
        c2  TINYINT NOT NULL,
        c3  SMALLINT NOT NULL,
        c4  SMALLINT NOT NULL,
        c5  INTEGER NOT NULL,
        c6  BIGINT NOT NULL,
        c7  SMALLINT NOT NULL,
        c8  INT NOT NULL,
        c9  INT UNSIGNED NOT NULL,
        c10 BIGINT UNSIGNED NOT NULL,
        c11 FLOAT NOT NULL,
        c12 DOUBLE NOT NULL,
        c13 VARCHAR NOT NULL
    )
STORED AS CSV
WITH HEADER ROW
WITH ORDER (c1 ASC)
LOCATION '../../testing/data/csv/aggregate_test_100.csv';

It says that, table is ordered according to c1 ASC. However, file at path ../../testing/data/csv/aggregate_test_100.csv is not ordered. Since tests with this table checks physical plans, everything works as expected.
However, if we were to run query using this table, we would receive wrong results because contract doesn't hold.

To Reproduce

No response

Expected behavior

I would like to have a new variant of the csv file (../../testing/data/csv/aggregate_test_100.csv), where c1 ASC is satisfied in the file.

Additional context

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant