You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
YQL support is required to implement the support of the type on the YTsaurus side. Later, this type can be supported on the YDB side. Actually, there was earlier reported an issue to implement this in YDB: #151
The text was updated successfully, but these errors were encountered:
Extend the existing Decimal type to be able to specify a large Precision up to 76.
For Precision values in the range of 1 - 35, nothing changes and the value is stored as an Int120 inside TUnboxedValuePod.
For Precision values in the range of 36 - 76, the value is stored as a binary string of 32 bytes (similar to a UUID) and is an Int256 (a pair of Int128, Uint128).
Serialization of large Decimals must be binary compatible with that of small Decimals including the special values Nan, Inf.
All built-in functions that work with small Decimals, such as conversions, comparisons, arithmetic, etc., must work with large Decimals as well.
All aggregations that work with small Decimals, such as sum, min, max, etc., must work with large Decimals as well too.
So far, only decimals up to 35 digits are supported, as Decimal128 allows up to 38 digits and 12 bits are reserved for an inline representation.
For some cases, this is not sufficient and usually systems support up to 76 digits which is a maximum for Decimal256 (see Clickhouse docs for instance https://clickhouse.com/docs/en/sql-reference/data-types/decimal).
YQL support is required to implement the support of the type on the YTsaurus side. Later, this type can be supported on the YDB side. Actually, there was earlier reported an issue to implement this in YDB: #151
The text was updated successfully, but these errors were encountered: