Generate logical data model (LDM) from physical data model (PDM)
Generate logical data model (LDM) from physical data model (PDM) stored in data source.
path Parameters
dataSourceIdstring · required
Request Body
aggregatedFactPrefixstringColumns starting with this prefix will be considered as aggregated facts. The prefix is then followed by the value of
separatorparameter. Given the aggregated fact prefix isaggrand separator is__, the columns with name likeaggr__sum__product__soldwill be considered as aggregated sold fact in the product table with SUM aggregate function.Example: aggrdateGranularitiesstringOption to control date granularities for date datasets. Empty value enables common date granularities (DAY, WEEK, MONTH, QUARTER, YEAR). Default value is
allwhich enables all available date granularities, including time granularities (like hours, minutes).Example: alldateReferencePrefixstringColumns starting with this prefix will be considered as references to date dataset. The prefix is then followed by the value of
separatorparameter. Given the reference prefix isdand separator is__, the columns with name liked__datewill be considered as reference to date dataset. There can be also second separator and granularity suffix, e.g.d__date__dayto create attribute reference to exact date dataset and granularity.Example: ddenormPrefixstringColumns starting with this prefix will be considered as denormalization references. The prefix is then followed by the value of
separatorparameter. Given the denormalization reference prefix isdrand separator is__, the columns with name likedr__customer_namewill be considered as denormalization references.Example: drfactPrefixstringColumns starting with this prefix will be considered as facts. The prefix is then followed by the value of
separatorparameter. Given the fact prefix isfand separator is__, the columns with name likef__soldwill be considered as facts.Example: fgenerateLongIdsbooleanA flag dictating how the attribute, fact and label ids are generated. By default their ids are derived only from the column name, unless there would be a conflict (e.g. category coming from two different tables). In that case a long id format of
<table>.<column>is used. If the flag is set to true, then all ids will be generated in the long form.Default: falsegrainMultivalueReferencePrefixstringColumns starting with this prefix will be considered as grain multivalue references. The prefix is then followed by the value of
separatorparameter. Given the reference prefix isgrmrand separator is__, the columns with name likegrmr__customer__customer_idwill be considered as grain multivalue references to customer_id in customer table.Example: grmrgrainPrefixstringColumns starting with this prefix will be considered as grains. The prefix is then followed by the value of
separatorparameter. Given the grain prefix isgrand separator is__, the columns with name likegr__namewill be considered as grains.Example: grgrainReferencePrefixstringColumns starting with this prefix will be considered as grain references. The prefix is then followed by the value of
separatorparameter. For composite references, the reference is multivalue if at least one column is multivalue. Given the reference prefix isgrrand separator is__, the columns with name likegrr__customer__customer_idwill be considered as grain references to customer_id in customer table.Example: grrmultivalueReferencePrefixstringColumns starting with this prefix will be considered as multivalue references. The prefix is then followed by the value of
separatorparameter. For composite references, the reference is multivalue if at least one column is multivalue. Given the reference prefix ismrand separator is__, the columns with name likemr__customer__customer_idwill be considered as multivalue references to customer_id in customer table.Example: mrpdmobjectPDM additions wrapper.
primaryLabelPrefixstringColumns starting with this prefix will be considered as primary labels. The prefix is then followed by the value of
separatorparameter. Given the primary label prefix ispland separator is__, the columns with name likepl__country_idwill be considered as primary labels.Example: plreferencePrefixstringColumns starting with this prefix will be considered as references. The prefix is then followed by the value of
separatorparameter. Given the reference prefix isrand separator is__, the columns with name liker__customer__customer_idwill be considered as references to customer_id in customer table.Example: rsecondaryLabelPrefixstringColumns starting with this prefix will be considered as secondary labels. The prefix is then followed by the value of
separatorparameter. Given the secondary label prefix islsand separator is__, the columns with name likels__country_id__country_namewill be considered as secondary labels.Example: lsseparatorstringA separator between prefixes and the names. Default is "__".
Default: __translationPrefixstringColumns starting with this prefix will be considered as secondary label translation. The prefix is then followed by the value of
separatorparameter. Given the translation prefix istrand separator is__, the columns with name liketr__attribute__label__en-USwill be considered as secondary label en-US translation tolabellabel inattributeattribute.Example: trwdfPrefixstringColumn serving as workspace data filter. No labels are auto generated for such columns.
Default: wdfworkspaceIdstringOptional workspace id.
tablePrefixstring · deprecated · requiredTables starting with this prefix will be included. The prefix is then followed by the value of
separatorparameter. Given the table prefix isout_tableand separator is__, the table with name likeout_table__customerswill be scanned.Example: out_tableviewPrefixstring · deprecated · requiredViews starting with this prefix will be included. The prefix is then followed by the value of
separatorparameter. Given the view prefix isout_viewand separator is__, the table with name likeout_view__us_customerswill be scanned.Example: out_view
Responses
LDM generated successfully.
ldmobjectA logical data model (LDM) representation.