You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
FixedIndex now minimally works, as does basic query context MemoRefHead merging.
The latter allows the relationship traversal to consider memos which are in the query context, but which have not yet generated parent node edits.
What we have is essentially this:
IE: the creation of the basic tree structure, and then edits to the index leaves to reflect the "record" being indexed.
Subsequent passes will enable context to periodically consolidate itself by emitting edits to the non-leaf index subjects, and pruning the context MemoRefHead to include only the edits generated. These will reference the prior leaf subject edits directly, allowing for those Memorefs to be removed from the context, while still yielding the same result.
Proposed next items:
Manual context compression, triggered in the test suite for now, but later to be triggered automatically as the context expands in the natural course of editing.
Update FixedIndex to handle data types other than int
Update FixedIndex to not act badly when values > 256^5 are indexed
Generation of Keyframe memos by the context ( AKA Materialized Memos )
Commutative merging for some memo types ( specifically the index )
Please note that FixedIndex is intended to be temporary. I think balanced trees or similar should be possible, but it's not critical for the Alpha necessarily.
Deliverables:
The text was updated successfully, but these errors were encountered: