Data types

• Session Level: To use the new data types (Tinyint, Smallint, Int, Float, Varchar, TIMESTAMP and BINARY), add a set statement before the table statement

  set odps.sql.type.system.odps2=true;

  And submit the execution together with the table statement.The SQL tool submitted through MaxCompute Studio automatically adds the set statement to submit execution by default.
• When it comes to INT types, 32 bits are added to the set statement and converted to BIGINT, 64 bits, if not added.
• SDK 0.27.2-public version and above, Client 0.27.0 version and above support new data type.

Open new typeodps.sql.type.system.odps2of influence.

• Implicit type conversion rules change.

  Possible compatibility issues: Some implicit type conversions under the new type system will be disabled, including string - > bigint, string - datetime, double - > bigint, decimal - > double, decimal - > bigint are all at risk of precision loss or error. This situation can be solved by cast transformation.

• Support operations, built-in functions, UDF is not the same.

  Some operations and built-in functions that take new types as parameters and return values are not available without opening new types, including UDF, which overloads new types as parameters and return values. Possible compatibility issues: For example, UDF contains two overloads: bigint and int. The old type must be the overload of bigint, while the new type may be resolved to the overload of int.

• The type of constant will change.

  A single shaping constant, such as 123, is bigint type under the old type, and int type under the new type. Possible compatibility issues: Type int leads to inconsistencies in function prototypes invoked by subsequent operations, including new type tables generated after dropping (i.e., writing to disk) that lead to changes in the behavior of peripheral tools and subsequent jobs.

• The resolution of the bigint keyword is different.

  In the old type system, the int keyword is treated as bigint, while the new type system is treated as real int. Possible compatibility issues: Type int leads to inconsistencies in function prototypes invoked by subsequent operations, including new type tables generated after dropping (i.e., writing to disk) that lead to changes in the behavior of peripheral tools and subsequent jobs.

For a detailed description of setproject, please see:Other operations

• NOTE 1:When insert is constant to decimal field, pay attention to the writing of constants. For example,3.5BD in the definition of constants.

  insert into test_tb(a) values (3.5BD);

  The a field is decimal type.

• NOTE 2: For INT constant, if the range of INT is exceeded, INT is converted into BIGINT;  if the range of BIGINT is exceeded, it is converted into DOUBLE. 
  In MaxCompute versions earlier than 2.0, all INT types in SQL script are converted to BIGINT , for example:

  create table a_bigint_table(a int); -- the int here is actually treated as a bigint
  select cast(id as int) from mytable; -- the int here is actually treated as a bigint

  To be compatible with earlier MaxCompute versions, MaxCompute 2.0 retains this conversion without setting odps.sql.type.system.odps2 as True. However, a warning is triggered when INT is treated as BIGINT. In this case, we recommend that you change an Int to a Bigint to avoid confusion.

• NOTE 3: VARCHAR constants can be expressed by STRING constants of implicit transformation.
• NOTE 4: STRING constants support connections, for example, abc xyz is parsed as abcxyz, and different parts can be written on different lines.
• NOTE 5: The time value displayed by the current query does not contain milliseconds. The tunnel command specifies the time format through-dfp , and can be specified in milliseconds, such astunnel upload -dfp 'yyyy-MM-dd HH:mm:ss.SSS' , for more information about tunnel commands, refer toTunnel commands.