Mysqltest selectivity.index_dive_limit test produces different results between SeekDB and golden on Android
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 2.9k
- Forks
- 339
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 52
Description
Environment
- Platform: Android (arm64)
- Emulator: Android Studio emulator (device: emulator-5554)
- Binary Path:
/data/local/tmp/seekdb - Startup Command:
./data/local/tmp/seekdb --nodaemon --base-dir /data/local/tmp/seekdb_data --port 5881 - Listening Port: 5881
Description
The mysqltest for selectivity.index_dive_limit (testing index_dive_limit for index dive / partition row estimation) produces inconsistent results between the SeekDB output and the expected golden file when running on an Android environment.
Actual Result
The test output from the Android (Linux) environment differs from the expected golden result file.
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
Start with the mysqltest named selectivity.index_dive_limit and reproduce it using the Android startup command and binary path provided. Compare the SeekDB output with the expected golden result and determine which result differs; the issue does not identify the test or golden file paths, so the exact fix scope remains to be established.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, cpp, mysql
- Domain
- databases, mobile-dev, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100