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

Improved test for partitioned table powered by tsbs #1191

Closed
4 tasks done
Rachelint opened this issue Sep 4, 2023 · 0 comments · Fixed by #1195
Closed
4 tasks done

Improved test for partitioned table powered by tsbs #1191

Rachelint opened this issue Sep 4, 2023 · 0 comments · Fixed by #1195
Labels
feature New feature or request

Comments

@Rachelint
Copy link
Contributor

Rachelint commented Sep 4, 2023

Describe This Problem

Now we just do integration test for the partitioned table using only a few data.
I think it is not engouh for keeping the correctness.

Proposal

Build improved test for partitioned table powered by tsbs.

  • modify tsbs
    • support setting partition-keys, access-mode.
    • support outputing query results to file.
  • impl comparing script
  • make integration bin able to build env only

Additional Context

No response

@Rachelint Rachelint added the feature New feature or request label Sep 4, 2023
Rachelint added a commit that referenced this issue Sep 7, 2023
## Rationale
Close #1191 

The integration test for partitioned table is too simple, now. We just
insert data of poor amount and query them...
In this, tsbs is introudced for big data amount test for partitioned
table.

## Detailed Changes
+ Introduce tsbs and a pre-generated dataset for testing.
+ We don't want to remove and rebuild components(e.g. ceresmeta) on
sometimes, and I added an option to control it in this pr, usage:
```
UPDATE_REPOS_TO_LATEST=false make run-dist-query
```

## Test Plan
It is the test itself.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant