Memory (Internal)
A RocketRide in-process memory node for temporary, keyed values within a
pipeline instance. Pick it for short-lived agent scratch space; use
memory_persistent when state must be retained across sessions.
About RocketRide
RocketRide hosts this node as a Python pipeline component. The node itself implements a small in-process store and has no separately configured service or dependency.
What it does
Creates a new keyed store for each node instance, then clears that store when
the instance is opened. It has no data lanes: its registered operations store,
retrieve, list, and clear values for code or an agent using the node. Choose it
over memory_persistent when the desired lifetime is only the current
instance and an external backend is unnecessary.
Configuration
This node has no configuration fields, profiles, or lanes. Add it when its run-scoped lifetime is appropriate; stored values are not copied or persisted by the node, so do not use it for data that must survive a new instance.
Notes
Registered operations
The node registers four operations under the memory prefix:
| Function | Description |
|---|---|
memory.put | Store a value under a key. |
memory.get | Retrieve the value for a key. |
memory.list | Return all stored keys in sorted order. |
memory.clear | Remove one key or all keys. |
memory.put requires a non-empty string key and a value; it trims the key
before storing and returns {ok: true, key}. memory.get requires a non-empty
string key; a missing key returns {ok: false, key, value: null}. The
no-argument memory.list returns {ok: true, keys}. memory.clear accepts
an optional string key; omitting it, or supplying an empty or whitespace-only
key, clears every stored key and returns them in cleared.
Calls whose argument object is not a dictionary, or whose required key/value
is invalid or missing, raise a ValueError before reaching the store. Clearing
a specified key that does not exist is successful and returns an empty
cleared list.
Lifetime
beginInstance creates the store and open clears it. In particular, opening
the node starts with an empty store even if the same instance was previously
used. The implementation uses a Python dictionary only; it does not provide
cross-instance or cross-process persistence.
Upstream docs
Schema
No configuration fields.