You can translate the question and the replies:

Dfs custom wrapper deployment

Custom core-site.xml file: In the configuration on custom wrapper data source in development environment, the core-site.xml is created and stored in particular local location in the denodo server. When we do promotion of this data source from development to testing environment, will the core-site.xml created locally in the test environment server ? or we have to move it manually ?

2 Answers

Hi, When a revision is created in Solution Manager, the revision consists of the vql statements to update the data sources, views, etc into the promotion environment. Configuration properties like the path for "core-site.xml" are only stored as a variable name, and the environment that the revision will be promoted to needs to have the updated path for core-site.xml plus any other configurations properties that are needed. The Validate tool in Solution Manager will flag any missing variables in the promotion environment and you can either port the current values or add a new ones in the "Create Missing VQL Properties" dialog. But this is just for the path that the variable stores. Any changes to a file that the path points to are not saved by the revision, so those will need to be updated by another method. So this is a long way of saying: if you want to use the same core-site.xml, just update the revision to use the current path. Either use the revision validation tool or Solution Manager will make it obvious for you to do this, as the revision will fail on promotion if that path does not exist. But, if you want to use a core-site.xml that's on a different server or has different values, you'll have to update that file in a separate method from Solution Manager and then ensure that the path variable in your promotion enviroment is correct. Hope this helps!
Denodo Team
28-11-2022 14:17:16 -0500
I understand the path variable will be promoted to new environment when we do revision/deployment in solution manager, but the physical file should be copied manually to the new environment by creating new directory. example : Env 1: Custom core-site.xml file: Local filepath: /opt/denodo/platform/conf/core-site.xml This core-site.xml file resides in physical path of env 1 server. after promotion to env 2 Env 2: Custom core-site.xml file: Local filepath: /opt/denodo/platform/conf/core-site.xml This core-site.xml does not resides in physical path of env 2 server, We need to manually copy this from env1 to env 2; is that correct ?
29-11-2022 01:04:40 -0500
You must sign in to add an answer. If you do not have an account, you can register here