Open
Conversation
added 30 commits
April 3, 2026 21:28
Example script output:
bash build-all-backends.sh 2>&1
==> Building duc-tkrzw ...
-> /home/me/duc/testing/duc-tkrzw OK
==> Building duc-tokyocabinet ...
-> /home/me/duc/testing/duc-tokyocabinet OK
==> Building duc-sqlite3 ...
-> /home/me/duc/testing/duc-sqlite3 OK
==> Building duc-lmdb ...
-> /home/me/duc/testing/duc-lmdb OK
==> Building duc-leveldb ...
-> /home/me/duc/testing/duc-leveldb OK
==> Building duc-kyotocabinet ...
-> /home/me/duc/testing/duc-kyotocabinet OK
=== Build summary ===
OK tkrzw (duc version: 1.5.0-rc2)
OK tokyocabinet (duc version: 1.5.0-rc2)
OK sqlite3 (duc version: 1.5.0-rc2)
OK lmdb (duc version: 1.5.0-rc2)
OK leveldb (duc version: 1.5.0-rc2)
OK kyotocabinet (duc version: 1.5.0-rc2)
Example: ./test-compare-backends.sh Indexing path: /usr/share/doc DB dir: /home/gruinelli/temp/duc/testing/dbs [tkrzw] indexing ... opening tkzrw DB with compression: RECORD_COMP_ZSTD done. dumping json ... done. (7140333 bytes) [tokyocabinet] indexing ... done. dumping json ... done. (7140333 bytes) [sqlite3] indexing ... done. dumping json ... done. (7140333 bytes) [lmdb] indexing ... done. dumping json ... done. (7140333 bytes) [leveldb] indexing ... done. dumping json ... done. (7140333 bytes) [kyotocabinet] indexing ... done. dumping json ... done. (7140333 bytes) === Pairwise JSON comparison === tkrzw == tokyocabinet [identical] tkrzw == sqlite3 [identical] tkrzw == lmdb [identical] tkrzw == leveldb [identical] tkrzw == kyotocabinet [identical] tokyocabinet == sqlite3 [identical] tokyocabinet == lmdb [identical] tokyocabinet == leveldb [identical] tokyocabinet == kyotocabinet [identical] sqlite3 == lmdb [identical] sqlite3 == leveldb [identical] sqlite3 == kyotocabinet [identical] lmdb == leveldb [identical] lmdb == kyotocabinet [identical] leveldb == kyotocabinet [identical] Result: all backends produce identical JSON output.
…ict, comment warning
…; raise TIMEOUT to 300s
…ool must not touch duc core
…README.md and root README.md
Author
|
@l8gravely Please review. Don't get confused about all the commits. If they bother you I can create a new PR with a single commit. |
…l must not touch duc core
Author
|
I had the MR pointing to |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
As suggested, I created a migration script.
I also added some shell scripts to test it and documented the DB formats.
See the README's for details.
Notes
/usr/share/docfor the scan by default.tkrzwas source to migrate to any other format is pretty slow (several minutes per destination). Sincetkrzwwill be the new default, it is unlikely a migration from it to other formats is needed, because of this, the tests exclude it by default.Script runs