[1/4] Add support for WebDX Groups, Feature-Group Mappings & Group Descendants #594
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.
Depends on #593
Description:
This PR introduces the foundational schema and data access layer for managing WebDX Groups and their associations with Web Features in Spanner. This is the beginning of #299 to support only the groups storage and filtering. (Snapshot schema will come separately)
Key Changes
Schema:
WebDXGroups
table to store group metadata.WebFeatureGroups
table to map web features to their associated groups.WebDXGroupDescendants
to include the descendant group IDs for efficient queryingData Access Layer:
UpsertGroup
andGetGroupIDFromGroupKey
methods in theClient
struct to interact with theWebDXGroups
table.UpsertWebFeatureGroup
to manage feature-group mappings in theWebFeatureGroups
table.UpsertGroupDescendantInfo
to manage mappings of groups to all descendant groups.WebFeatureGroup
,groupSpannerMapper
, etc.) to facilitate data mapping and persistence.Purpose