Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement splitting and encoding
ops
,nsInfo
as separateOP_MSG
sections, implement prose tests #1495Implement splitting and encoding
ops
,nsInfo
as separateOP_MSG
sections, implement prose tests #1495Changes from 96 commits
48b9614
af854ed
1eb7466
5567324
644d561
f566303
3d13ffd
cf46b46
e049234
0e16427
0d518d8
6b77f78
2ed8e87
07bac95
16f100b
9f8ce2c
fdb90d2
39386fe
f67af3f
53f6883
9a7b668
395af7a
8f504b0
b02a638
a11e5f6
bfbc1cc
1c3c590
1c9c19e
061e605
8320216
f41ed59
4846e0b
dbf9a26
a0005cd
35eee96
21bb22e
182b2f9
fb32fde
f026ee3
7372f13
0fb65d4
e36898f
70bb422
3584de5
5a17ea0
8e1d770
e973615
33ec764
ee893f2
e33f592
f94ad58
310426a
301a2ba
1a57fb6
6f01e61
c3224e9
c057390
dbb6ec8
cb11c44
8bd7a6a
f781bca
ec88c02
1d4a1d3
14bb86e
2127031
bcbde1e
fcbfe08
752fcbe
764d7de
f186b31
3442a73
ffd4f75
3fc86bb
f9c960c
86e5234
fb134f8
a4bf4d0
2837235
b6702a6
24ce6db
ca5d19a
6d8a3e6
076d39a
6b2b7a8
96733a7
8bda529
11653f0
8d545ff
e2aaa2a
52bb622
70fd9f1
038fafa
f430b7e
cf175d4
ea0633e
9fe35e4
056d411
6f68c0e
ee3073e
0e78b67
38c880d
0156135
f07ff6f
3c6c09f
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does this limitation apply only to
client bulk write
?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am not sure if limitation is the right word here. But yes, this is unique to client bulk writes:
extraElements
before encoding thePAYLOAD_TYPE_1_DOCUMENT_SEQUENCE
section. Thus, when we are encoding the document sequence, we know exactly how much space we have left available before reachingMessageSettings.getMaxMessageSize
.PAYLOAD_TYPE_1_DOCUMENT_SEQUENCE
sections. That is, we may need to write something after writing those sections. That, in turn, means we can't know exactly how much space we have left when we encode document sequences. But whatever we write after writing the sequences, its size is bounded, and 1000 bytes is used in the spec as the value that is definitely not smaller than that bound.