agrag.vectordb.pending
Pending-record bookkeeping shared by the VectorStore adapters.
A record written for an in-flight Cutover Job lands under a staging id, so a committed record with the real id stays searchable until the job commits and survives the job's rollback.
Functions:
- promote_record – Return the committed record a staged record stands for.
- stage_records – Return records ready to write for one job, or unchanged outside a job.
Attributes:
- PENDING_FLAG – Payload boolean that is true while a record belongs to an in-flight job.
- PENDING_JOB_KEY – Payload key holding the id of the job that wrote a staged record.
- RESERVED_KEYS – Payload keys the stores own; a caller payload may not use them.
- TARGET_ID_KEY – Payload key holding the real id a staged record is promoted to.