All data that is delivered by simple rest endpoints is indexed in elasticsearch indices. Queries and data delivery takes place directly out of the elasticsearch (not from Pimcore database).
For each Datahub configuration separate elasticsearch indices will be created and updated.
Indexing of data takes places asynchronously with an update queue and the process queue command
datahub:simple-rest:process-queue. This command needs to be executed on a regular base, e.g.
every 5 minutes.
Index mapping and queue filling takes place automatically when creating and updating Datahub
configurations. In addition, also commands for index management are available
Per endpoint, multiple indices are created - one for each dataobject class, one for dataobject folders, one for assets and one for asset folders.
Tree Hierarchy Management The indexing process tries to keep a valid folder structure in index. Based on workspace settings a combined parent folder is calculated. This combined parent folder, might be a sub folder of the parent folder in Pimcore folder structure, and all element paths are rewritten to it.
Also it might be possible, that due to workspace and data schema settings, missing links in folder structure occur. In this case, the indexing process creates virtual folders to fill up these gaps.
For updating whole index structure after changes, multiple runs of
be necessary (since additional items might be added to queue during queue processing).