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.
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
exp/lighthorizon/cmd: index batch reduce tweaks #4552
exp/lighthorizon/cmd: index batch reduce tweaks #4552
Changes from 3 commits
b4a5a68
0bcf070
cd6322a
b51d4db
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Can you explain the rationale for putting this into the store itself? It feels odd to me that the index store itself should care about something like a sub-URL when the caller can just do a
Join(basePath, subPath)
prior to callingindex.ConnectWithConfig
. That is, above in this diff, why not do the string join prior to the connect as it was 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.
filepath.Join("s3://testing", "job_0")
will mangle the proto scheme slashes, the result from this example iss3:/testing/job_0
which aws sdk didn't like, so, moved the url path composition down to the point at which real store is determined from scheme already and build URL paths in that known context, rather than caller duplicating the same logic to check scheme first to identify store type to know how to compose url path.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 see 🤔 still a little weird to me as I think it's still the caller's responsibility to build sane paths, but I can understand the rationale for hiding it, as well.