Graph Store

This entity represents a graph store that can be used to store and manage graph data. It included generated data or data copied using the entity copy task template.

A graph store is automatically created by executing one of the new microservice task templates.

Properties

The table below documents the available properties for graph stores. The 'name' column displays the property name as it can be used in Groovy and Java Scripts.

Name

Type

Default

Description

Executable

executable

Task

n/a

Specifies the task that is executed to populate the graph store.

Actions

The available actions are described below. Some actions apply to the list, while others are specific to selected graph stores.

List Actions

The following actions are available on the graph stores list. If the action is disabled a tooltip will provide the exact reason for the deactivation. The required permissions are described in detail for each action.

  • Bulk Delete

Delete the selected objects.

The following options are available:

Cascade

Recursively delete depending objects.

When using cascade, dependent objects are deleted first also with cascade enabled. Thus, a cascade deletion is a recursive function that deeply searches for dependent objects and deletes them first. There is only a confirmation for the first object. The dependent objects are deleted without confirmation but only when the user has the DELETE permission.

This feature is only available in development mode. More information about development mode can be found in the chapter User Settings. It should be used with caution.

An object in the result list can have two different states, these are:

DELETED

The object could be deleted.

NOT_DELETED

The object could be not deleted. This may be because the executing person does not have a delete permission on the object or the object is still referenced by others. A detailed reason can be determined with the help of the error message. If the object is still in use, these objects are also displayed.

The following permissions are required on the list:

  • DELETE

  • READ

Object Actions

The following actions are available on specific graph stores. In order to execute the action, the user must possess the necessary permissions for the object. The permissions required for each action are described individually. If the user does not have these permissions, the action will be disabled and the tooltip will provide the exact reason for the deactivation.

  • Delete

Delete the object. If the object is still used by another entity, an error message is displayed, and the object is not deleted. The delete operation must be confirmed in a separate popup.

The following options are available:

Cascade

Recursively delete depending objects.

When using cascade, dependent objects are deleted first also with cascade enabled. Thus, a cascade deletion is a recursive function that deeply searches for dependent objects and deletes them first. There is only a confirmation for the first object. The dependent objects are deleted without confirmation but only when the user has the DELETE permission.

This feature is only available in development mode. More information about development mode can be found in the chapter User Settings. It should be used with caution.

The following permissions are required:

  • DELETE

  • READ

License Options

This object is available if at least one of the following license options is enabled:

  • COMPONENT:DATA_GENERATION

  • DATABASE_TYPE:KAFKA

  • DATABASE_TYPE:WEBSERVICE