You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have a blockchain channel consisting of 100+ orgs. When adding a new private data collection in collection definition file, since the chain code source code is not changed, the CC version number is not increased, but since collection definition file is modified sequence number is increased. Currently, we've got to have all 100+ orgs to install and approve chain code with new collection definition file for the chain code to be effective. It's a lot of work for collaboration in a decentralized system like HLF.
Expected
Only orgs related to the newly added collection (e.g. orgs in policy item of the collection) in collection definition file should have to install and approve the chain code. All other orgs shall not be influenced by the newly created collection.
Example: If I add a new collection assetCollection as follows, it will only be recognized by Org1 and Org2. So only Org1 and Org2 will have to install and approve it. All other orgs don't have to realize assetCollection is added since they will not read or write to it, so all other orgs will not install and approve the chain code again with the updated collection definition file.
kaiknight
changed the title
Adding collection in collection definition file shall not influence all orgs
Adding a private data collection shall not influence all orgs
Dec 6, 2023
Current Status
We have a blockchain channel consisting of 100+ orgs. When adding a new private data collection in collection definition file, since the chain code source code is not changed, the CC version number is not increased, but since collection definition file is modified sequence number is increased. Currently, we've got to have all 100+ orgs to install and approve chain code with new collection definition file for the chain code to be effective. It's a lot of work for collaboration in a decentralized system like HLF.
Expected
Only orgs related to the newly added collection (e.g. orgs in policy item of the collection) in collection definition file should have to install and approve the chain code. All other orgs shall not be influenced by the newly created collection.
Example: If I add a new collection assetCollection as follows, it will only be recognized by Org1 and Org2. So only Org1 and Org2 will have to install and approve it. All other orgs don't have to realize assetCollection is added since they will not read or write to it, so all other orgs will not install and approve the chain code again with the updated collection definition file.
---- collection definition file ---
[
{
"name": "assetCollection",
"policy": "OR('Org1MSP.member', 'Org2MSP.member')",
"requiredPeerCount": 1,
"maxPeerCount": 1,
"blockToLive":1000000,
"memberOnlyRead": true,
"memberOnlyWrite": true
},
....
other existing collections
]
Solution
No response
Please let us know if you plan to work on this.
No response
The text was updated successfully, but these errors were encountered: