Beispiel #1
0
 /// <summary>
 /// Prune the ledger specifying the offset before and at which ledger transactions should be removed. Only returns when
 /// the potentially long-running prune request ends successfully or with one of the following errors:
 /// - ``INVALID_ARGUMENT``: if the payload, particularly the offset is malformed or missing
 /// - ``UNIMPLEMENTED``: if the participant is based on a ledger that has not implemented pruning
 /// - ``INTERNAL``: if the participant has encountered a failure and has potentially applied pruning partially. Such cases
 ///   warrant verifying the participant health before retrying the prune with the same (or a larger, valid) offset.
 ///   Successful retries after such errors ensure that different components reach a consistent pruning state.
 ///
 /// Other GRPC errors can be returned depending on the type of condition preventing a prune:
 /// - ``OUT_OF_RANGE``: if the participant is not yet able to prune at the specified offset, but without user intervention
 ///   the offset will eventually be usable for pruning.
 /// - ``FAILED_PRECONDITION`` if some sort of user intervention is required before pruning can proceed at the specified
 ///   offset.
 /// </summary>
 /// <param name="request">The request to send to the server.</param>
 /// <param name="options">The options for the call.</param>
 /// <returns>The call object.</returns>
 public virtual grpc::AsyncUnaryCall <global::Com.Daml.Ledger.Api.V1.Admin.PruneResponse> PruneAsync(global::Com.Daml.Ledger.Api.V1.Admin.PruneRequest request, grpc::CallOptions options)
 {
     return(CallInvoker.AsyncUnaryCall(__Method_Prune, null, options, request));
 }
Beispiel #2
0
 /// <summary>
 /// Prune the ledger specifying the offset before and at which ledger transactions should be removed. Only returns when
 /// the potentially long-running prune request ends successfully or with one of the following errors:
 /// - ``INVALID_ARGUMENT``: if the payload, particularly the offset is malformed or missing
 /// - ``UNIMPLEMENTED``: if the participant is based on a ledger that has not implemented pruning
 /// - ``INTERNAL``: if the participant has encountered a failure and has potentially applied pruning partially. Such cases
 ///   warrant verifying the participant health before retrying the prune with the same (or a larger, valid) offset.
 ///   Successful retries after such errors ensure that different components reach a consistent pruning state.
 ///
 /// Other GRPC errors can be returned depending on the type of condition preventing a prune:
 /// - ``OUT_OF_RANGE``: if the participant is not yet able to prune at the specified offset, but without user intervention
 ///   the offset will eventually be usable for pruning.
 /// - ``FAILED_PRECONDITION`` if some sort of user intervention is required before pruning can proceed at the specified
 ///   offset.
 /// </summary>
 /// <param name="request">The request received from the client.</param>
 /// <param name="context">The context of the server-side call handler being invoked.</param>
 /// <returns>The response to send back to the client (wrapped by a task).</returns>
 public virtual global::System.Threading.Tasks.Task <global::Com.Daml.Ledger.Api.V1.Admin.PruneResponse> Prune(global::Com.Daml.Ledger.Api.V1.Admin.PruneRequest request, grpc::ServerCallContext context)
 {
     throw new grpc::RpcException(new grpc::Status(grpc::StatusCode.Unimplemented, ""));
 }
Beispiel #3
0
 /// <summary>
 /// Prune the ledger specifying the offset before and at which ledger transactions should be removed. Only returns when
 /// the potentially long-running prune request ends successfully or with one of the following errors:
 /// - ``INVALID_ARGUMENT``: if the payload, particularly the offset is malformed or missing
 /// - ``UNIMPLEMENTED``: if the participant is based on a ledger that has not implemented pruning
 /// - ``INTERNAL``: if the participant has encountered a failure and has potentially applied pruning partially. Such cases
 ///   warrant verifying the participant health before retrying the prune with the same (or a larger, valid) offset.
 ///   Successful retries after such errors ensure that different components reach a consistent pruning state.
 ///
 /// Other GRPC errors can be returned depending on the type of condition preventing a prune:
 /// - ``OUT_OF_RANGE``: if the participant is not yet able to prune at the specified offset, but without user intervention
 ///   the offset will eventually be usable for pruning.
 /// - ``FAILED_PRECONDITION`` if some sort of user intervention is required before pruning can proceed at the specified
 ///   offset.
 /// </summary>
 /// <param name="request">The request to send to the server.</param>
 /// <param name="headers">The initial metadata to send with the call. This parameter is optional.</param>
 /// <param name="deadline">An optional deadline for the call. The call will be cancelled if deadline is hit.</param>
 /// <param name="cancellationToken">An optional token for canceling the call.</param>
 /// <returns>The call object.</returns>
 public virtual grpc::AsyncUnaryCall <global::Com.Daml.Ledger.Api.V1.Admin.PruneResponse> PruneAsync(global::Com.Daml.Ledger.Api.V1.Admin.PruneRequest request, grpc::Metadata headers = null, global::System.DateTime?deadline = null, global::System.Threading.CancellationToken cancellationToken = default(global::System.Threading.CancellationToken))
 {
     return(PruneAsync(request, new grpc::CallOptions(headers, deadline, cancellationToken)));
 }