ThoughtSpot supports the common data types. Compare these with the data types you want to load, and do any necessary conversion ahead of loading the data.
Supported data types
The tables you create to receive the data must have the same number of columns and data types as the data you will be loading. Choose a data type for each column from the list of supported data types:
Table 1. Supported data types
|Kind of data
||Supported data types
||Specify the maximum number of characters, as in VARCHAR(255). The size limit is 1GB for VARCHAR values.
||DOUBLE is recommended.
||INT holds 32 bits.
BIGINT holds 64 bits.
|Date or time
|DATETIME, TIMESTAMP, and TIME are stored at the granularity of seconds.
TIMESTAMP is identical to DATETIME, but is included for syntax compatibilty.
Note the 65K limitation on the number of characters for VARCHAR. If you have any VARCHAR data that exceeds this limit, the entire load will fail.
For geographical data types, use VARCHAR. For latitude and longitude, you can use either VARCHAR or DOUBLE. After loading the data, designate it as a geographical data type when you Model Data in Bulk in the Modeling File. Wherever abbreviations or codes are used, they are the same as what the USPS (United States Postal Service) recognizes.
These types of data can be designated as geographical data, which enables them to be visualized using the Geo chart types:
Table 2. Data that uses geo charts
- name: United States
- long name: United States
- name_sort: United States of America
- abbreviation: U.S.A.
- adm0_a3: USA
- adm0_a3_is: USA
- adm0_a3_us: USA
- admin: United States of America
- brk_a3: USA
- brk_name: United States
- formal_en: United States of America
- iso_a2: US
- iso_a3: USA
- iso_n3: 840
||States in the United States
- name: California
- US Postal Service abbreviation: CA
||Must be used with LONGITUDE
||Must be used with LATITUDE
||Zip codes and zip codes +4 in the United States
- po_name: MT MEADOWS AREA
- ZIP: "00012"
- zip2: 12