0
0
bleve/index/scorch/segment
Steve Yen a444c25ddf scorch zap merge uses array for docTermMap with no sorting
Instead of sorting docNum keys from a hashmap, this change instead
iterates from docNum 0 to N and uses an array instead of hashmap.
The array is also reused across outer loop iterations.

This optimizes for when there's a lot of structural similarity between
docs, where many/most docs have the same fields.  i.e., beers,
breweries.  If every doc has completely different fields, then this
change might produce worse behavior compared to the previous sparse
hashmap approach.
2018-01-29 10:47:08 -08:00
..
mem scorch zap in-memory segment representation (SegmentBase) 2018-01-27 11:35:10 -08:00
zap scorch zap merge uses array for docTermMap with no sorting 2018-01-29 10:47:08 -08:00
empty.go scorch ref-counting 2017-12-13 14:48:07 -08:00
int_test.go initial version of scorch which persists index to disk 2017-12-06 18:33:47 -05:00
int.go initial version of scorch which persists index to disk 2017-12-06 18:33:47 -05:00
segment.go Include overhead from data structures in segment's SizeInBytes 2018-01-17 11:11:44 -08:00