When importing data into Datameer, it is important to know which type of data you are importing or need to import. When using your data within workbooks, certain Datameer functions only work with certain types of data. Congruently, certain functions return only a specific type of data.
Also there are data requirements when using infographic widgets to visualize your data.
Data Field Types
64-Bit integer value
Unlimited integer value
64-Bit float value
High-precision float value
|LIST||a collection of multiple values of one data type|
float, big decimal, integer, or big integer
float, big decimal, integer, big integer, date, string, list, or Boolean
In mathematics integers (aka whole numbers) are made up of the set of natural numbers including zero (0,1,2,3, ...) along with the negatives of natural numbers (-1,-2,-3, ...). When talking about Integers in computer programming, it is necessary to define a minimum and maximum value. Datameer uses a 64-bit integer which allows the user to represent whole numbers between -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807.
Big integers are like integers, but they are not limited to 64 bits. They are represented using arbitrary-precision arithmetic. Big integers represent only whole numbers. Big integers in Datameer are treated differently than in Hive because Datameer allows a larger range of values, so they are written as strings into a Hive table if you export. By default, the precision for big integers is set at 32 upon import. This can updated if needed in the default properties by changing the value of das.big-decimal.precision=.
In mathematics, there are real numbers that represent fractions (1/2, 12/68) or numbers with decimal places (12.75, -18.35). Datameer uses double precision floating-point representation (aka float) to manipulate and represent real numbers. The complete range of numbers that can be represented this way is approximately 2 -1022 through (1+(1-2 -52))x2 1023. During import/upload, Datameer automatically recognizes a number with either a single period (.) or single comma (,) as a decimal separator and defines this data as a float data type. After ingestion, Datameer stores float and big decimal values using a period (.) character. The auto schema detection for the float data type works with CSV, JSON, XML, Key/value files.
Big decimals are similar to float values. The main advantage of this data field type is that they are exact to the number of decimal places for which they are configured, float values might be inaccurate in certain cases. If a number has more decimal places than big decimal was configured for, then the number is rounded. The number of decimal places can be configured in
32 digits is the default precision used by Datameer for big decimal values upon import.
In Datameer, data in the DATE primitive data type is always represented in a Gregorian, month-day-year (MDY) format (e.g., "Sep 16, 2010 02:56:39 PM"). Datameer detects if your data should be parsed into the DATE data type during ingest. This can also be done after ingest as other data types can be converted to the DATE primitive data type using workbook functions.
Boolean data in computing has two values, either true or false. It is used in many logical expressions and is derived from Boolean algebra created by George Boole in the 19th century.
In Datameer multiple values can be combined into a list. Lists are a series of values of a single data type, which starts counting from zero (0).
Data Mapping in Avro
When importing data to Datameer, data types are mapped as follows:
|Avro Schema Type||Datameer Value Type|
|Bytes with logical type Decimal||BIG_DECIMAL|
|Fixed with logical type Decimal||BIG_DECIMAL|
When exporting data to Avro, data types are mapped as follows:
If a column marked as accept empty a union scheme type is created, e.g. union( null, string) for nullable string type.
|Datameer Value Type||Avro Schema Type|
|DATE without pattern||Long|
|DATE with pattern||String|
|LIST<listtype>||Arrays<converted list type>|
Data Mapping in Parquet
Export data mapping
When exporting data to Parquet, data types are mapped as follows:
Datameer field type
Parquet field type
Import data mapping
When importing data from Parquet, data types are mapped as follows:
|Parquet Field Type||Datameer Field Type|
Parquet files using the INT96 format are interpreted as time stamps. Datameer accepts these columns, but cuts off the nanoseconds. If the workbook has Ignore Errors enabled, then those error messages are stored in a separate column and the column with the error is NULL. The chart below provides additional Parquet storage mapping details.
|DATE||TIMESTAMP_MILLIS||Stored as INT64|
|STRING||UTF8||BINARY format with UTF-8 encoding|
|BIGINTEGER||DECIMAL||BINARY format with precision of 1 and scale of 0|
|LIST||Repeated elements of group of the list element type.|
Optional group of a repeating group of optional element types. Nested lists are supported.
Data Mapping in External Systems
Export Data Mapping
When export data to External Systems, data types are mapped as follows:
|Datameer Field Type||Hive Field Type|
|BIG_DECIMAL||DECIMAL with copied precision and scale|
|LIST[A]||ARRAY [A] (INFO: We support recursive types)|