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

Did you remove the volumes listed in "docker volume ls", this is where the couch data is stored mario.schwaiger@... --- [EXTERNAL] Re: [Hyperledger Fabric] Removed Databases, can't reset

#fabric #couchdb

Even more confusing, by default in the core.yaml I had: stateDatabase: goleveldb How had there ever been data in the couchdb - and why is there none now after a complete reset? And where is the LevelD

#fabric #couchdb

Hi! I was testing out the database capabilities and effects on changes in the fabric-samples. (fabcar) In a trial run I've removed all databases and all data from both couchdb-Docker instances. Everyt

#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

I've a query on how we need to deal with data structure changes in chaincode. Lets say, you have deployed the chaincode in production and lot of data stored in ledger and world state db(Couchdb). If y

#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

How did you download all the components for fabric samples? Did you use the convenience script we provide? If so what parameters did you use on it. If you downloaded everything late last week, it's po

#couchdb #docker #fabric

I am trying to bring up the latest fabric-samples/test-network with this script: ./network.sh up createChannel -ca -s couchdb But I kept coming up with this error: Error: error getting endorser client

#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

What should I search for in the peer logs? Some sort of error? Because I can't see the index on the couchdb entries

#couchdb #fabric-chaincode

Do you have the peer logs? Regards, Senthil

#couchdb #fabric-chaincode

Hi, I currently trying to add a new index to my 1.4 network. I have the folders correctly set too. When I update the chaincode with the new index folder I can see that my peers have the package correc

#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

Some additional peer logging would help to troubleshoot it: FABRIC_LOGGING_SPEC=info:statecouchdb,couchdb=debug Dave Enyeart "Mattia Bolzonella" ---06/11/2020 05:37:49 AM---Hi, i'm trying to start a p

#couchdb #docker #fabric #fabric-questions

Hi, i'm trying to start a peer but I get the error reportet in the below log dump. I can't figure out how to solve it. 2020-06-05 08:41:17.126 UTC [peer] getLocalAddress -> INFO 002 Auto-detected peer

#couchdb #docker #fabric #fabric-questions

Speaking more generally... JSON spec does not guarantee a certain order or formatting. What you put into a JSON database (whether CouchDB, MongoDB, etc) may not match exactly what you get back. Only t

#cache #couchdb

Hi Jeehoon Lim, Thank you for the nice explanation. The read-write set constructed by the peer should be consistent across peers In the read-set, we include only the version not the actual data. In th

#cache #couchdb

Hi all. I report a bug to Hyperledger Jira. ( https://jira.hyperledger.org/browse/FAB-17954 ) Please check wheather it could be a real problem or not, and which is better solution for this. ==========

#cache #couchdb