Why not supported range scans?
See original GitHub issue Range scans
is not supported for HaloDB. If I want to support range scans function
, what should I do?
Issue Analytics
- State:
- Created 5 years ago
- Comments:5
Top Results From Across the Web
Error: Out of Scan Range. | Sony USA
The error Out of Scan Range may appear if the computer video card is set for a refresh rate the display does not...
Read more >Nmap range scan not working as expected #2488 - GitHub
Nmap detect some available(up) host as not-available(down) when performing ip range scan, But it can detect them correctly when performing ...
Read more >Long range scan not working since patch. : r/X4Foundations
Long range scan not working since patch. It will visually and audibly ping the asteroids around me when the pulse goes out, ...
Read more >Does Google BigTable support range scan? - Stack Overflow
I am confused, the SST table is sorted internally. Two SST tables may not be sorted. In this case, it seems BigTable doesn't...
Read more >Error Messages (Tenable.io)
Warning Message Recommended Action
Scan Aborted Scan aborted because it stalled in initializing. Tenable.io aborted the sca...
Processing Error Unexpected error in processing. Tenable.io aborted...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@shuaijunlan range scans are currently not supported. The workload for which HaloDB was designed for only does point lookups.
I haven’t given this problem much thought yet, but a possible approach could be to use an ordered index in memory. We should ideally not order the data on disk as this would increase read and write amplification for HaloDB, or might force us to do random writes.
HaloDB currently has an in-memory index, which is an off-heap concurrent hash table. To support range scans we could use a
ConcurrentSkipList
as the index, but since HaloDB need to handle large data sets we need an implementation of the skip list which does memory allocation outside the heap. More research is needed to figure out how this will perform and the resources it will consume.This is probably a big effort, and I don’t plan do this immediately.
@amannaly Thank you for your guidance. Is there a more detailed document about HaloDB designing?