search for: dbcompact_no_renumber

Displaying 2 results from an estimated 2 matches for "dbcompact_no_renumber".

2024 Dec 13
1
Using a document id as metadata key and merges
...e that the document ids are preserved during the merge so > that the metadata keys remain valid ? Compaction maps document ids by adding/subtracting a per-source-database offset. By default this is calculated to abut the ranges from each source but you can force the offset to be 0 with Xapian::DBCOMPACT_NO_RENUMBER (--no-renumber). However compaction can't handle input ranges overlapping (after offsetting) so "modulo" isn't going to help here. The reason for this restriction is that compaction mostly copies the encoded postlist data rather than decoding and reencoding it which would be slo...
2024 Dec 12
1
Using a document id as metadata key and merges
Hi, Following a discussion a few years ago, Recoll stores the documents text contents in database metadata entries, with keys derived from document ids. More recently an index creation method using several temporary indexes merged on completion was implemented. This is still a bit experimental. It brings a significant speed increase in some cases. I just realised that the merge lost many