| commit | d5051ae975b38d03d3c2e702839872cadb45790a | |
| author | Olly Betts <olly@survex.com> | |
| Tue, 26 Dec 2017 23:52:51 +0000 (27 12:52 +1300) | ||
| committer | Olly Betts <olly@survex.com> | |
| Tue, 26 Dec 2017 23:52:51 +0000 (27 12:52 +1300) | ||
| tree | 4acf788ec21db06e9a8189d7fee497e6e1daa5c4 | treesnapshot (tar.gz zip) |
| parent | 02c4a934180473f2003324ac4600d4559497964d | commitdiff |
Enable writable tests for sharded databases
Writing to a sharded WritableDatabase has been supported since 1.3.2,
but the test harness wasn't running many of the tests that could be
with a sharded WritableDatabase - now those requiring "writable" are
run, which uncovered a bug in replace_document(term, doc) on a
sharded database (fixed by this commit) and also a bug with
get_termfreq() on a TermIterator from a Document, which currently
returns the termfreq for just the shard the doc is in (not yet fixed -
adddoc2 and adddoc5 trigger this but aren't run under multi for
now).
Writing to a sharded WritableDatabase has been supported since 1.3.2,
but the test harness wasn't running many of the tests that could be
with a sharded WritableDatabase - now those requiring "writable" are
run, which uncovered a bug in replace_document(term, doc) on a
sharded database (fixed by this commit) and also a bug with
get_termfreq() on a TermIterator from a Document, which currently
returns the termfreq for just the shard the doc is in (not yet fixed -
adddoc2 and adddoc5 trigger this but aren't run under multi for
now).