Scan on non-existent column family should fail earlier
Open
- Dominant language
- C++
- Stars
- 1.9k
- Forks
- 432
- PR merge metrics
- No merged PRs in 30d
Description
Scan on non-existent column family currently scan a whole tablet and then return empty results.
Probably tablet node should check against table schema to detect non-existent column family earlier.
Contributor guide
No contributing guide indexed for this repository
Research direction
No files, tests, or entry points are named. Start by tracing tablet-node handling for scans against the table schema, then verify that a scan using a non-existent column family is rejected before scanning the tablet and that valid scans still behave as expected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100