Repository navigation
[To dev/1.3] [Pipe] Split OPC UA sink requests by advertised server limits (#18486) - #18510
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Backport
91a44fd8c009a5dfa336953e4fd5aea04ee81586todev/1.3.This adapts OPC UA operation-limit discovery and request batching to the 1.3 branch's Milo 0.6 API. Writes and node-management requests are split according to
MaxNodesPerWriteandMaxNodesPerNodeManagement, with safe defaults when limits cannot be read.Verification:
mvn spotless:apply -pl iotdb-core/datanodegit diff --check origin/dev/1.3...HEAD