LU tables are the basic building blocks for creating Logical Units and their Schemas. Their purpose is to hold data retrieved from various sources after it has been transformed according to a project’s requirements.
An LU table can also act as the Master of Data that holds the data generated in Fabric and is not synced by source systems.
Click for more information about how to add an LU Table to an LU Schema.
LU tables can be created either automatically, for example, using the Auto Discovery Wizard or manually. When building a table, first define the table's properties, columns and indexes and then create the Table Population map which holds the transformation and mapping rules.
Creating a population for an LU table is optional. When a table acts as the Master of Data, it does not get feeds from source systems and the Table Population is redundant.
An LU table window has the following tabs:
The following LU tables are generated by the product automatically and are not displayed in the LU Schema window:
_k2_main_info, which stores the last deployed LU version and the last sync time.
Field Name |
Description |
lu_name |
Logical Unit name |
version |
Version of the last deployed LU |
instance_id |
Instance Id |
version_timestamp |
Timestamp of the LU instance's last sync |
_k2_objects_info, which stores LU instance statistics on an object population or enrichment function level.
LU tables are the basic building blocks for creating Logical Units and their Schemas. Their purpose is to hold data retrieved from various sources after it has been transformed according to a project’s requirements.
An LU table can also act as the Master of Data that holds the data generated in Fabric and is not synced by source systems.
Click for more information about how to add an LU Table to an LU Schema.
LU tables can be created either automatically, for example, using the Auto Discovery Wizard or manually. When building a table, first define the table's properties, columns and indexes and then create the Table Population map which holds the transformation and mapping rules.
Creating a population for an LU table is optional. When a table acts as the Master of Data, it does not get feeds from source systems and the Table Population is redundant.
An LU table window has the following tabs:
The following LU tables are generated by the product automatically and are not displayed in the LU Schema window:
_k2_main_info, which stores the last deployed LU version and the last sync time.
Field Name |
Description |
lu_name |
Logical Unit name |
version |
Version of the last deployed LU |
instance_id |
Instance Id |
version_timestamp |
Timestamp of the LU instance's last sync |
_k2_objects_info, which stores LU instance statistics on an object population or enrichment function level.