Btw, FoundationDB org officially supports a document layer (https://github.com/FoundationDB/fdb-document-layer based on MongoDB API) on top of the foundationDB. As it is a multi-modal database, they a

#fabric #fabric-chaincode

Hi Jim, I would like to understand the following: Currently, we support only the query based on a secondary index and JSON from CouchDB (not supporting or planning to support map/reduce functions). Ho

#fabric #fabric-chaincode

Hi The performance study on LevelDB secondary index options is well done. That said, for Fabric, I think it's critical to keep CouchDB as an option. Most of the solutions I look at need the functional

#fabric #fabric-chaincode

I didn’t tested placing the content in the root of the project, as usually the META-INF is placed in the app resource directory (as stated in the initial email). Remarkably, this actually worked! I as

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

Have you placed the index file in the correct location as specified in https://hyperledger-fabric.readthedocs.io/en/release-2.0/couchdb_tutorial.html#add-the-index-to-your-chaincode-folder? Regards, S

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

I'm trying to create a CouchDB index while deploying the Java-based chain code. I was following the documentation from there: https://hyperledger-fabric.readthedocs.io/en/release-2.0/couchdb_tutorial.

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

While executing a submitTransaction method i am getting an error like "2020-04-30T17:18:11.313Z - warn: [Transaction]: _validatePeerResponses: Received error response from peer: message=transaction re

#hyperledger-fabric #fabric-ca-client #fabric-chaincode #fabric-sdk-node

I am getting an error while invoking functions in smart contract Could anyone let me know why i getting this silly error, I only have one argument in the function as argument looks like this "async vi

#fabric-sdk-node #hyperledger-fabric #fabric-ca-client #fabric-chaincode #fabricca

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

There are two organizations A and B. User1 in Org1 has a document Doc1 in his private data store and he wants to share it with User2 of Org2 for a limited time like 3 days, the document shared should

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

Hi Kamlesh I have done what you said and this moment I faced"Error:timed out waiting for txid on all peers" error when I executed "peer lifecycle chaincode approveformyorg" command. Do you know how to

#fabric-chaincode #hyperledger-fabric

Hello, Even with v2.0 it is possible to use the prior chaincode lifecycle process. You would need to make changes in configtx.yaml file for capabilities to be of the previous version instead of v2.0.

#fabric-chaincode #hyperledger-fabric

Hi , It seems you using old chaincode lifecycle in 2.0 release.Can you please try new chaincode lifecycle and see if it works.If it works then you have to look lifecycle endorsement policy configurati

#fabric-chaincode #hyperledger-fabric

Hi all, I have been tried to develop custom network and I faced with an issue when I instantiated the chaincode. I use the chaincode that explained in here (https://hyperledger-fabric.readthedocs.io/e

#fabric-chaincode #hyperledger-fabric

how chaincode example 02 can be modified in hyperledger 1.4.4 help!!

#fabric-chaincode

Thanks a lot Senthil :) I have been meaning to contribute to Hyperledger project, since I started learning Fabric around 2 years back. I guess this is a right time for me to start contributing to the

#fabric #fabric-chaincode

I see. Good to know. Anyway, keep up the good work. I am sure that Manish would be more interested in this work. When we were designing ledger for v1.0, Manish, in fact, proposed to build a query laye

#fabric #fabric-chaincode

Sorry for not being clear. I have already formulated an encoding scheme that requires addition of 4 characters prefix and have implemented queries over that encoding format. But, If there is a good im

#fabric #fabric-chaincode

Hi Prasanth, I remember a similar request made in the past on enabling range queries on composite keys. Hence, we created this JIRA https://jira.hyperledger.org/browse/FAB-11281 but we didn't proceed

#fabric #fabric-chaincode

Hi Senthil, You are right to some extent. My first inspiration is from the composite keys. In fact, the first set of ideas involved just having composite key as index for each and every field in the s

#fabric #fabric-chaincode