-
Notifications
You must be signed in to change notification settings - Fork 22
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #319 from IBM/Readme-Changes
move transform exceptions doc out of ray runtime to overview
- Loading branch information
Showing
3 changed files
with
19 additions
and
17 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,17 @@ | ||
# Exceptions | ||
A transform may find that it needs to signal error conditions. | ||
For example, if a referenced model could not be loaded or | ||
a given input data (e.g., pyarrow Table) does not have the expected format (.e.g, columns). | ||
In general, it should identify such conditions by raising an exception. | ||
With this in mind, there are two types of exceptions: | ||
|
||
1. Those that would not allow any data to be processed (e.g. model loading problem). | ||
2. Those that would not allow a specific datum to be processed (e.g. missing column). | ||
|
||
In the first situation the transform should throw an exception from the initializer, which | ||
will cause the runtime to terminate processing of all data. | ||
In the second situation (identified in the `transform()` or `flush()` methods), the transform | ||
should throw an exception from the associated method. | ||
This will cause only the error-causing datum to be ignored and not written out, | ||
but allow continued processing of tables by the transform. | ||
In both cases, the runtime will log the exception as an error. |