Datatypes

This topic describes standard datatypes and space-saving variations for values stored in HEAVY.AI.
Datatypes
Each HEAVY.AI datatype uses space in memory and on disk. For certain datatypes, you can use fixed encoding for a more compact representation of these values. You can set a default value for a column by using the DEFAULT constraint; for more information, see CREATE TABLE.
Datatypes, variations, and sizes are described in the following table.
Datatype
Size (bytes)
Notes
BIGINT
8
Minimum value: -9,223,372,036,854,775,807; maximum value: 9,223,372,036,854,775,807.
BIGINT ENCODING FIXED(8)
1
Minimum value: -127; maximum value: 127
BIGINT ENCODING FIXED(16)
2
Same as SMALLINT.
BIGINT ENCODING FIXED(32)
4
Same as INTEGER.
BOOLEAN
1
TRUE: 'true', '1', 't'. FALSE: 'false', '0', 'f'. Text values are not case-sensitive.
DATE[1]
4
Same as DATE ENCODING DAYS(32). 
DATE ENCODING DAYS(16)
2
Range in days: -32,768 - 32,767
 Range in years: +/-90 around epoch, April 14, 1880 - September 9, 2059.
 Minumum value: -2,831,155,200; maximum value: 2,831,068,800.
 Supported formats when using COPY FROM: mm/dd/yyyy, dd-mmm-yy, yyyy-mm-dd, dd/mmm/yyyy.
DATE ENCODING DAYS(32)
4
Range in years: +/-5,883,517 around epoch. Maximum date January 1, 5885487 (approximately). Minimum value: -2,147,483,648; maximum value: 2,147,483,647. Supported formats when using COPY FROM: mm/dd/yyyy, dd-mmm-yy, yyyy-mm-dd, dd/mmm/yyyy.
DATE ENCODING FIXED(16)
2
In DDL statements defaults to DATE ENCODING DAYS(16). Deprecated.
DATE ENCODING FIXED(32)
4
In DDL statements defaults to DATE ENCODING DAYS(16). Deprecated.
DECIMAL
2, 4, or 8
Takes precision and scale parameters: DECIMAL(precision,scale)
Size depends on precision:
Up to 4: 2 bytes
5 to 9: 4 bytes
10 to 18 (maximum): 8 bytes
 Scale must be less than precision.
DOUBLE
8
Variable precision. Minimum value: -1.79 x e^308; maximum value: 1.79 x e^308
EPOCH
8
Seconds ranging from -30610224000 (1/1/1000 00:00:00) through 185542587100800 (1/1/5885487 23:59:59).
FLOAT
4
Variable precision. Minimum value: -3.4 x e^38; maximum value: 3.4 x e^38.
INTEGER
4
Minimum value: -2,147,483,647; maximum value: 2,147,483,647.
INTEGER ENCODING FIXED(8)
1
Minumum value: -127; maximum value: 127.
INTEGER ENCODING FIXED(16)
2
Same as SMALLINT.
LINESTRING
Variable[2]
Geospatial datatype. A sequence of 2 or more points and the lines that connect them. For example: LINESTRING(0 0,1 1,1 2)
MULTIPOLYGON
Variable[2]
Geospatial datatype. A set of one or more polygons. For example:MULTIPOLYGON(((0 0,4 0,4 4,0 4,0 0),(1 1,2 1,2 2,1 2,1 1)), ((-1 -1,-1 -2,-2 -2,-2 -1,-1 -1)))
[1] - In OmniSci release 4.4.0 and higher, you can use existing 8-byte DATE columns, but you can create only 4-byte DATE columns (default) and 2-byte DATE columns (see DATE ENCODING DAYS(16)).
[2] - See Storage and Compression below for information about geospatial datatype sizes.
HEAVY.AI does not support geometry arrays.
Timestamp values are always stored in 8 bytes. The greater the precision, the lower the fidelity.
Geospatial Datatypes
HEAVY.AI supports the LINESTRING, MULTIPOLYGON, POINT, and POLYGON geospatial datatypes.
In the following example:
p0, p1, ls0, and poly0 are simple (planar) geometries.
p4 is point geometry with Web Mercator longitude/latitude coordinates.
p2, p3, ls1, ls2, poly1, and mpoly0 are geometries using WGS84 SRID=4326 longitude/latitude coordinates.
1
CREATE TABLE geo ( name TEXT ENCODING DICT(32),
2
                   p0 POINT,
3
                   p1  GEOMETRY(POINT),
4
                   p2 GEOMETRY(POINT, 4326),
5
                   p3 GEOMETRY(POINT, 4326) ENCODING NONE,
6
                   p4 GEOMETRY(POINT, 900913),
7
                   ls0  LINESTRING,
8
                   ls1 GEOMETRY(LINESTRING, 4326) ENCODING COMPRESSED(32),
9
                   ls2 GEOMETRY(LINESTRING, 4326) ENCODING NONE,
10
                   poly0 POLYGON,
11
                   poly1 GEOMETRY(POLYGON, 4326) ENCODING COMPRESSED(32),
12
                   mpoly0 GEOMETRY(MULTIPOLYGON, 4326)
13
                  );
