simonsobs / simonsobs/sotodlib
ManifestDb needs to support updating a range match
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 19
- Forks
- 23
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 14
Description
(As discussed with @jseibert575)
E.g. suppose we used scheme.add_range_match('obs:obs_timestamp'), then added a record with timestamp=(1800060000,1800070000); and later we realize that item should be extended to (1800080000). Would be nice to simply change a range match of an existing record.
add_entry with replace=True can't help with this because it would not recognize the new entry as being in conflict with the original one (which in itself is a problem!).
Contributor guide
No contributing guide indexed for this repository
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
Start by reading ManifestDb and the add_range_match and add_entry entry points, then reproduce the timestamp example from the issue. Trace how replace=True detects conflicts and determine how an existing range match should be updated; done means the original record can be extended without creating an unrecognized conflicting entry.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100