Partition Annotation

Partitioning is as easy as defining an index. Like an index a partition is determined by a specific field. There can only be one partition-able field within an Entity.

  1. Defining a partition

    The partition annotation must be accompanied by an @Attribute annotation.

    A partition field can be auto generated using a Lifecycle Event
    You can update the partition field on an entity. By doing so, it will delete the old entity, and persist a new one. It will also re-map all relationships to the new entity.
    For each partition, a new data file will be created to store the partitioned data.
    The amount of partitions per entity are limited only by the quantity of open files you operating system supports.
    There is no formal limit of amount of records per partition.
  2. Relationships