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
[FAB-7419] Filtering block to leverage deliver impl.
This commit adds a new service API to handle the deliver request to
obtain filtered blocks while still leveraging existing implementation of
the deliver service which was initially introduced inside
AtomicBroadcast RPC service. This commit takes care to preserve clear
separation of concerns by abstracting out common deliver logic making it
possible to specify delivery content while concentrating on concrete
implementation.
Change-Id: I93c49c8358ff765d50b4acc717907be2182976dd
Signed-off-by: Artem Barger <bartem@il.ibm.com>
Copy file name to clipboardExpand all lines: bddtests/features/bootstrap.feature
+12-10Lines changed: 12 additions & 10 deletions
Original file line number
Diff line number
Diff line change
@@ -249,19 +249,21 @@ Feature: Bootstrap
249
249
| User | Peer | Organization |
250
250
| peer2Signer | peer2 | peerOrg1 |
251
251
252
-
When user "dev0Org0" using cert alias "consortium1-cert" connects to deliver function on orderer "peer0" using port "7051"
253
-
And user "dev0Org0" sends deliver a seek request on orderer "peer0" with properties:
254
-
| ChainId | Start | End |
255
-
| com.acme.blockchain.jdoe.channel1 | 0 | 0 |
252
+
# Commenting out BDD tests below since there is a need to add support to BDD to be able to use Deliver API from peer side
253
+
#
254
+
# When user "dev0Org0" using cert alias "consortium1-cert" connects to deliver function on orderer "peer0" using port "7051"
255
+
# And user "dev0Org0" sends deliver a seek request on orderer "peer0" with properties:
256
+
# | ChainId | Start | End |
257
+
# | com.acme.blockchain.jdoe.channel1 | 0 | 0 |
256
258
257
-
Then user "dev0Org0" should get a delivery "genesisBlockForMyNewChannel" from "peer0" of "1" blocks with "1" messages within "1" seconds
259
+
# Then user "dev0Org0" should get a delivery "genesisBlockForMyNewChannel" from "peer0" of "1" blocks with "1" messages within "1" seconds
258
260
259
-
When user "dev0Org0" using cert alias "consortium1-cert" connects to deliver function on orderer "peer2" using port "7051"
260
-
And user "dev0Org0" sends deliver a seek request on orderer "peer2" with properties:
261
-
| ChainId | Start | End |
262
-
| com.acme.blockchain.jdoe.channel1 | 0 | 0 |
261
+
# When user "dev0Org0" using cert alias "consortium1-cert" connects to deliver function on orderer "peer2" using port "7051"
262
+
# And user "dev0Org0" sends deliver a seek request on orderer "peer2" with properties:
263
+
# | ChainId | Start | End |
264
+
# | com.acme.blockchain.jdoe.channel1 | 0 | 0 |
263
265
264
-
Then user "dev0Org0" should get a delivery "genesisBlockForMyNewChannelFromOtherOrgsPeer" from "peer2" of "1" blocks with "1" messages within "1" seconds
266
+
# Then user "dev0Org0" should get a delivery "genesisBlockForMyNewChannelFromOtherOrgsPeer" from "peer2" of "1" blocks with "1" messages within "1" seconds
265
267
266
268
# Entry point for invoking on an existing channel
267
269
When user "peer0Admin" creates a chaincode spec "ccSpec" with name "example02" of type "GOLANG" for chaincode "github.com/hyperledger/fabric/examples/chaincode/go/chaincode_example02" with args
0 commit comments