-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
fix injection failure of StorageLocationSelectorStrategy objects #10363
Merged
Merged
Changes from all commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
65583aa
fix to allow customer storage location selector strategy
FrankChen021 a24ae6e
add test cases to check instance of selector strategy
FrankChen021 0a6e163
update doc
FrankChen021 67aaf08
code format
FrankChen021 154d7c5
resolve code review comments
FrankChen021 402571b
inject StorageLocation
FrankChen021 26a98fb
fix CI
FrankChen021 71b416e
fix mismatched license item reported by CI
FrankChen021 fae9a79
change property path from druid.segmentCache.locationSelectorStrategy…
FrankChen021 90dfa73
using a helper method to bind to correct property path
FrankChen021 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
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
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
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
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
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
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
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
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
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
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
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
Oops, something went wrong.
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.
I think the previous implementation is better since you can use the configuration name
druid.segmentCache.locationSelectorStrategy
withouttype
. Is there a reason thatlocationSelectorStrategy
cannot be here?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.
This is because
StorageLocationStrategy
depends onSegmentLoaderConfig.locations
. IfStorageLocationStrategy
is placed here, whenSegmentLoaderConfig
is being deserialized,locations
required byStorageLocationStrategy
can't be found and injected into it.After moving this property out of
SegmentLoaderConfig
, bothSegmentLoaderConfig
andStorageLocationStrategy
are deserialized during construction ofSegmentLoaderLocalCacheManager
, and jackson could find thelocations
objects required by strategy object through google guice framework to create strategy object correctly.Using the configuration name without
type
I think is wrong. Please take a look at this configurationdruid.coordinator.balancer.strategy
, or the clarification on the change of configuration name I left above.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.
Got it. Then, how about using a similar naming to the coordinator balancer? For example, we can bind
StorageLocationSelectorStrategy
todruid.segmentCache.locationSelector
, and use astrategy
property name forStorageLocationSelectorStrategy
instead oftype
.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.
Sorry for the late reply.
Your suggestion makes the naming more meaningful. I'll update this PR later this day.