Connector Improvement: HVR: Include Object Type Added to HVR_Table allowing for better automation
AnsweredHi,
I was adding objects for replication to our hub and can see that the table explorer can identify the type of objects being replicated. See screenshot:



However, once we add these to the hub and they are included in the Repo DB hvr_table, there is no properties associated with the entry that retain this data. i.e. we can no longer tell what type of object is being replicated.
This would be a very useful piece of information to retain as it can influence the type of replication procedures / jobs being used, the type of actions that could be applied etc.
For example, we replicate both HANA tables and views. Sidenote: I know replicating views is never the priority, believe me I know we should be replicating the raw tables populating the view but this is not an option for us unfortunately so we are doing what we can to provide value to the "customer" on our end.
For replicating HANA tables we have a standard list of actions that apply and a different set of standard actions for when we are replicating views. If we could identify the type of object being replicated via any repo table that joins to the hvr_table we could automate this process and remove the current manual step that has to occur where a user adds the required standard list of actions to the channel.
To me, it seems like this could be an easy add on to the current table definitions seeing as HVR can already identify the type of object to be replicated by simply adding this data along with the inserted record to the HVR repo table.
Would be keen to know if there is already a way for us to do this as I can't find anywhere in the repo db tables that store the replicated object properties.
Thanks
-
Sorry James we have no plans to make these changes.
Mark.
Please sign in to leave a comment.
Comments
1 comment