Uploading data to dataspaces

When you import data from an Excel or CSV file into a new Elasticsearch index, the following indexing options are available:

  • Global: Segmented: Creates a shared index in which the documents are partitioned by dataspace. When a configuration with this scope is saved as an import template, the users that are allowed to view the template will be able to import CSV files that have the same columns as the template. The imported data will then be tagged with the currently-active dataspace and will be visible only to users that have access to it. This kind of scope is useful to allow the import of data in a common format into isolated dataspaces while limiting the number of indices in Elasticsearch.

  • Global: Non-segmented: Creates a shared index in which the documents are not partitioned. When a configuration with this scope is saved as an import template, the users that are allowed to view the template will be able to import CSV files that have the same columns as the template. The imported data will be visible from all of the dataspaces. This kind of scope is useful to allow the import of data in a common format that can be used in any dataspace.

  • Local: Creates an index in which the documents are associated to the current dataspace. When a configuration with this scope is saved as an import template, all of the users that have access to the dataspace will be able to import CSV files that have the same columns as the template. The imported data will be visible only from the current dataspace.

  • None: Creates an arbitrary Elasticsearch index by using the current user credentials. When a configuration with this scope is saved as an import template, all of the users that are allowed to view the template will be able to import additional data only if their Elasticsearch roles grant write permission to the index.

image

Global scopes can be selected only by users which have the ACL permission to create import templates in the default dataspace (HOME).