improve wording for database sharding options in UI #13543
Merged
Conversation
This file contains 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
hkernbach
approved these changes
Feb 12, 2021
joerg84
approved these changes
Feb 12, 2021
8 tasks
elfringham
pushed a commit
to elfringham/arangodb
that referenced
this pull request
Apr 20, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Scope & Purpose
Improve the wording for sharding options displayed in the web interface.
Instead of offering
flexibleandsingle, now use the more intuitiveShardedandOneShardoptions, and update the help text for them (refer to attached screenshots for details).We may need to adjust documentation referring to "single" and "flexible" before we can merge this. We also need to decide whether this should be backported to 3.7 or not.
Backports:
Testing & Verification
Link to Jenkins PR run:
http://172.16.10.101:8080/view/PR/job/arangodb-matrix-pr/13971/