jcoglan commented on issue #4994:
URL: https://github.com/apache/couchdb/issues/4994#issuecomment-2034724358
It appears that it is possible for the design doc signature to vary
according to something we have not yet determined. The client's cluster that we
(Neighbourhoodie) are investigating gives the following results for one of the
design docs affected by a bad index signature:
$ cdb '/' | jq '{ version, git_sha }'
{
"version": "3.3.3",
"git_sha": "40afbcfc7"
}
$ cdb '/{db}/_design/{id}' | md5sum
ef932f29b40bc1795360ea095051d782 -
$ cdb '/{db}/_design/{id}/_info' | jq '.view_index.signature'
"c15a2c0300aefa07abdea125eba80a98"
We copied this design doc and saved into a local dev cluster running the
same CouchDB version/commit, and it gave the same md5sum and signature.
However, when putting this same design doc into the CouchDB service
installed by Homebrew, it gives the same md5sum but a different signature:
$ cdb '/{db}/_design/{id}/_info' | jq '.view_index.signature'
"20ae103a2d660c16f4cbbc43703ede09"
This indicates that it’s possible for the same design document to produce a
different signature on different systems, possibly on different nodes of the
same cluster depending on what the cause is.
Environment of each test:
- Customer production system: Linux, CouchDB v3.3.3, SpiderMonkey 1.8.5,
Erlang 24.3.4.15, ICU library 60.3, collator 153.80, algorithm 10
- Local dev cluster: macOS 13.6.4, CouchDB v3.3.3, SpiderMonkey 91, Erlang
25.3.2.9, ICU library 74.2, collator 153.121, algorithm 15.1
- Homebrew install: macOS 13.6.4, CouchDB v3.3.3, SpiderMonkey 91, Erlang
26.2.1, ICU library 73.2, collator 153.120, algorithm 15
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
