[MGNLPER-62] QuerySnifferProcessor is not aware of QuerySnifferDefinitionRegistry changes Created: 02/Nov/18  Updated: 09/Nov/18  Resolved: 05/Nov/18

Status: Closed
Project: Periscope
Component/s: None
Affects Version/s: None
Fix Version/s: 1.0

Type: Bug Priority: Neutral
Reporter: Ilgun Ilgun Assignee: Ilgun Ilgun
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)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Documentation update required:
Yes
Epic Link: Periscope back-end MVP
Sprint: Basel 159
Story Points: 2

 Description   

Currently, when user defines a new sniffer (command, operation) within Periscope, this won't be picked up unless server restarts. However, we have the capability to handle this case in the runtime.

 

 

Acceptance Criteria:

  • When user defines a new sniffer, our system should be aware of this.

Generated at Mon Feb 12 10:28:21 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.