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
LookupVindex: Implement
internalize
command for lookup vindexes #17429LookupVindex: Implement
internalize
command for lookup vindexes #17429Changes from 12 commits
3ab44c3
944c39c
7038c78
128198d
983a415
ee296d2
f11a0a7
f6f42ba
f63d9f3
18b7de1
e866118
1631cd2
2da390d
db3c825
dca9d30
5c0cda5
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.
This text is a bit off IMO. If we're not able to set the owner (the backing table) as part of the externalize then it's an error. No? Unless I'm missing something, then I think this is better:
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.
Actually, we don't return an error if the vindex is unowned while externalizing, instead we just remove the
write_only
param from the vindex. This is the old behaviour that we follow inLookupVindexExternalize
. Do you think we should change this behaviour (we can return error for unowned vindexes)?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.
OK, fine to leave it as is then. Been a while since I was in this code so had forgotten. Thanks!