Copied!
Storage
Geometry storage requirements are largely dependent on coordinate data. Coordinates are normally stored as 8-byte doubles, two coordinates per point, for all points that form a geometry. Each POINT geometry in the p1 column, for example, requires 16 bytes.
Compression
WGS84 (SRID 4326) coordinates are compressed to 32 bits by default. This sacrifices some precision but reduces storage requirements by half.
For example, columns p2, ls1, poly1, and mpoly0 in the table defined above are compressed. Each geometry in the p2 column requires 8 bytes, compared to 16 bytes for p0.
You can explicitly disable compression. WGS84 columns p3, ls2 are not compressed and continue using doubles. Simple (planar) columns p0, p1, ls0, poly1 and non-4326 column p4 are not compressed.
For more information about geospatial datatypes and functions, see Geospatial Capabilities.
Defining Arrays
Define datatype arrays by appending square brackets, as shown in the arrayexamples DDL sample.
1
CREATE TABLE arrayexamples (
2
  tiny_int_array TINYINT[],
3
  int_array INTEGER[],
4
  big_int_array BIGINT[],
5
  text_array TEXT[] ENCODING DICT(32), --OmniSci supports only DICT(32) TEXT arrays.
6
  float_array FLOAT[],
7
  double_array DOUBLE[],
8
  decimal_array DECIMAL(18,6)[],
9
  boolean_array BOOLEAN[],
10
  date_array DATE[],
11
  time_array TIME[],
12
  timestamp_array TIMESTAMP[])
Copied!
You can also define fixed-length arrays. For example:
1
CREATE TABLE arrayexamples (
2
  float_array3 FLOAT[3],
3
  date_array4 DATE[4]
Copied!
Fixed-length arrays require less storage space than variable-length arrays.
Fixed Encoding
To use fixed-length fields, the range of the data must fit into the constraints as described. Understanding your schema and the scope of potential values in each field helps you to apply fixed encoding types and save significant storage space.
These encodings are most effective on low-cardinality TEXT fields, where you can achieve large savings of storage space and improved processing speed, and on TIMESTAMP fields where the timestamps range between 1901-12-13 20:45:53 and 2038-01-19 03:14:07. If a TEXT ENCODING field does not match the defined cardinality, HEAVY.AI substitutes a NULL value and logs the change.
For DATE types, you can use the terms FIXED and DAYS interchangeably. Both are synonymous for the DATE type in HEAVY.AI.
Some of the INTEGER options overlap. For example, INTEGER ENCODINGFIXED(8) and SMALLINT ENCODINGFIXED(8) are essentially identical.
Shared Dictionaries
You can improve performance of string operations and optimize storage using shared dictionaries. You can share dictionaries within a table or between different tables in the same database. The table with which you want to share dictionaries must exist when you create the table that references the TEXT ENCODING DICT field, and the column that you are referencing in that table must also exist. The following small DDL shows the basic structure:
1
CREATE TABLE text_shard (
2
i TEXT ENCODING DICT(32),
3
s TEXT ENCODING DICT(32),
4
SHARD KEY (i))
5
WITH (SHARD_COUNT = 2);
6
​
7
CREATE TABLE text_shard1 (
8
i TEXT,
9
s TEXT ENCODING DICT(32),
10
SHARD KEY (i),
11
SHARED DICTIONARY (i) REFERENCES text_shard(i))
12
WITH (SHARD_COUNT = 2);
Copied!
In the table definition, make sure that referenced columns appear before the referencing columns.
For example, this DDL is a portion of the schema for the flights database. Because airports are both origin and destination locations, it makes sense to reuse the same dictionaries for name, city, state, and country values.
1
create table flights (
2
*
3
*
4
*
5
dest_name TEXT ENCODING DICT,
6
dest_city TEXT ENCODING DICT,
7
dest_state TEXT ENCODING DICT,
8
dest_country TEXT ENCODING DICT,
9
​
10
*
11
*
12
*
13
origin_name TEXT,
14
origin_city TEXT,
15
origin_state TEXT,
16
origin_country TEXT,
17
*
18
*
19
*
20
​
21
SHARED DICTIONARY (origin_name) REFERENCES flights(dest_name),
22
SHARED DICTIONARY (origin_city) REFERENCES flights(dest_city),
23
SHARED DICTIONARY (origin_state) REFERENCES flights(dest_state),
24
SHARED DICTIONARY (origin_country) REFERENCES flights(dest_country),
25
*
26
*
27
*
28
)
29
WITH(
30
*
31
*
32
*
33
)
Copied!
To share a dictionary in a different existing table, replace the table name in the REFERENCES instruction. For example, if you have an existing table called us_geography, you can share the dictionary by following the pattern in the DDL fragment below.
1
create table flights (
2
​
3
*
4
*
5
*
6
​
7
SHARED DICTIONARY (origin_city) REFERENCES us_geography(city),
8
SHARED DICTIONARY (origin_state) REFERENCES us_geography(state),
9
SHARED DICTIONARY (origin_country) REFERENCES us_geography(country),
10
SHARED DICTIONARY (dest_city) REFERENCES us_geography(city),
11
SHARED DICTIONARY (dest_state) REFERENCES us_geography(state),
12
SHARED DICTIONARY (dest_country) REFERENCES us_geography(country),
13
​
14
*
15
*
16
*
17
)
18
WITH(
19
*
20
*
21
*
22
);
Copied!
The referencing column cannot specify the encoding of the dictionary, because it uses the encoding from the referenced column.

SQL - Previous

Data Definition (DDL)

Users and Databases

Last modified 2mo ago

Export as PDF

Copy link

Contents