Do you have the peer logs? Regards, Senthil

the above error seems to match your old definition -- "endorsementPolicy": { "signaturePolicy": "OR('Org1MSP.member'), OR('Org2MSP.member')" } Anyway, I do not have expertise in this. If Yacov looks

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

Sorry for typing it wrong. The endorsement policy in my collections config is as follows: "endorsementPolicy": { "signaturePolicy": "OR('Org1MSP.member', 'Org2MSP.member')" } Setting

As the memberOnlyWrite is set to false by default (not configured in the collection config as well), all peers are authorized to write if it can satisfy the endorsement policy. Is the endorsement

Wouldn't the doc https://hyperledger-fabric.readthedocs.io/en/release-2.0/operations_service.html help? Regards, Senthil

Hi all, I have a fabric 2.0 network with 2 orgs having 1 peer each (similar to test-network). I implemented a private data collection that persists in the off-chain DB of the peer of one of the orgs

Hyperledger Fabric Documentation Workgroup call - Eastern hemisphere When: Friday, 19 June 2020 6:00am to 7:00am (GMT+01:00)

Hi, Would really appreciate if anybody has any thought/suggestion regarding my query. Thanks, Shruti

Hi All, We will hold thedocumentation workgroup calls this Friday -- with both an Eastern hemisphereand Western hemisphere call. Please feel free to come along, you're alwaysvery welcome. You can

If you need to expose all features of a database, changes are needed at the database as well as peer code. if you need to plugin a database that is compatible with what currently Fabric offers, then

Given that, I might be using cloud services to deploy custom database, let's say like SQL DB server, then I do not have the option to alter the databases, right? Plus, the fabric compatibility with

Yes, it is not in the roadmap (may change in the future if some drawbacks with go-plugins are addressed by the go team) Yes. Let's say chaincode exposes Put() to update a kv pair. Based on this

As Gari suggests here, in the JIRA link you mentioned: I was just trying to confirm, that building the plugins as native to Fabric tree in not currently under the timeline, right? Let's say if I

As discussed/decided in https://jira.hyperledger.org/browse/FAB-8665, pluggable stateDB is not going to be supported anytime soon. If you are okay to fork the Fabric, you can find a high level

I learnt that initially there was a plan to implement the Go plugin architecture last year to provide pluggability of state databases in Fabric. However, looking at one of the JIRAs, I found that this

Reminder: Hyperledger Fabric Documentation Workgroup call - Eastern hemisphere When: Friday, 19 June 2020, 6:00am to 7:00am, (GMT+01:00) Europe/London Where:https://zoom.us/j/6223336701 View

A small clarification on this statement. We still validate all reads made by the CouchDB rich query to ensure repeatable read isolation. If any read version is not the same as the committed version

As per the documentation, I understood that the support for SQL is very limited in the forked/proprietary oracle's Fabric (I believe it is not open-sourced). In other words, whatever we can do with

Hi Mark. Do you mind explaining how you ensureserializability? Do you record a digest of the resultsand then re-execute it at commit and compare or something else? And how does that work with mixed