Update IoTDB 2.0 client SSL config#548
Merged
Merged
Conversation
HTHou
changed the title
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
1 participant
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.
Summary
2.0.11-260701-SNAPSHOT.Impact
This allows IoTDB 2.0 benchmark runs to use the newer client snapshot and configure mutual SSL/client keystore parameters when SSL is enabled. Existing SSL truststore-only setups continue to work; empty keystore settings are not passed as client keystore paths.
Validation
mvn -pl iotdb-2.0 -am -DskipTests compilemvn -pl iotdb-2.0 -DskipTests dependency:tree -Dincludes=org.apache.iotdb:iotdb-jdbc,org.apache.iotdb:iotdb-session