Entity types and states

Entity types and states

Overview

You can find here a list of possible types and the different states of an entity.

Types

An entity can be of one of the following types:

Type

Value

FILE

1

PROJECT

2

CUSTOMER

3

PORTAL

4

MANUFACTURER

5

States

States are grouped together in ranges, depending on the type of operation.

Type

Range

Scheduling operations

0-9

Fetching operations

10-19

Draining operations

20-29

Deleting operations

30-39

Error states

90-99

The following states have been defined so far:

State

Value

Comment

State

Value

Comment

NEW

0

Entity has been created by the API

SCHEDULED

1

The schedule worker went over this entry and marked it for the fetch worker

IS_FETCHING

10

The entity is being downloaded

FETCHED

11

The entity has been downloaded; the corresponding storage entity has been created

TO_BE_COPIED

12

The storageEntity should be copied from another storageEntity

IS_COPYING

13

The storageEntity is actual copied from another storageEntity

TO_BE_MOVED

20

The storageEntity has been marked for draining

IS_MOVING

21

The storageEntity is currently draining to another storage

MOVED

22

The storageEntity has been drained

IS_DELETING

30

The entity is currently being deleted

IS_DELETING_BINARY

31

The actual binary file is currently being deleted from a storage  - only the binary-file, not the entry in the database

DELETED_BINARY

32

The actual binary file was deleted from a storage

TO_BE_DELETED

33

The entity is scheduled to be deleted

TO_BE_DELETED_BINARY

34

The binary file of the entity is scheduled to be deleted

CANCELLED

80

This entity has been cancelled

FETCHED_ERROR

90

An error has occured while trying to fetch an entity

DELETING_ERROR

91

An error has occured while deleting an entity or file

MOVING_ERROR

92

An error has occured while moving a file between storages

FETCHED_NO_SPACE_ERROR

93

There was no space left when the fetch-worker tried to download the entity

FATAL_FETCHED_ERROR

94

The fetch-worker tried already "fetchtries"-times to download the entity, or there was a severe problem when downloading the entity ( e.g. file not found)