a29dd25a48
This is somewhat unlikely, but if a term is (incredibly) popular, its uvarint count value representation might go beyond 8 bytes. Some KVStore implementations (like forestdb) provide a BatchEx cgo optimization that depends on proper preallocated counting, so this change provides a proper worst-case estimate based on the max-unvarint of 10 bytes instead of the previously incorrect 8 bytes. |
||
---|---|---|
.. | ||
firestorm | ||
store | ||
upside_down | ||
analysis.go | ||
field_cache.go | ||
index.go |