LU Tables Overview

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.

LU Table Structure

An LU table window has the following tabs:

  • Table Columns, holding a list of columns and their definitions.
  • Table Indexes, holding a list of indexes which are added to an LU table to improve the selection process. Each LU table can have several indexes where each index can contain several columns.
  • Search, holding a list of fields available for a cross-instance search.
  • CDC Topic, holding a list of fields to be published to an external system (CDC topic) using the CDC mechanism.
  • Table Properties, where the table’s properties like the Primary Key, Sync Method or related Enrichment functions are defined.

Built-in Product LU Tables

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.

Field Name

Description

table_name

LU table name

object_name

Object name, population name or enrichment function name

type

Object type: 6 - population, 10 - enrichment function

verified_time

Last time of verification as to whether the object should be synced or not

start_sync_time

Object's last sync start time

end_sync_time

Object's last sync end time

start_write_time

Start time of the last write LU instance into the SQLite file

last_write_time

End time of the last write LU instance into the SQLite file

number_of_records

Number of processed records

time_to_populate_in_sec

Total time in seconds to run the object

next_time_to_populate_object

Next time the object should be synced

version

The Version Id of the last object's sync

sync_error

Object's sync error message in case of failure

LU Tables Overview

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.

LU Table Structure

An LU table window has the following tabs:

  • Table Columns, holding a list of columns and their definitions.
  • Table Indexes, holding a list of indexes which are added to an LU table to improve the selection process. Each LU table can have several indexes where each index can contain several columns.
  • Search, holding a list of fields available for a cross-instance search.
  • CDC Topic, holding a list of fields to be published to an external system (CDC topic) using the CDC mechanism.
  • Table Properties, where the table’s properties like the Primary Key, Sync Method or related Enrichment functions are defined.

Built-in Product LU Tables

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.

Field Name

Description

table_name

LU table name

object_name

Object name, population name or enrichment function name

type

Object type: 6 - population, 10 - enrichment function

verified_time

Last time of verification as to whether the object should be synced or not

start_sync_time

Object's last sync start time

end_sync_time

Object's last sync end time

start_write_time

Start time of the last write LU instance into the SQLite file

last_write_time

End time of the last write LU instance into the SQLite file

number_of_records

Number of processed records

time_to_populate_in_sec

Total time in seconds to run the object

next_time_to_populate_object

Next time the object should be synced

version

The Version Id of the last object's sync

sync_error

Object's sync error message in case of failure