Edit Schema Project Connection

1. Navigate to the Project Overview tab.

2. Click Edit Connection.

3. Use the Connection Information modal to make any necessary changes.

4. Click Save.

Edit Schema Monitoring Naming Convention

1. Navigate to the Project Overview tab.

2. Click Edit Schema Monitoring.

3. Use the Basic Information modal to make any necessary changes to naming formats.

4. Click Save.

Add New Schema Detection Owner

1. Navigate to the Project Overview tab.

2. Click Edit Schema Monitoring.

3. Use the dropdown menu in the Schema Monitoring modal to select a new schema detection owner. The new owner must be an owner of one or more of the data sources belonging to that schema.

4. Click Save.

Change the Frequency of Schema Monitoring Jobs

1. Navigate to the App Settings page and scroll down to the Advanced Configuration.

2. Copy and paste this YAML into the text box:

   Copy

   schedule:
     schemaEvolutionCheck: 'your-new-frequency'

   Replace your-new-frequency with the time you would like between schema jobs. For example use */30 * * * * for the queries to run every 30 minutes.

3. Click Save.

Change the Frequency of Column Detection Jobs

1. Navigate to the App Settings page and scroll down to the Advanced Configuration.

2. Copy and paste this YAML into the text box:

   Copy

   schedule:
     columnEvolutionCheck: 'your-new-frequency'

   Replace your-new-frequency with the time you would like between column detection jobs. For example use */30 * * * * for the queries to run every 30 minutes.

3. Click Save.

Manually Run Schema Monitoring Jobs

Manually Run Schema Monitoring Job for All Data Sources

Prerequisite: Immuta permission: USER_ADMIN

You can manually run a schema monitoring job globally using the /dataSource/detectRemoteChanges endpoint of the Immuta API with an empty payload.

Manually Run Schema Monitoring Job as a Data Owner

You can manually run a schema monitoring job for all data sources that you own using the /dataSource/detectRemoteChanges endpoint of the Immuta API with a payload containing the hostname for your data sources or their individual IDs.

Manually Run Schema Monitoring Job as a Data User

You can manually run a schema monitoring job for data sources you are subscribed to using the /dataSource/detectRemoteChanges endpoint of the Immuta API with a payload containing the hostname for your data source and the table name or data source ID.

Manually Run a Column Detection Job

1. Navigate to the data source overview page.

2. Click on the health check icon.

3. Scroll to Column Detection, and click Trigger Detection.