feat: Create a view on the instance, not on the table #1476
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.
Summary:
This PR is being added to address a recent minor change suggested in the design document for Bigtable Authorized Views. To support future feature work, the views should be decoupled from tables and therefore created using a Bigtable instance object instead of a table object.
Background:
This PR is part of a series of PRs for introducing the Bigtable Authorized Views feature. So far this PR and this PR have been merged.
Changes
view
method toInstance
.view
method fromTable
.Next Steps
(Verbatim from the previous PR)
increment
,createRules
andfilter
methods now available onAuthorizedView
. Make sure that these methods pass the proper parameters along and that they target an authorized view.TabularApiSurface
class.