Remote NodeState subsystem: collection history/deletions, columnar temporal view, history merge
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 642
- Forks
- 70
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 21
Description
Several remote APIs are deferred until a remote NodeState subsystem exists (shared with algorithm OutputNodeState):
Nodes.history/Edges.history/Edges.deletionscollection views- collection-level
PropertiesView.temporalcolumnar timeline view History.merge/compose_historieson remote history handles- (test-side)
filter.Node.by_state_columnneeds a boolean OutputNodeState column to be exercisable
Depends on the server-side NodeState implementation (see the linked issue in the first comment). These are the corresponding KNOWN_GAPS ledger entries in the parity suite (_parity.py): nodes.history, edges.history, edges.deletions, collection_props.temporal, history.merge, filter.node.by_state_column.
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
Start by reading the linked server-side NodeState issue from the first comment, then inspect the corresponding KNOWN_GAPS entries in _parity.py. The work covers remote history, deletion, temporal, merge, and state-column behavior; it is done when those listed parity gaps are implemented and the boolean OutputNodeState column can be exercised by the filter test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, rust
- Domain
- api, databases, testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100