Skip to content

Commit 1d3bdb1

Browse files
committed
Tweaks.
1 parent 52f0c56 commit 1d3bdb1

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

README.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -127,9 +127,9 @@ byte[][] compressedData = new byte[100000000][]; // Data for 100 million custome
127127
SixBitBinarySearch binary = new SixBitBinarySearch(compressedData, false); // false == exact-match search.
128128
int index = binary.search("key");
129129
```
130-
It is important to note that ```compressedData``` does not need to be completely filled. It could have 70 million entries,
131-
for example, and the binary search would still work. This is because the array of compressed data typically has extra space
132-
to accommodate new entries (usually with some incremental ID implementation to avoid adding in the middle, but always at
130+
It is important to note that ```compressedData``` does not need to be completely filled. It could have 70 million entries
131+
and the binary search would still work. This is because the array of compressed data typically has extra space to
132+
accommodate new entries (usually with some incremental ID implementation to avoid adding in the middle, but always at
133133
the end of the array), so unused slots (nulls) are placed at the end.
134134

135135
A more realistic approach is to organize your data with a unique prefix (usually an ID) and search for it. For example,

0 commit comments

Comments
 (0)