Zum Hauptinhalt springen

ApplyChangesNodeConfiguration2

Namespace: Meshmakers.Octo.MeshAdapter.Nodes.Load

Configuration node object for apply changes to the object in mongodb

public record ApplyChangesNodeConfiguration2 : NodeConfiguration, INodeConfiguration, IEquatable<NodeConfiguration>, IEquatable<ApplyChangesNodeConfiguration2>

Inheritance Object → NodeConfiguration → ApplyChangesNodeConfiguration2
Implements INodeConfiguration, IEquatable<NodeConfiguration>, IEquatable<ApplyChangesNodeConfiguration2>

Properties​

Identity​

Identity this node runs as: Caller (default), ServiceAccount (the pipeline's service account with its full roles, even when a caller is present), or System (unfiltered, bypasses data permissions). A missing value resolves to Caller so existing pipelines are unchanged (AB#5127).

public NodeExecutionIdentity Identity { get; set; }

Property Value​

NodeExecutionIdentity

EntityUpdatesPath​

The path to the entity update

public string EntityUpdatesPath { get; set; }

Property Value​

String

AssociationUpdatesPath​

The path to the association update

public string AssociationUpdatesPath { get; set; }

Property Value​

String

OnDuplicateKey​

What to do when a unique index refuses the write. Defaults to DuplicateKeyHandling.Throw, which is what the node has always done.

A unique index is the only thing that holds against two callers writing the same natural key at once - a pipeline's own "does it exist yet" lookup reads before it writes, so both callers pass it. DuplicateKeyHandling.Report is for the pipeline that has a sensible answer for the loser of that race: an anonymous HTTP endpoint that would otherwise return a 500, and in a Development environment a stack trace, for what is a routine refusal.

public DuplicateKeyHandling OnDuplicateKey { get; set; }

Property Value​

DuplicateKeyHandling

DuplicateKeyTargetPath​

Where true is written when a unique index refused the write and ApplyChangesNodeConfiguration2.OnDuplicateKey is DuplicateKeyHandling.Report. Nothing is written on the way through, so the pipeline must treat an absent value as "no duplicate".

public string DuplicateKeyTargetPath { get; set; }

Property Value​

String

Description​

public string Description { get; set; }

Property Value​

String

Constructors​

ApplyChangesNodeConfiguration2()​

public ApplyChangesNodeConfiguration2()