Manage / Update Schemas from a Data Store

While the previous page walked through how to create new schemas from a Data Store, this page walks though how to manage existing schemas from the Data Store. When you do batch schema management from the Data Store you are able to:

  1. Deprecate old schemas that no longer exist in your Data Store

  2. Check for new fields and sample values to all of the Schemas within the Data Store and to automatically update your Data Catalog with any changes that exist in the Data Store


For more details on defining a schema read through the Schema Definition page!

Get Schema Updates

Select Manage Existing Schemas from the Data Stores detail page:


Since we do not access your Data Store unless you explicitly tell us to we present a prompt asking you to confirm; depending on the type of Data Store and number of schemas it may take some time for us to generate all of the schemas.


Selecting Get Schema Updates trigger the execution to retrieve your schemas.

Manage Schema Update Results


The results in this table consist of two lists:

  1. Existing Schemas: those that you already have in Tree Schema

  2. Deprecated Schemas: those that are currently active in Tree Schema but no longer exist in your underlying Data Store

In addition, the similar options exist for managing schemas that exist for adding schemas:

  1. Update Schema: All selected rows will have the schema status updated, this is primarily used to mark old schemas as deprecated if they no longer exist

  2. Update Fields: For each row selected, Tree Schema will poll your Data Store to get the full set of fields for the associated schema, as well as up to 20 sample values for each field. Tree Schema will add new fields, mark removed fields as deprecated, and add new sample values where applicable.

Confirmation of Schema Updates

When you select submit you will be presented with a summary of the updates. Similar to the add schemas from data store walkthrough, the process of adding and updating fields from each schema may time some time depending on the number of schemas that you have so that process runs in the background.