-
Notifications
You must be signed in to change notification settings - Fork 668
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
improve scorch config parsing of forced zap version #1401
Merged
Merged
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
There are no files selected for viewing
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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -139,17 +139,18 @@ func NewScorch(storeName string, | |
// configForceSegmentTypeVersion checks if the caller has requested a | ||
// specific segment type/version | ||
func configForceSegmentTypeVersion(config map[string]interface{}) (string, uint32, error) { | ||
forcedSegmentVersion, ok := config["forceSegmentVersion"].(int) | ||
if ok { | ||
forcedSegmentType, ok2 := config["forceSegmentType"].(string) | ||
if !ok2 { | ||
return "", 0, fmt.Errorf( | ||
"forceSegmentVersion set to %d, must also specify forceSegmentType", forcedSegmentVersion) | ||
} | ||
forcedSegmentVersion, err := parseToInteger(config["forceSegmentVersion"]) | ||
if err != nil { | ||
return "", 0, nil | ||
} | ||
|
||
return forcedSegmentType, uint32(forcedSegmentVersion), nil | ||
forcedSegmentType, ok2 := config["forceSegmentType"].(string) | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Now that there's no "ok" anymore, "ok2" should be the new "ok" :-D |
||
if !ok2 { | ||
return "", 0, fmt.Errorf( | ||
"forceSegmentVersion set to %d, must also specify forceSegmentType", forcedSegmentVersion) | ||
} | ||
return "", 0, nil | ||
|
||
return forcedSegmentType, uint32(forcedSegmentVersion), nil | ||
} | ||
|
||
func (s *Scorch) paused() uint64 { | ||
|
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
in case of err, its returning nil?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, because error in this case just means that it was not int or float64, in which case we do not proceed to process the settings (which I believe is consistent with what we did before).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am not very sure of this. Giving some hints about the incorrect format looks cleaner to me than not giving any clues to the user of what is going wrong.
Also, unable to comprehend the importance of maintaining consistency with what we did before for a small period of time between v11 - v12/13..
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not arguing for consistency, I'm simply saying I'm not changing the behavior (other than adding support for float64). If you'd like to improve the error handling, maybe you should create your own PR?