I am very new to Ataccama and still exploring everything by myself. I have updated logical model (added new entities), load operation and then configured transformations. Saved and generated the project. But I cannot see the new entities in Postgresql. I was under assumptions that after generating the logical model, tables will be created automatically in postgre but that didn’t happen. Tried saving, generating, stopping and starting servers several time but no luck.
Is there any steps to follow?
Thanks
FS
Best answer by AKislyakov
MDM Server automatically adds new columns (and alters existing ones in some cases), but it leaves deleted columns intact.
Here is the parameter that controls database alteration level:
nme.vldb.alterTableLevel
addColumns,alterColumnsAlter
Defines what alter table commands will be executed if a table in database does not match the model. This is list of permitted values:
addColumns. Add missing columns.
alterColumnsAlter. Alter existing columns that can be altered by DB DDL command, only extending varchar size and on some databases altering to clob is supported, that is, it won’t change from small to large numbers (INTEGER → LONG). If database does not support alteration via DDL command, warning is written into log.
Unless you're starting your mdm-server in Read-Only mode (nme.vldb.readonly=true), it should create missing tables upon startup. In the mdm-server startup logs, there should be messages like "Starting plan..." for transformations related to your new entities. If you see such messages and the server starts up successfully, then the tables should be in place. If you don’t see them, then probably mdm-server doesn’t see your changes / uses some other configuration.
Thank You @AKislyakov . Today all the new entities were showing up in postgres but found another issue. Due to model changes I had deleted few columns from existing entities but those are still showing up in postgres tables. Is there anyway to delete them?
MDM Server automatically adds new columns (and alters existing ones in some cases), but it leaves deleted columns intact.
Here is the parameter that controls database alteration level:
nme.vldb.alterTableLevel
addColumns,alterColumnsAlter
Defines what alter table commands will be executed if a table in database does not match the model. This is list of permitted values:
addColumns. Add missing columns.
alterColumnsAlter. Alter existing columns that can be altered by DB DDL command, only extending varchar size and on some databases altering to clob is supported, that is, it won’t change from small to large numbers (INTEGER → LONG). If database does not support alteration via DDL command, warning is written into log.
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.
