Add "include_alias_metadata" role flag #8719
Closed
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.
When #7985 was merged, it had an unintended side-effect. Any time alias metadata changes, there's an additional storage write. Because an alias can be a role ID with many entities associated with it, this means that the metadata can change at a very high rate, causing a high additional storage load.
This PR places the additional alias metadata behind a flag that is off by default. Folks who wish to obtain that metadata can enable the flag, under advisement that it may have a performance impact.
I considered alternative design approaches. One approach was to analyze which metadata fields were unlikely to change often, and keep those. However, the
account_id
field seemed to be the only one that fit, and it seemed like a better user experience from an understandability standpoint to have the fields be included all or nothing rather than piecemeal.I also considered defaulting this field to "on" but I would rather have users opt in to the performance impact, rather than opting out of it. Since the linked PR is a fairly recent change, I think this is sensible.
Acceptance test output