[IMGREC-57] Allow users to re-initialise ImageRecognisers Created: 24/May/19  Updated: 09/Aug/19  Resolved: 25/Jul/19

Status: Closed
Project: Image Recognition
Component/s: None
Affects Version/s: None
Fix Version/s: 1.1

Type: Improvement Priority: Neutral
Reporter: Ilgun Ilgun Assignee: Nguyen Phung Chi
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 0d
Time Spent: 8d 3.5h
Original Estimate: Not Specified

Issue Links:
Cloners
is cloned by IMGREC-69 Migration test will take into account... Closed
Relates
relates to IMGREC-64 WorkspaceEventListener are not regist... Closed
dependency
is depended upon by IMGREC-60 Only assets in Tours are tagged Closed
is depended upon by IMGREC-62 Fix migration diffs Closed
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)
Documentation update required:
Yes
Date of First Response:
Epic Link: Image Rec
Sprint: Add-Ons 15, Add-Ons 16
Story Points: 8

 Description   

Before we used to use observed component mechanism but due to its limited functionality we had to remove that. Currently we allow users to configure one versus the other image recogniser by dropping various jars to their bundles. However, there should be a simpler mechanism to handle this, even if not there must be functionality to trigger re-initialisation of image recognisers. E.g. when AWS passwords changed, user ideally doesn't need to restart.



 Comments   
Comment by Julie Legendre [ 25/Jul/19 ]

Perfect, thanks!

Generated at Mon Feb 12 02:09:07 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.