Priority: Major - P3
Affects Version/s: WT2.6.1, WT2.7.0
Fix Version/s: WT2.8.0
We found that WT_CURSOR->search_near() positions on wrong key after search for huge key in column-store table.
I'll attach test and DB, test is supposed to be run from examples/c/ directory of WiredTiger (it has hardcoded path to snappy compressor).
I.e. one can see that the last key is 0x30000000003 while after WT_CURSOR->search_near() we're on 0x30000000002