./startFabric.sh Development only script for Hyperledger Fabric control Running 'startFabric.sh' FABRIC_VERSION is unset, assuming hlfv12 FABRIC_START_TIMEOUT is unset, assuming 15 (seconds) Removing

#couchdb #fabric-peer #hyperledger-fabric

I figure out the issue with this. If anyone encounter the same problem then this might help. Make sure that you're copying the META-INF folder in the external build and release scripts. You can refer

#fabric #couchdb

I am building and deploying the chaincode externally on hyperledger fabric v2.3.2 and using couchdb as the state DB. I would appreciate if anyone could tell me how to package the couch DB indexes? Cou

#fabric #couchdb

Hi everyone. We are trying to build an application in HL Fabric with CouchDB and Golang, and it has grown a bit too much, and now we have many data types where we need to make join equivalents in the

#couchdb #database #fabric

Hi there, I'm was trying to find out if this is possible on the SO and reading the CouchDB documentation, but could not find anything that would work on the Fauxton web client to test it. I have a dat

#couchdb #fabric-chaincode

FYI: we are working with the GO SDK, and we have a struct with idCategory (integer) and another structure with the idCategory and its value. I need to "join" the result. Maybe the solution is not rela

#couchdb #database

Hi. My name is Rodrigo and I am starting with HF (v2.2). Can someone point me a link about how to perform a JOIN (the equivalent map-reduce) using couchdb? I need a doc, an example, something (I googl

#couchdb #database

I had a similar error and ended up being an issue with the high number of records (400k+) processed by the query. I am not sure whether this could be related to your case, but using indexes (and even

#couchdb #fabric-chaincode #hyperledger-fabric

I had a similar error and ended up being an issue with the high number of records (400k+) processed by the query. I am not sure whether this could be related to your case, but using indexes (and even

#couchdb #fabric-chaincode #hyperledger-fabric

Hi David, That's correct! However, we found a minor fix in the chaincode and post that the latest error logs give following stack trace: ``` [34m2021-01-12 09:22:03.362 UTC [endorser] callChaincode ->

#couchdb #fabric-chaincode #hyperledger-fabric

Your first log snippet showed CouchDB queries timing out after 35 seconds each. This is the core.yaml ledger.state.couchDBConfig.requestTimeout of 35s. It means that CouchDB is still processing the qu

#couchdb #fabric-chaincode #hyperledger-fabric

Thanks a lot David for your response. So digging deeper into the logs, we found that peer was returning below error: [chaincode] BuildQueryResponse -> ERRO Failed to get query result from iterator [ch

#couchdb #fabric-chaincode #hyperledger-fabric

Adding workarounds such as longer timeouts will only prolong your pain. You must address the root cause of the slow query in CouchDB. Troubleshoot it in a separate CouchDB environment until you have f

#couchdb #fabric-chaincode #hyperledger-fabric

Hi David, The chaincode is performing a select query on the CouchDB documents, and the fields set for filtering the results are indexed while installing and instantiating the chaincode. The single que

#couchdb #fabric-chaincode #hyperledger-fabric

Hi Samyak Jain, Just to add on top of the approach David suggested. You can use the block event service to do much more like pushing important data to various systems (not just data stores). In the en

#couchdb #fabric #hyperledger-fabric

For any queries/reporting beyond simple JSON queries, the recommendation is to use a downstream purpose-built data service. Chaincode is optimized for transactions, not large queries. See an example o

#couchdb #fabric #hyperledger-fabric

The query appears to be a JSON find query. These queries will be slow or time out if they do not utilize a well designed index against the JSON data. See the CouchDB tutorial for more details: https:/

#couchdb #fabric-chaincode #hyperledger-fabric

Hi, While trying to get data from hyperledger fabric, we are getting following error at client side "Error While Query ERROR:Error: error getting results for query response error: QUERY_STATE_NEXT fai

#couchdb #fabric-chaincode #hyperledger-fabric

Hi Community, We are trying to model the traceability of an asset in hyperledger fabric. We've come up with several ideas but are unsure which one would be most efficient in terms of retrieving tracea

#couchdb #fabric #hyperledger-fabric

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