Shared project memory can now be written to, with warnings when a write stays local instead.
What's wrong with this entry?
A project memory partition can now be described and used as read-write, with explicit warnings when a write cannot reach shared memory and stays local.
- directory listings can describe a store as "public project memory, read-write" when the partition grant is rw and org memory writes are on
- requires the orgMemoryWrites setting, matched against orgMemoryWritesAccount, plus a per-partition "rw" grant
- writes to a discovery-sourced rw store return warnings when the opt-in or grant was withdrawn (the write stays local) and while the grant is being renewed
The synced project memory write grant is being re-established, so this write was saved locally and is NOT yet persisted to shared memory; treat it as not yet persisted until sync succeeds at the next credential renewal.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.242
Artifact
write_dbaccepts a batch of writes under one approvalBoth mention write