mirror of
https://github.com/featurebasedb/featurebase.git
synced 2026-09-09 22:51:02 +00:00
clarify sort order in TopN doc
This commit is contained in:
parent
55310a5309
commit
b313902edd
1 changed files with 2 additions and 2 deletions
|
|
@ -342,9 +342,9 @@ have the attribute specified by `field` with one of the values specified in
|
|||
**Result Type:** array of key/count objects
|
||||
|
||||
**Caveats:**
|
||||
* TopN will return the top bitmaps by count only on frames with a ranked cache.
|
||||
* TopN on a frame with ranked cache will return the top bitmaps sorted by count.
|
||||
* Non-ranked frames maintain a LRU (least recently used) cache, thus a TopN query on this frame will return bitmaps sorted in most recently setbit order.
|
||||
* The frame's cache size determines the limit of sorted bitmaps.
|
||||
* Non-ranked frames maintain a LRU (least recently used) cache, thus a TopN query on this frame will return bitmaps in most recently setbit order.
|
||||
* The ranked cache maintains a sorted set of bitmaps by count up to the cache size.
|
||||
* Once full, the cache will truncate the set of bitmaps at the frame options CacheSize limit. Bitmaps with a similar count that straddle the limit will be truncated in no particular order.
|
||||
* The TopN filter operation only applies to data in the cache, and not all bitmaps in the frame.
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue