feat(query): arbitrary target-schema columns #1801
Open
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.
Pull Request checklist
Currently, target-schema "filter" labels (i.e. those used to identify whether-or-not a target-schema is configured against a series) can include only shard-key columns. This PR adds support for arbitrary target-schema filter labels.
For example, a dataset with shard-key columns
SA
andSB
can now have a target-schema defined against an arbitrary columnC
:See here for an example spec.