Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents

References

Jira Legacy
serverSystem Jira
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolutioncolumnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyCPS-2022

Issues & Decisions

...

#

...

Issue

...

Notes

...

Decisions

...

Overview

This is internal page intended for the collaboration between the team to decide how the Subscription will be present in memory.

Proposed Structure  

The structure is similar to the incoming subscription request from the Client.

true
Code Block
linenumbers
Map < Unique Subscription Id , Map < Dmi-Plugin Name , CmSubscriptionCompositeObject > >

CmSubscriptionCompositeObject
	CmSubscriptionPredicate list
	 - targetFilter : (List of cmHandles - Subscription request incoming cmhandles grouped using target dmiPlugin)
	 - Status ( Accepted , Rejected or Pending ) - initially Pending
	 - scopeFilter : 
			Datastore ( passthrough-operational and passthrough-running )
 - 			List of xpaths 

Example

Code Block
{"subscription123" , 
   { "dmi-1" : { "cmSubscriptionPredicates" : [
        “targetFilter” :  list of cmhandles, // mandatory
        "scopeFilter"  :  {
           "datastore": “ncmp-datastore:passthrough-operational or ncmp-datastore:passthrough-running", // optional. default is passthrough-operational
           "xpath-filter": list of valid xpaths  // mandatory
        }
],
        "status" : "ACCEPTED/REJECTED/PENDING"
    } 
  }
}

...