Issue 391: Update Pravega library versions and deployment script #392
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.
Change log description
Updates Pravega libraries and deployment scripts.
Purpose of the change
Fixes #391.
What the code does
cloudalchemy.node_exporter
naming, iii) device names, iv) Bookkeeper initialization command.provided
todriver-nats-streaming
. The reason for doing that is thatdriver-nats-streaming
is transitively importing a very old version of Google Protobuf (3.9.1
- Aug 06, 2019). Pravega also uses Google Protobuf. When upgrading Pravega, we found aNoSuchMethodError
related to Google Protobuf and the reason was that the newer Pravega version are compiled with a more recent Google Protobuf version with incompatible changes (since version3.17.2
). Having both Google Protobuf versions in the classpath leads to runtime errors, so I decided to prevent the oldest Google Protobuf version to be transitively imported bydriver-nats-streaming
. Given that NATS Streaming has been deprecated, I feel that it is a safe action to do (which can precede the removal of NATS Streaming until NATS JetStream is available).How to verify it