4.46. RevisionInfo

The revision information for an entity managed through the REST API.

Name Description Schema

clientId optional

A client identifier used to make a request. By including a client identifier, the API can allow multiple requests without needing the current revision. Due to the asynchronous nature of requests/responses this was implemented to allow the client to make numerous requests without having to wait for the previous response to come back.Example : "string"


lastModifier optional read-only

The user that last modified the entity.Example : "string"


version optional

NiFi Registry employs an optimistic locking strategy where the client must include a revision in their request when performing an update. In a response to a mutable flow request, this field represents the updated base version.Example : 0

integer (int64)