DataTransaction.set_attr — Queue one manifest attribute update.
tf = DataTransaction.set_attr(tx, key, value) records a key/value pair in an open process-local transaction; commit writes it to the pinned dataset's manifest.
Syntax
tf = DataTransaction.set_attr(tx, key, value)Inputs
tx- Type
Any- Required
- Yes
- Default
- —
- Description
- Managed DataTransaction receiver.
key- Type
StringScalar- Required
- Yes
- Default
- —
- Description
- Attribute key.
value- Type
Any- Required
- Yes
- Default
- —
- Description
- Value to store.
Returns
tf- Type
LogicalArray- Description
- Logical result.
Errors
RUNMAT:Data:Error- When
- A Dataset family receiver, argument, manifest, payload, or filesystem operation fails.
- Message
data: operation failed
RunMat:data:ManifestConflict- When
- A transaction's expected manifest sequence no longer matches the stored manifest.
- Message
data: manifest conflict
RunMat:data:TransactionNotFound- When
- The transaction is absent from the process-local registry.
- Message
data: transaction not found
Value representation
Each stored attribute value must be a string scalar (including a one-element string array), character row vector, finite scalar double, fixed-width integer scalar, or scalar logical value. Numeric/logical array carriers, nonscalar string arrays, character matrices or pages, cells, and nested structs require explicit encoding and are rejected at JSON serialization. Typed missing strings store as JSON null and decode as missing strings. Empty strings and literal spellings such as <missing> remain ordinary text.
Scalar integer values retain exact mathematical value through JSON serialization, including full-width uint64. The original narrow integer storage class is not represented by manifest JSON. No filesystem write occurs at queue time; the value boundary is checked when commit serializes pending attributes.
Example
Queue and commit an attribute
schema = struct(); schema.arrays = struct();
ds = data.create('tx-attr.data', schema);
tx = Dataset.begin(ds);
tf = DataTransaction.set_attr(tx, 'count', uint64(7));
DataTransaction.commit(tx);
fresh = Dataset.refresh(ds);Using DataTransaction.set_attr with coding agents
Open a RunMat example with live inputs, then ask the agent to explain how DataTransaction.set_attr changes the result.
Run a small DataTransaction.set_attr example, explain the result, then change one input and compare the output.
FAQ
Is the update visible before commit?⌄
No. It is held in the process-local transaction queue until commit succeeds.
Related Io functions
Data
commit · data.copy · data.create · data.delete · data.exists · data.export · data.import · data.inspect · data.list · data.move · data.open · DataArray.chunk_shape · DataArray.codec · DataArray.dtype · DataArray.fill · DataArray.name · DataArray.rank · DataArray.read · DataArray.resize · DataArray.shape · DataArray.write · Dataset.array · Dataset.arrays · Dataset.attrs · Dataset.begin · Dataset.get_attr · Dataset.has_array · Dataset.id · Dataset.path · Dataset.refresh · Dataset.set_attr · Dataset.set_attrs · Dataset.snapshot · Dataset.version · DataTransaction.abort · DataTransaction.commit · DataTransaction.create_array · DataTransaction.delete_array · DataTransaction.fill · DataTransaction.id · DataTransaction.resize · DataTransaction.set_attrs · DataTransaction.status · DataTransaction.write
Repl Fs
addpath · cd · copyfile · delete · dir · exist · fileattrib · fileparts · filesep · fullfile · genpath · getenv · getpref · isenv · isfile · isfolder · ispref · ls · matlabroot · memmapfile · memmapfile.subsasgn · memmapfile.subsref · mkdir · movefile · open · opentoline · path · pathsep · pcode · pwd · readstruct · rehash · restoredefaultpath · rmdir · rmpath · run · savepath · setenv · setpref · system · tempdir · tempname · uigetdir · uigetfile · uiputfile · unsetenv · userpath · what · winqueryreg · xmlread · xmlwrite
Tabular
arrayDatastore · csvread · csvwrite · detectImportOptions · dlmread · dlmwrite · fileDatastore · getvaropts · parquetDatastore · parquetinfo · parquetread · readcell · readmatrix · readtable · readtimetable · setvaropts · setvartype · spreadsheetImportOptions · writecell · writematrix · writetable · writetimetable · xlsread · xlswrite
Filetext
fclose · feof · fgetl · fgets · fileread · filewrite · fopen · fprintf · fread · frewind · fwrite · readlines · writelines
Import
Json
Related guides
Source you can read
Every RunMat function's source is public. Read exactly how DataTransaction.set_attr is executed, line by line, in Rust.
- View the source for DataTransaction.set_attr in Rust on GitHub
- Learn how the RunMat runtime works
- Found a bug? Open an issue with a minimal reproduction.
About RunMat
RunMat is a runtime that executes MATLAB-syntax code fast on any GPU. The runtime is free for individuals, including freelancers; students and faculty at an academic institution, for teaching or research there; contributors to an open-source project, for work on that project; organizations with 250 or fewer people and US$10M or less in annual revenue; and anyone, for non-production use. See runmat.com/license.
- RunMat automatically optimizes your math for GPU execution on Apple, Nvidia, and AMD hardware. No code changes needed. Simulations that took hours now take minutes.
- Start running code in seconds. RunMat runs in the browser, on the desktop, or from the CLI. No license server, no IT ticket.