Adding testing data for better coverage in compatibility-verifier
- Dominant language
- Java
- Stars
- 6.1k
- Forks
- 1.5k
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 189
Description
As suggested by @mcvsubbu we would like to test these features in compatibility-verifier
- No dictionary column
- Offheap memory for consuming segments in server
- Bloom filter
- Range index
- var length dictionary
- partition column (even though there is only one server)
- Walk through the existing queries to see if additional queries can added
Contributor guide
Research direction
Start in the compatibility-verifier and review its existing testing data and queries. Add coverage for the listed dictionary, offheap, Bloom filter, range index, variable-length dictionary, and partition-column cases, then walk through the existing queries to identify additional coverage; done means these scenarios are exercised.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- databases, testing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100