Can the java version chaincode deploy index? #328
Replies: 1 comment 2 replies
-
|
Couch DB indexes should work with Java chaincode in the same way as other chaincode languages. Make sure that the packaged chaincode contains the index in the correct location, relative to the root of the chaincode, not down inside any source folders. See these pages in the Fabric documentation: |
Beta Was this translation helpful? Give feedback.
-
|
I copied the index from go-version asset-transfer-ledger-quires chaincode to go-version asset-transfer-basic chaincode and java-version asset-transfer-basic chaincode. And I changed the field in the index. The go-version asset-transfer-basic chaincode with index is OK. However, the java-version asset-transfer-basic chaincode with index was not successful as well. Do you know what's wrong with my deployment and what caused the difference between two basic chaincode? I think the location is correct. And I use scripts in fabric-samples/test-network to do that, so the steps seem no fault.
|
Beta Was this translation helpful? Give feedback.
-
|
I create a new virtual machine with Ubuntu 20 in VMware, the fabric version is 2.5.4, and deploy the asset-private-data/chaincode-java. There are no index as well.
|
Beta Was this translation helpful? Give feedback.
-
When I deploy the java version asset-transfer-private-data chaincode in test-network, the index deployment was not successful. And the go version asset-transfer-private-data chaincode is OK.
Then, I want check the reason, but there are no java-version asset-transfer-ledger-quires chaincode. So I copied the index from go-version asset-transfer-ledger-quires chaincode to go-version asset-transfer-basic chaincode and java-version asset-transfer-basic chaincode. And I changed the field in the index.
The go-version asset-transfer-basic chaincode with index is OK. However, the java-version asset-transfer-basic chaincode with index was not successful as well.
Beta Was this translation helpful? Give feedback.
All reactions