Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Fixed
-
1.12.0
-
None
Description
Currently, Decimal types are disabled by default since existing Decimal implementation has a lot of flaws and performance problems. The goal of this Jira to describe majority of them and possible ways of improving existing implementation to be able to enable Decimal data types by default.
Attachments
Issue Links
- causes
-
DRILL-6435 MappingSet is stateful, so it can't be shared between threads
- Resolved
- is related to
-
DRILL-6355 Decimal data type enhancements for pre-planning stage
- Open
-
ARROW-61 [Java] Method can return the value bigger than long MAX_VALUE
- Resolved
-
DRILL-2101 Decimal literals are treated as double
- Resolved
-
DRILL-3909 Decimal round functions corrupts input data
- Resolved
-
DRILL-4834 decimal implementation is vulnerable to overflow errors, and extremely complex
- Resolved
-
DRILL-5390 Casting as decimal does not make drill use the decimal value vector
- Resolved
-
DRILL-5858 case expression using decimal expression causes Assignment conversion not possible
- Resolved
-
DRILL-6378 MajorType passed into UDF with FieldReader has unset prec, scale for DECIMAL
- Resolved
-
DRILL-1003 var_pop(decimal) cause internal error
- Resolved
-
DRILL-1004 stddev_samp(decimal) cause interval error
- Resolved
-
DRILL-1005 stddev_pop(decimal) cause internal error
- Resolved
-
DRILL-2282 Eliminate spaces, special characters from names in function templates
- Open
-
DRILL-4552 During inference, treat decimal literals as Double when planner.enable_decimal_data_type is off
- Closed
- relates to
-
DRILL-4184 Drill does not support Parquet DECIMAL values in variable length BINARY fields
- Resolved
-
DRILL-6221 Decimal aggregations for NULL values result in 0.0 value
- Resolved
-
DRILL-920 var_samp(decimal38) cause internal assertion error
- Resolved
- links to