Supported Data Types and Values - Amazon QuickSight

Supported Data Types and Values

Amazon QuickSight currently supports the following primitive data types: Date, Decimal, Integer, String. QuickSight accepts Boolean values by promoting them to integers. It can also derive geospatial data types. Geospatial data types use metadata to interpret the physical data type. Latitude and longitude are numeric. All other geospatial categories are strings.

Make sure that any table or file that you use as a data source contains only fields that can be implicitly converted to these data types. Amazon QuickSight skips any data rows that can't be converted.

String and Text Data

Fields or columns that contain characters are called strings. A field with the data type of STRING can initially contain almost any type of data. Examples include names, descriptions, phone numbers, account numbers, JSON data, cities, post codes, dates, and numbers that can be used to calculate. These types are sometimes called textual data in a general sense, but not in a technical sense. QuickSight doesn't support binary and character large objects (BLOBs) in dataset columns. In the QuickSight documentation, the term "text" always means "string data".

The first time you query or import the data, QuickSight tries to interpret the data that it identifies as other types, for example dates and numbers. It's a good idea to verify that the data types assigned to your fields or columns are correct.

For each string field in imported data, QuickSight uses a field length of 8 bytes plus the UTF-8 encoded character length. Amazon QuickSight supports UTF-8 file encoding, but not UTF-8 (with BOM).

Numeric Data

Numeric data includes integers and decimals. Integers with a data type of INT are negative or positive numbers that don't have a decimal place. QuickSight doesn't distinguish between large and small integers. Decimals with a data type of DECIMAL are negative or positive numbers that contain at least one decimal place, before or after the decimal point.

Truncation of data beyond the fourth decimal place to the right. QuickSight supports displaying of no more than four decimal places to the right of the decimal point. The full value is still used in all calculations, but it doesn't display.

The following rules apply:

  • When you create or edit a dataset, you can use your data in its original state to create calculations on decimal data.

  • When this data is imported into SPICE.

QuickSight enables you to create calculations that are based on DECIMAL data having more than four decimal places to the right of the decimal point. However, QuickSight can display no more than four decimal places to the right of the decimal point. The value is truncated, not rounded, when displayed in data preparation or analyses and when imported into SPICE. For example, 13.00049 is truncated to 13.0004.

As an example, take a decimal field with a value of 0.00006, which displays in the user interface as 0.0. The full value 0.00006 is still used in all calculations. The following examples show how the true value functions in calculations:

  • My-Decimal > 0 = TRUE : The display value is true.

  • ceil(My-Decimal) = 1 : The display value is 1.

  • My-Decimal + 0.00009 = 0.00015 : The display value is 0.0001.

  • My-Decimal * 1.5 = 0.00009 : The display value is 0.0.

For each INT and DECIMAL field in imported data, QuickSight uses a field length of 8 bytes. QuickSight supports UTF-8 file encoding, but not UTF-8 (with BOM).

Date and Time Data

Fields with a data type of Date also include time data, and are also known as Datetime fields. QuickSight supports dates and times that use supported data formats.

QuickSight uses UTC time for querying, filtering, and displaying date data. When date data doesn't specify a time zone, QuickSight assumes UTC values. When date data does specify a time zone, QuickSight converts it to display in UTC time. For example, a date field with a time zone offset like 2015-11-01T03:00:00-08:00 is converted to UTC and displayed in Amazon QuickSight as 2015-11-01T15:30:00.

For each DATE field in imported data, QuickSight uses a field length of 8 bytes. QuickSight supports UTF-8 file encoding, but not UTF-8 (with BOM).