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
https://jira.hyperledger.org/browse/FAB-1382
The deliver API currently works on a windowing concept. Because of the
HTTP2/gRPC internal windowing, this additional layer of windowing is
unnecessary.
This changeset removes the notion of a Window from Deliver and instead
replaces it with a start and stop position specification. To receive
blocks indefinitely (replicating the old behavior with ACKs) the end
position may be specified as MAX_UINT64.
This changeset has an unfortunately high amount of ripple, and required
extensive rework in the bdd tests, but the overall changeset is a
simplification.
Change-Id: I5095da82ab1f6d892b0112cdb9848842529936d9
Signed-off-by: Jason Yellick <[email protected]>
Copy file name to clipboardexpand all lines: bddtests/features/orderer.feature
+46-44
Original file line number
Diff line number
Diff line change
@@ -15,28 +15,29 @@ Feature: Orderer
15
15
And I wait "<BootTime>" seconds
16
16
And user "binhn" is an authorized user of the ordering service
17
17
When user "binhn" broadcasts "<NumMsgsToBroadcast>" unique messages on "orderer0"
18
-
And user "binhn" connects to deliver function on "orderer0" with Ack of "<SendAck>" and properties:
19
-
| Start | SpecifiedNumber | WindowSize |
20
-
| SPECIFIED | 1 | 10 |
18
+
And user "binhn" connects to deliver function on "orderer0"
19
+
And user "binhn" sends deliver a seek request on "orderer0" with properties:
20
+
| Start | End |
21
+
| 1 | Newest |
21
22
Then user "binhn" should get a delivery from "orderer0" of "<ExpectedBlocks>" blocks with "<NumMsgsToBroadcast>" messages within "<BatchTimeout>" seconds
Scenario Outline: Basic seek orderer function (Utilizing properties for atomic broadcast)
@@ -45,55 +46,56 @@ Feature: Orderer
45
46
And I wait "<BootTime>" seconds
46
47
And user "binhn" is an authorized user of the ordering service
47
48
When user "binhn" broadcasts "<NumMsgsToBroadcast>" unique messages on "orderer0"
48
-
And user "binhn" connects to deliver function on "orderer0" with Ack of "<SendAck>" and properties:
49
-
| Start | SpecifiedNumber | WindowSize |
50
-
| SPECIFIED | 1 | 10 |
49
+
And user "binhn" connects to deliver function on "orderer0"
50
+
And user "binhn" sends deliver a seek request on "orderer0" with properties:
51
+
| Start | End |
52
+
| 1 | Newest |
51
53
Then user "binhn" should get a delivery from "orderer0" of "<ExpectedBlocks>" blocks with "<NumMsgsToBroadcast>" messages within "<BatchTimeout>" seconds
52
-
When user "binhn" seeks to block "1" on deliver function on "orderer0"
54
+
When user "binhn" sends deliver a seek request on "orderer0" with properties:
55
+
| Start | End |
56
+
| 1 | Newest |
53
57
Then user "binhn" should get a delivery from "orderer0" of "<ExpectedBlocks>" blocks with "<NumMsgsToBroadcast>" messages within "1" seconds
Scenario Outline: Basic orderer function varying ACK
79
+
Scenario Outline: Basic orderer function using oldest seek target
76
80
77
81
Given we compose "<ComposeFile>"
78
82
And I wait "<BootTime>" seconds
79
83
And user "binhn" is an authorized user of the ordering service
80
84
When user "binhn" broadcasts "<NumMsgsToBroadcast>" unique messages on "orderer0"
81
-
And user "binhn" connects to deliver function on "orderer0" with Ack of "<SendAck>" and properties:
82
-
| Start | SpecifiedNumber | WindowSize |
83
-
| SPECIFIED | 1 | 1 |
85
+
And user "binhn" connects to deliver function on "orderer0"
86
+
And user "binhn" sends deliver a seek request on "orderer0" with properties:
87
+
| Start | End |
88
+
| Oldest | 2 |
84
89
Then user "binhn" should get a delivery from "orderer0" of "<ExpectedBlocks>" blocks with "<NumMsgsToBroadcast>" messages within "<BatchTimeout>" seconds
0 commit comments