TRY ME

Try Valo for free

We want to show you something amazing.

We'll send you a link to download a fully functional Valo copy to play with.



Great! Check your email and enjoy Valo



Apologies, we seem to be having a problem processing your input, please try again

Data Types

The list below contains the data types that can appear in a stream’s schema.

Type Description
boolean A boolean.
byte A signed 8 bit integer.
short A signed 16 bit integer.
int A signed 32 bit integer.
long A signed 64 bit integer.
double A double precision floating point.
date A date.
time A time.
datetime A date time.
duration A duration.
string A string.
contributor A contributor id.
uuid A UUID.
ip An IPv4 or IPv6 address.
email An email address.
uri A URI.
geoPoint A geographic point.
geoCircle A geographic circle.
geoRectangle A geographic rectangle.
tags A field containing tags.
record A record.
array An array.

Boolean

A boolean value - i.e. true or false.

A field is specified to be of type “boolean” using this schema:

{ "type" : "boolean" }

Values written to a boolean field must be in one of the supported boolean formats.

Byte

A signed 8 bit integer in the range -128 to 127 (inclusive).

A field is specified to be of type byte using this schema:

{ "type" : "byte" }

Values written to a byte field must be in one of the supported natural number formats.

Short

A signed 16 bit integer in the range -32,768 to 32,767 (inclusive).

A field is specified to be of type short using this schema:

{ "type" : "short" }

Values written to a short field must be in one of the supported natural number formats.

Int

A signed 32 bit integer in the range -2,147,483,648 to 2,147,483,647 (inclusive).

A field is specified to be of type int using this schema:

{ "type" : "int" }

Values written to an int field must be in one of the supported natural number formats.

Long

A signed 64 bit integer in the range -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807.

A field is specified to be of type long using this schema:

{ "type" : "long" }

Values written to a long field must be in one of the supported natural number formats.

Double

A 64 bit double precision (IEEE 754) floating point.

A field is specified to be of type double using this schema:

{ "type" : "double" }

Values written to a double field must be in one of the supported real number formats.

Date

A date.

A field is specified to be of type date using this schema:

{ "type" : "date" }

Values written to a date field must be in one of the supported date formats.

Time

A time.

A field is specified to be of type time using this schema:

{ "type" : "time" }

Values written to a time field must be in one of the supported time formats.

Date time

A date time.

A field is specified to be of type datetime using this schema:

{ "type" : "datetime" }

Values written to a datetime field must be in one of the supported date time formats.

Duration

A duration.

A field is specified to be of type duration using this schema:

{ "type" : "duration" }

Values written to a duration field must be in one of the supported duration formats.

String

A string.

A field is specified to be of type string using this schema:

{ "type" : "string" }

Values written to a string field must be represented as a string in the data format you are using (e.g. a JSON string).

Contributor

A contributor id.

A field is specified to be of type contributor using this schema:

{ "type" : "contributor", "definition": "<name of contributor type>" }

See Contributor type for how to look-up or register the contributor type.

Values written to a contributor field must be represented as a string in the data format you are using (e.g. a JSON string).

UUID

A UUID.

A field is specified to be of type uuid using this schema:

{ "type" : "uuid" }

Values written to a uuid field must be in one of the supported UUID formats.

IP Address

An IPv4 or IPv6 address.

A field is specified to be of type ip using this schema:

{ "type" : "ip" }

Values written to an ip field must be in one of the supported IP Address formats.

Email Address

An email address.

A field is specified to be of type email using this schema:

{ "type" : "email" }

Values written to an email field must be in one of the supported Email Address formats.

URI

A URI.

A field is specified to be of type uri using this schema:

{ "type" : "uri" }

Values written to a uri field must be in one of the supported URI formats.

Geographic Point

A geographic point - represented as lat / lon coordinates.

A field is specified to be of type geoPoint using this schema:

{ "type" : "geoPoint" }

Values written to a geoPoint field must be in one of the supported Geographic Point formats.

Geographic Circle

A geographic circle - represented as the centre (lat / lon coordinates) and the radius.

A field is specified to be of type geoCircle using this schema:

{ "type" : "geoCircle" }

Values written to a geoCircle field must be in one of the supported Geographic Circle formats.

Geographic Rectangle

A geographic rectangle - represented as a pair of diagonally opposite lat / lon coordinates.

A field is specified to be of type geoRectangle using this schema:

{ "type" : "geoRectangle" }

Values written to a geoRectangle field must be in one of the supported Geographic Rectangle formats.

Tags

A field containing zero or more tags.

A field is specified to be of type tags using this schema:

{ "type" : "Tags" }

Valo populates fields containing tags automatically. Refer to the tag feature documentation for more details.

Record

A record represents a complex type. The top level type in a schema (the topDef) is generally a record. Anything which has a hierarchical document structure (think JSON) can be represented as a record.

A field is specified to be of type record using a schema like this:

{
  "type" : "record"
  "properties" : {
    "fieldName1": { "type": "..." },
    "fieldNameN": { "type": "..." },
  }
}

If your schema includes a hierarchical document structure (i.e. records contain properties that are themselves records) you will be unable to populate all of the fields with data formats that don’t support hierarchical data.

Array

Note

Array support is planned for a future version of Valo.