Snow Owl AP
GitHubNeed Help?
  • ℹ️Introduction
    • Snow Owl® AP Admin Guide
  • 🗺️Plan your deployment
    • Technology stack
    • Hardware requirements
    • Software requirements
  • 📤Configuration
    • Release package
    • Folder structure
    • Get SSL certificate (optional)
    • Preload dataset (optional)
    • Configure Elastic Cloud (optional)
    • Spin up the service
  • ↗️Software Upgrades
    • Perform an upgrade
  • 💾Backup and Restore
    • Backup
    • Restore
  • 📋Miscellaneous
    • User management
    • Install the client
Powered by GitBook
On this page
Export as PDF
  1. Configuration

Preload dataset (optional)

PreviousGet SSL certificate (optional)NextConfigure Elastic Cloud (optional)

Last updated 3 years ago

In certain cases, a pre-built dataset is also shipped together with the Authoring Platform. This is to ease the initial setup procedure and get going fast.

This method is only applicable to deployments where the Elasticsearch cluster is co-located with the Terminology Server.

To load data into a managed Elasticsearch cluster, there are several options:

  • use

  • use

  • use Snow Owl to rebuild the data to the remote cluster

These datasets are the compressed form of the Elasticsearch data folder which follows the same structure. Except for having a top folder called indexes . This is the same folder as in ./snow-owl/resources/indexes . So to be able to load the dataset one should just extract the contents of the dataset archive to this path.

tar --extract \
    --gzip \
    --verbose \
    --same-owner \
    --preserve-permissions \
    --file=snow-owl-resources.tar.gz \
    --directory=/opt/snow-owl/resources/

chown -R 1000:0 /opt/snow-owl/resources

Make sure to validate the file ownership of the indexes folder after decompression. Elasticsearch requires UID=1000 and GID=0 to be set for its data folder.

📤
cross-cluster replication
snapshot-restore