HI Kishanthan,
Currently i have done some implementation on registry related data
deletion, removing solr indexes. But there are scenarios i have to consider
where deleting registry related data in mounted environment.
Thank you.
On Fri, Feb 27, 2015 at 10:00 AM, Kishanthan Thangarajah <
kishant
Hi Senaka,
We have an approach known as TenantMgtListener, where all the registered
listeners will get notified when a tenant is created or deleted. There are
methods (onPreDelete, onPostDelete, etc) that gets called by the tenant-mgt
core component during tenant deletion. So for all component spe
Hi Shashika,
So do you plan to create API methods on a per kernel component and per
product component basis? I would find that rather scattered and hard to
maintain. Though this looks justifiable from a kernel's point of view how
would you repeat the same at a component level? My thought was that
HI Senaka,
Main reason for putting this method inside the kernel is, because when
creating a tenant all the user management data addition resides inside the
kernel, and all the registry related data addition reside inside the. and
each data deletion methods also reside inside the kernel, so this i
Shashika,
Apart from whatever tool that you build (again for a specific tenant
administration purpose), who else will need to invoke this API method? My
feeling is that this method does not belong inside the registry kernel or
components. WDYT?
Thanks,
Senaka.
On Wed, Feb 25, 2015 at 3:18 AM, Sh
Hi Senaka/all
To do delete the DB related data one option is to add a new method to
registry api called deleteAllTenantData(or suitable one) so i have to
implement this method on every dependent registry classes, Is it ok to
introduce new method to registry api?
As i see when deleting a registry
Hi Shashika,
In solr indexing, we store the resource by its tenant_id
(indexed_document_id = resourcePath + "tenant" + tenantId)
e.g: Assume you stored resource from the tenant1, indexed document id looks
like below,
"id": "/_system/governance/services/aaa/aaa/1.0.0*tenantId1*"
You can get all
Hi Shashika,
I believe this is the only way to do this. There are several things to note
here.
1. In memory data - Ideally unloading the tenant should clean-up all of
this and if it does not there is an issue.
2. DB data - all the tables have a tenant-id column. What you need is a
query to delete
Hi,
Im in the process of deleting a tenant and all its related resources,so
what i came up with is to delete all the resources related to that tenant
using a direct DB call is there any other options to delete these data.
and if i to continue on the above approach what are the areas i have to
conc
