Hello. It has been passed 3 months after last comment. Sorry for bothering you, but I want to make things clear. The problem is that it can makes the error 'Inconsistent Response Payload from Differen

#cache #couchdb

Yes, I have tried that. The CouchDB volumes were removed properly. But even if not, when the Docker containers are removed and re-created - somehow it should be populated (again) if I do the same step

#fabric #couchdb

The second version of the chaincode would have to support both the old and new data. There are various approaches possible: You could attempt to unmarshal the JSON using new data structure, and if it

#fabric #database #couchdb #fabric-chaincode #hyperledger-fabric

Oh, my bad. I had downloaded fabric samples binaries, images, etc a few months back and also downloaded a new one last week only via git clone (so I think only the sample codes changed?). That probabl

#couchdb #docker #fabric

If couchdb returned an error status code while processing the index, we do log the error but chaincode upgrade would succeed irrespective of that. I would suggest to search for the term index to see w

#couchdb #fabric-chaincode

Hi David, thanks for the reply, I've recreated the network and now it seems to work, I'll save save your hint for possible future problems. Mattia IFIN SISTEMI S.R.L. a socio unico Via G. Medici 9/a 3

#couchdb #docker #fabric #fabric-questions

Just for confirmation - spoke with Marek on rocketchat, and the fix for FABCJ-285 will resolve this... will look to put our a patch release in the coming week. Regards, Matthew. Matthew B White IBM Bl

#couchdb #fabric-chaincode #fabric-sdk-java

Private data collections define which organization's peers are authorized to receive and store the private data. This is orthogonal to user based access control. You need to consider both aspects. So

#fabric-chaincode #couchdb #fabric-questions #hyperledger-fabric

I have installed hyperledger fabric 2.0.0. When I try to run the fabcar example, I am getting an error like this "Error: error getting endorser client for channel: endorser client failed to connect to

#fabric-questions #hyperledger-fabric #docker #fabric-chaincode #couchdb

Error: Got error while committing(read tcp 10.0.9.49:37944->10.0.9.15:5984: read: connection reset by peer error reading response body We have the following environment setup and configurations for an

#fabric #couchdb

From the Fabric docs: "If you want to build a dashboard or collect aggregate data as part of your application, you can query an off-chain database that replicates the data from your blockchain network

#fabric-chaincode #hyperledger-fabric #couchdb

This is the 2nd time the peer has crashed due to this error. Nework is on HLF 1.4.2 and the logs are attached in the file. Have anyone faced the same issue before or any ideas on resolving it? I have

#fabric #couchdb #network

Hi suresh, Best thing would be store them into an external secured storage system like into a Private IPFS or azure. In case of IPFS the hash is generated which can be stored in fabric to access the p

#fabricca #fabric-ca #raft #couchdb #fabric

Fabric only exposes a subset of CouchDB functionality. JSON queries and associated indexes are supported, but map reduce queries are not supported, since this is not a pattern we expect many databases

#fabric-chaincode #couchdb