I'm not sure how to properly formulate my question/problem but I will try.
I found that by some reason heed does not use tagged lmdb versions (like 0.9.35 etc.) and instead uses some (random?) commit from mdb.master branch (from cloned meilisearch repo but that doesnt make a difference). Issue comes when trying to concurrently use same database from different executables (not necessarily written in Rust) - they all use the officially tagged release. By some mysterious reason Heed uses untagged one. I seem can not find a valid explanation why is it done like this. This especially visible for databases which use lock files because on all taged lmdb versions is
MDB_LOCK_VERSION 1
and on mdb.master
MDB_LOCK_VERSION ((MDB_DEVEL) ? 999 : 2)
This issue is mostly for discussions, I don't have exact opinion how this can/should be solved.
I'm not sure how to properly formulate my question/problem but I will try.
I found that by some reason heed does not use tagged lmdb versions (like 0.9.35 etc.) and instead uses some (random?) commit from mdb.master branch (from cloned meilisearch repo but that doesnt make a difference). Issue comes when trying to concurrently use same database from different executables (not necessarily written in Rust) - they all use the officially tagged release. By some mysterious reason Heed uses untagged one. I seem can not find a valid explanation why is it done like this. This especially visible for databases which use lock files because on all taged lmdb versions is
MDB_LOCK_VERSION 1and on mdb.master
MDB_LOCK_VERSION ((MDB_DEVEL) ? 999 : 2)This issue is mostly for discussions, I don't have exact opinion how this can/should be solved.