Schemas are supported only by Master Data V2.
JSON Schema is a tool with rules to validate the structure of JSON data. More information about JSON Schema can be found in the book Understanding JSON Schema. A Schema lets users configure the structure of a Data Entity.
This article explains how changes in a Schema affect the Data Entities, which actions are triggered in the background and the amount of inconsistency time until all configurations are completed. So, consider the lifecycle of a Schema below:
Each phase of the lifecycle will be split into 3 areas: saving data, searching and background process.
Master Data can work without any Schema created before documents are stored, but there are limitations to save and search documents.
|Saving data||You can store data without a Schema and the validation will affect only the |
|Searching||You can search and scan all the Documents you have stored, but there are limitations about filtering in the search. Since you don't have a Schema to configure which fields should be searchable, only internal fields are searchable (|
|Background process||No Schema means no triggers or custom fields searchable. So, there is nothing being processed in the background.|
You can create a Schema before or after sending documents to be persisted in Master Data. Schemas are created using the Schemas API. In case we already have documents in the database, a process is triggered in the background.
|Background process||When there already are documents in the database, the process will revalidate all documents. If the document is valid, the internal field |
The amount of time that takes to revalidate all documents will depend on the amount of documents and the amount of parallel changes that are being processed at the moment. A Data Entity with 1 million documents usually takes one hour, but could be more. Also, currently it is not possible to see the progress of the revalidation process.
|Saving data||Nothing has changed yet because you are not sending the |
By using the Schema query string, you avoid creating invalid Documents. After this change, documents will be validated during the request and a bad request (HTTP status code 400) will be returned by the API to invalid documents.
|Searching||After the Background Process, you can use the Search API using the custom fields as you want. You must also inform the |
Modifications in a Schema allows you to add or change properties, or enable more fields to be searchable.
|Background process||The process to modify a schema works the same as in the Schema creation.|
|Saving data||After a schema is modified, the database behavior changes when saving documents. The validation of new properties will be applied and documents could be rejected. Therefore, make sure you did the right configuration (you can rollback changes, if necessary).|
|Searching||While the Background Process is running, the Search becomes inconsistent until all documents in the Search Engine are updated.|
If you want to remove the Schema for any reason, you have to remove its usage.
|Background process||Nothing is processed in the background from the removal of a Schema.|
|Saving data||When saving data, make sure you are not using the removed Schema in the API or you will receive a bad request.|
|Searching||Just like when saving data, make sure you are not making a search with the removed Schema to avoid a bad request.|
Updated over 1 year ago