Profile data via Edge

Important 

In Collibra 2024.05, we launched a new user interface (UI) for Collibra Data Intelligence Platform! You can learn more about this latest UI in the UI overview.

Use the following options to see the documentation in the latest UI or in the previous, classic UI:

After you have configured the profiling options, you can start the profiling process for the schemas in the data source.

Important Advanced data types are not taken into account when profiling via Edge.

Tip Collibra Data Intelligence Platform only has access to synchronized metadata and profiling results, not to the actual data from your data source.

Before you begin

Required permissions

Steps

  1. Open the Database asset page of a registered database.
  2. In the tab panebar, click Configuration. In the tab panebar, click Configuration.
  3. Click the Profiling tab.
    The options open.

    Tip Only the synchronized schemas are available in the list.

    Important If you want to profile only one or more schemas, ensure the default profiling option is set to Do Not Profile (unless specified in the schema-specific rule, and that you only define a specific rule for the relevant schemas.
  4. On the Profiling tab page, click Run Profiling.
    Data Catalog triggers the Edge site to start a profiling job.
    Depending on your profiling options, the Edge site profiles all or some schemas and tables, based on all synchronized metadata or on a subset.
  1. Open the Database asset page of a registered database.
  2. In the tab panebar, click Configuration. In the tab panebar, click Configuration.
  3. Click the Profiling tab.
    The options open.

    Tip Only the synchronized schemas are available in the list.

  4. In the Default Rule section, click Edit.
  5. Select Automatically Profile after Metadata Synchronization.
  6. Synchronize one or more schemas.
    When the schemas are synchronized, Data Catalog automatically triggers the Edge site to start a profiling job.
    Depending on your profiling options, the Edge site profiles all or some schemas and tables, based on all synchronized metadata or on a subset.
  1. Open the Database asset page of a registered database.
  2. In the tab panebar, click Configuration. In the tab panebar, click Configuration.
  3. Click the Profiling tab.
    The options open.

    Tip Only the synchronized schemas are available in the list.

  4. In Synchronization Schedule, click Add Schedule to add a new schedule, or to edit an existing schedule.
    The Edit Schedule dialog box appears.
  5. Enter the required information.
    FieldDescription
    RepeatThe interval when you want to synchronize automatically. The possible values are: Daily, Weekly, Monthly, and Cron expression.
    Cron

    The Quartz Cron expression that determines when the synchronization takes place.

    This field is only visible if you select Cron expression in the Repeat field.

    Every

    The day on which you want to synchronize, for example, Sunday.

    This field is only visible if you select Weekly in the Repeat field.

    Every first

    The day of the month on which you want to synchronize, for example, Tuesday.

    This field is only visible if you select Monthly in the Repeat field.

    At

    The time at which you want to synchronize automatically, for example, 14:00.

    • You can only schedule on the hour. For example, you can add a synchronization schedule at 8:00, but not at 8:45.
    • This field is only visible if you select Daily, Weekly, or Monthly in the Repeat field.
    Time zoneThe time zone for the schedule.
  6. Click Save.
    The profiling job starts according to the schedule.
    Depending on your profiling options, the Edge site profiles all or some schemas and tables, based on all synchronized metadata or on a subset.

What's next?

The Edge site completes the profiling process and sends the results to Collibra Data Intelligence Platform.

  • You can see the profiling job in the list of activities.
    When the activity is completed, the results page gives an overview of the profiled data.
    If something goes wrong, the job is reported as failed. By default, the capability will try to collect the data, calculate the statistics, and send the results two times with each attempt taking 30 minutes. You can change this in the capability configuration.
  • You can find the profiling results and charts in the Table and Column asset pages.

    Note Columns mapped to following java.sql.Types are excluded from the profiling queries: ARRAY, BINARY, BLOB, CLOB, DATALINK, DISTINCT, JAVA_OBJECT, LONGVARBINARY, NCLOB, NULL, OTHER, REF, REF_CURSOR, ROWID, SQLXML, STRUCT, VARBINARY.

  • In the Configuration tab page of the Database asset, if a schema is profiled, you see a check symbol next to the schema name. If the profiling of a schema failed, an exclamation mark is shown.

Note The Unified Data Classification process does not automatically run at the same time as profiling. You need to activate the classification process separately.