# Notification for nested subscription

**URL:** <https://dmap-community.ductus.global/t/notification-for-nested-subscription/1179>\
**Category:** CDB and CDB API\
**Created:** [April 24, 2017, 9:57am UTC](https://dmap-community.ductus.global/t/notification-for-nested-subscription/1179 "2017-04-24T09:57:16Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![sudhanshu](https://avatars.discourse-cdn.com/v4/letter/s/6bbea6/32.png) [@sudhanshu](https://dmap-community.ductus.global/u/sudhanshu)\
**Post date:** [April 24, 2017, 9:57am UTC](https://dmap-community.ductus.global/t/notification-for-nested-subscription/1179/1 "2017-04-24T09:57:16Z")

</div>

I have defined a data like -

```
	|	|G1
	|B |G2
	|___|
	|	|H1
A	|C	|H2
        |___| 
        |D	
	|E	
	|F	

```

And i have done subscription at A/B and A. What i see if I change G1, I get two notifications. shouldnt i get only 1 notification. ConfD shouldn’t suppress one notification ?

---

<div class="post-metadata">

**Author:** ![cohult](https://yyz2.discourse-cdn.com/flex010/user_avatar/dmap-community.ductus.global/cohult/32/221_2.png) [@cohult](https://dmap-community.ductus.global/u/cohult)\
**Post date:** [April 25, 2017, 8:50am UTC](https://dmap-community.ductus.global/t/notification-for-nested-subscription/1179/2 "2017-04-25T08:50:43Z")

</div>

Hi,

As you can see in the /examples.confd/cdb\_subscription/trigger/cdb\_client\_B.c example, two notifications can be desirable in many use-cases.

Side note: You can use the pyang tool to print a tree structure of a YANG model.

```
$ pwd
/Users/tailf/confd-6.3/examples.confd/cdb_subscription/trigger
$ pyang -f tree example.yang

```

```auto
module: example
   +--rw sys
      +--rw ifc* [name]
         +--rw name interfaceName
         +--rw description? string
         +--rw enabled? boolean
         +--rw hw
         | +--rw speed? interfaceSpeed
         | +--rw duplex? interfaceDuplex
         | +--rw mtu? mtuSize
         | +--rw mac? string
         +--rw ip* [address]
            +--rw address inet:ipv4-address
            +--rw prefix-length prefixLengthIPv4
            +--rw broadcast? inet:ipv4-address

```