Trace projection is not shared between data sources
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 9.9k
- Forks
- 471
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 117
Description
Noticing this mostly when using saved searches: I'll open a saved search which includes a particular SELECT projection, but when I switch sources the projection seems to reset. It seems like the projection gets stored alongside the source, since switching back to the original store restores the projection.
I'd have expected that for a given saved search that changing the source maintains the same projection. If the current behavior is on purpose, what would be the better way to handle this? Having to keep all sources up to date per saved search seems painful
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce this with a saved search that has a SELECT projection, then switch between its data sources and observe where the projection state is stored. Trace the saved-search and source-switching entry points; done means the same saved search preserves its projection across sources, with coverage for switching away and back.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- observability
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100