[IMGREC-13] Handle Exceptions gracefully in ImageRecognitionService Created: 23/Aug/18 Updated: 23/Oct/18 Resolved: 22/Oct/18 |
|
| Status: | Closed |
| Project: | Image Recognition |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 1.0 |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Ilgun Ilgun | Assignee: | Federico Grilli |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Date of First Response: | |
| Epic Link: | Periscope back-end MVP |
| Sprint: | Basel 158 |
| Story Points: | 2 |
| Description |
|
Currently we submit image recognition tasks to dedicated executorService under info.magnolia.ai.image.ImageRecognitionService. However, should there be any exceptions in ImageRecognisers, those would not be visible by the users simply because we don't log them nor handle them gracefully. Perhaps even the threads are killed by the exceptions. |