Alan-Jowett / LexonGraph / 29454789772

82%

Build Type

push

github

Committed by web-flow

Commit Message

Implement Azure Table continuation write batching (#170)

* Implement transaction-first continuation writes

- require continuation-row transaction publication when rows fit one Azure Table transaction
- fall back to concurrent continuation-row inserts while keeping root-row-last commit
- add transaction and concurrent fallback verification coverage

Refs: #164

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Signed-off-by: Alan Jowett <alan.jowett@microsoft.com>

* Reject malformed batch status parsing

- require Azure Table batch responses to yield one parsed operation status per continuation row
- treat empty or truncated batch status parsing as explicit backend failure
- cover batch status parsing expectations in unit tests

Refs: #164

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Signed-off-by: Alan Jowett <alan.jowett@microsoft.com>

* Accept single-status batch success responses

- treat empty Azure Table batch status parsing as a backend failure
- stop requiring one parsed status per continuation row because the live service can return a single successful batch status
- preserve explicit failure handling for malformed empty batch responses

Refs: #164

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Signed-off-by: Alan Jowett <alan.jowett@microsoft.com>

* Tighten continuation write fallback behavior

- surface concurrent continuation-row insert failures without waiting for every request to finish
- stop building oversized Azure Table transaction bodies once the batch payload limit is exceeded
- keep the approved all-at-once concurrent fallback when transaction batching does not fit

Refs: #164

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Signed-off-by: Alan Jowett <alan.jowett@microsoft.com>

* Avoid boundary collisions and duplicate batch builds

- generate high-entropy multipart boundaries per Azure Table transaction request
- eliminate the duplicate ... (continued)

Coverage Stats

255 of 294 new or added lines in 1 file covered. (86.73%)

275 existing lines in 1 file now uncovered.

27268 of 33266 relevant lines covered (81.97%)

78102.2 hits per line