tiup bench tpch run queries in a strange order
Open
Nobody has claimed this yet.
component/bench
type/bug
- Dominant language
- Go
- Stars
- 466
- Forks
- 338
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 8
Description
Bug Report
Please answer these questions before submitting your issue. Thanks!
- What did you do?
Run tpch using tiup bench tpch --sf=1 run
- What did you expect to see?
Queries run sequentially as their seq num (q1, q2, q3, q4 ...).
- What did you see instead?
- What version of TiUP are you using (
tiup --version)?
1.4.0 tiup
Go Version: go1.16.2
Git Ref: v1.4.0
GitHash: eb335e6ad9d0dc19d1c43db422cd409d62bc3cea
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the behavior with tiup bench tpch --sf=1 run using the reported TiUP 1.4.0 version and compare the displayed order with q1, q2, q3, and q4. Trace the bench tpch command to find where query execution order is selected; done means the queries run sequentially by sequence number.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100