Examples of UIDMeta

• net.opentsdb.meta.UIDMeta
  UIDMeta objects are associated with the UniqueId of metrics, tag names or tag values. When a new metric, tagk or tagv is generated, a UIDMeta object will also be written to storage with only the uid, type and name filled out.

  Users are allowed to edit the following fields:

  • display_name
  • description
  • notes
  • custom

  The {@code name}, {@code uid}, {@code type} and {@code created} fields can only be modified by the system and are usually done so on object creation.

  When you call {@link #syncToStorage} on this object, it will verify that theUID object this meta data is linked with still exists. Then it will fetch the existing data and copy changes, overwriting the user fields if specific (e.g. via a PUT command). If overwriting is not called for (e.g. a POST was issued), then only the fields provided by the user will be saved, preserving all of the other fields in storage. Hence the need for the {@code changed} hash map and the {@link #syncMeta} method.

  Note that the HBase specific storage code will be removed once we have a DAL @since 2.0

Examples of net.opentsdb.meta.UIDMeta

Examples of net.opentsdb.meta.UIDMeta