Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
dcache-bulk: remove target error object and always convert to type + …
…message Motivation: While the BulkRequestTarget object has a Throwable error field, we do not store the error in serialized form in the database; rather, we store its type (canonical class name) and message; moreover, we always store the root exception metadata. However, when deserializing a processed target from the database fields, we have to reconstruct an error for the object field as a placeholder (as a Throwable with error type + message as message). This then leads to displays of target info with error type always `Throwable` and the type name embedded into the message. This is rather ugly and redundant. Modification: Eliminate the actual Throwable object field in the BulkRequestTarget object, and always store the type and message of the root exception directly. These are then simply pushed to the database and retrieved as such. Result: Economy and consistency of error metadata for bulk target information listings. I consider this a defect so I am suggesting back-port to 8.2 Target: master Request: 8.2 Patch: https://rb.dcache.org/r/13895/ Requires-notes: yes Acked-by: Tigran
- Loading branch information
Showing
12 changed files
with
105 additions
and
67 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
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
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
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
Oops, something went wrong.