[Fix][Doc] Fix key description error in redis zh doc
#7993
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
…_column") .stringType() .noDefaultValue() .withDescription("key, list, set, zset use value of a specific column"); public static final Option<String> HASH_KEY_COLUMN = Options.key("hash_key_column") .stringType() .noDefaultValue() .withDescription("The column of hash key you want to write to redis"); public static final Option<String> HASH_VALUE_COLUMN = Options.key("hash_value_column") .stringType() .noDefaultValue() .withDescription("The column of hash value you want to write to redis");
Hisoka-X
changed the title
key description error in redis zh doc
Hisoka-X
approved these changes
Nov 7, 2024
hailin0
approved these changes
Nov 7, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Purpose of this pull request
Fix the document description error in this PR #7888
Does this PR introduce any user-facing change?
How was this patch tested?
Check list
New License Guide
release-note.