Collections, Views, and saved queries — analysis - #1314
Open
joepio wants to merge 1 commit into
Open
Conversation
Map the four "Collection" layers, confirm persisted Collection resources are unused in product paths, and propose retiring them while growing Table Views into the persistable query primitive. Co-authored-by: joepmeindertsma <joepmeindertsma@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Related Issues
Analysis only — no issue closed yet.
Summary
Collections were the original persistable query.
/query,/search, and Table Views now cover that job, and persisted Collection resources are off the product path (not in Base classes,populate_collectionsis test-only, no e2e creates one).This PR adds
planning/collections-and-saved-queries.md: what “Collection” currently means (four layers), what actually runs, and options for unifying the persistable-query idea.Recommendation: retire Collection resources (keep the
/queryenvelope and TSCollectionclient), then growViewinto the named saved query. Extract a separate QuerySpec only if dashboards / LLM tools need the spec without presentation.Checklist