Object size

Build 1501 on 14/Nov/2017  This topic last edited on: 21/Mar/2016, at 18:35

It is possible to define up to three separate 'sizes' for each object type.
 
A size is a numeric object attribute (int, short, long, float, double, decimal, etc.) that is marked as such by using the Tera-specific extra attribute,  gs:size, in the schema definition.
 
The three possible sizes are 'Main', 'Aux' and 'Extra'. These are three 'labels' that can be used freely to identify different sizes of an object. Usually there will be only one size - use 'Main' for it.
 
Typically, a size object attribute will be an automatically computed attribute that computes some sort of reasonable size for the object it belongs to, e.g., the size of one or more binary data attributes, the total length of certain string attributes etc.

<xs:attribute name="size" type="tNonNegativeLong" gs:compute="true" gs:size="Main" gs:dimension="datasize:byte">

  <xs:annotation>

    <xs:appinfo>

      <gs:ui mode="Hidden"/>

    </xs:appinfo>

    <xs:documentation>Object 'main' size: the size in bytes of the image data</xs:documentation>

  </xs:annotation>

</xs:attribute>

 

Relation between object size and quota

There is a fixed relationship between the object size attributes and the quota applied to the partition the object belongs to. That is, object attributes with a size defined as "Main" are relevant to the computation of the quota attribute "MaxSize" and MaxTotalSize, which define the maximum size (in MB) of individual objects in a partition, and the total size of all objects in a partition. Similarly, object attributes with a size specified as "Aux" are used to check the quota attribute "MaxAuxSize" and "MaxTotalAuxSize".

See also

Defining a size attribute

Quota and partitions