Currently Inventory uses the full exception as the message returned by Job.setStatus.
Because inventory exceptions have not been standardized in the past, it would be useful to provide a mechanism for providing a mapping of all frequent exceptions to a standard message returned in Job.setStatus(...).
The approach should allow this mapping through an easily maintained yaml file as part of initialization.
To do this correctly will require some time for design and implementation that will extend beyond the current release of the Ingest-inventory Job / zookeeper release planned ~10/11.
This Issue is to allow this scheduling within the timeframe for this release.
Currently Inventory uses the full exception as the message returned by Job.setStatus.
Because inventory exceptions have not been standardized in the past, it would be useful to provide a mechanism for providing a mapping of all frequent exceptions to a standard message returned in Job.setStatus(...).
The approach should allow this mapping through an easily maintained yaml file as part of initialization.
To do this correctly will require some time for design and implementation that will extend beyond the current release of the Ingest-inventory Job / zookeeper release planned ~10/11.
This Issue is to allow this scheduling within the timeframe for this release.