espy opened a new issue, #5291:
URL: https://github.com/apache/couchdb/issues/5291
If you `GET` the `_info` of a ddoc that contains just a `nouveau` section
and one or more indexes, `signature` is always
`3e823c2a4383ac0c18d4e574135a5b08`.
## Description
Any ddoc with just a `nouveau` key always has
`3e823c2a4383ac0c18d4e574135a5b08` as a `signature`, which is also the same as
the `signature` for any "empty" ddoc without any indexes, eg.
```json
{
"_id": "_design/test",
"_rev": "9-1607aa524e868b26cb775a5252a6ced3",
"language": "javascript"
}
```
So it seems the `nouveau` object in ddocs is invisible to the hashing
function used for `signature`.
Note that proper 64bit hashes _are_ generated per ddoc for the _directories
on disk_, so the hashing does work somewhere:
```
data/nouveau/{nodeName}/shards/{shardName}/{databaseName}.{someInteger}/{ddocHash}
```
The `{ddocHash}` here looks as expected (for a Nouveau ddoc, which should
have a 64 bit hash).
## Steps to Reproduce
1. Look at the `/_info` output of any ddoc that has a `nouveau` section
## Expected Behaviour
I would expect these to be different from ddoc to ddoc and between changes
to the same ddoc, like it is for ddocs with a `views` section.
## Your Environment
```json
{
"couchdb":"Welcome",
"version":"3.4.1",
"git_sha":"f504e38a5",
"uuid":"4e36c505782b7068ead9895902c5f07d",
"features":[
"nouveau",
"access-ready",
"partitioned",
"pluggable-storage-engines",
"reshard",
"scheduler"
],
"vendor":{"name":"The Apache Software Foundation"}
}
```
* CouchDB version used: 3.4.1 Mac binary
* Browser name and version: Requests made using Thunder Client for VS Code
* Operating system and version: Mac OS Sonoma 14.6.1
--
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]
