From a9241679e7a4e39d97ad32d122cc98279e835ed3 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Christian=20Neum=C3=BCller?= Date: Mon, 2 Sep 2019 15:09:24 +0200 Subject: [PATCH] Rename FailedNoneRetryable -> FailedNotRetryable The former sounds strange to me. Alternative suggestion: FailedUnretryable. --- specification/sdk-exporter.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/specification/sdk-exporter.md b/specification/sdk-exporter.md index 50c2c720cdc..98fac17ceb7 100644 --- a/specification/sdk-exporter.md +++ b/specification/sdk-exporter.md @@ -32,7 +32,7 @@ ExportResult is one of: - Success - batch is successfully exported. For protocol exporters this typically means that the data is sent over the wire and delivered to the destination server. -- FailedNoneRetryable - exporting failed. The caller must not retry exporting the same batch. The batch must be dropped. This for example can happen when the batch contains bad data and cannot be serialized. +- FailedNotRetryable - exporting failed. The caller must not retry exporting the same batch. The batch must be dropped. This for example can happen when the batch contains bad data and cannot be serialized. - FailedRetryable - cannot export to the destination. The caller should record the error and may retry exporting the same batch after some time. This for example can happen when the destination is unavailable, there is a network error or endpoint does not exist. @@ -40,7 +40,7 @@ ExportResult is one of: Shuts down the exporter. Called when SDK is shut down. This is an opportunity for exporter to do any cleanup required. -`Shutdown` should be called only once for each `Exporter` instance. After the call to `Shutdown` subsequent calls to `Export` are not allowed and should return FailedNoneRetryable error. +`Shutdown` should be called only once for each `Exporter` instance. After the call to `Shutdown` subsequent calls to `Export` are not allowed and should return FailedNotRetryable error. `Shutdown` should not block indefinitely (e.g. if it attempts to flush the data and the destination is unavailable). Language library authors can decide if they want to make the shutdown timeout to be configurable.