StarRocks/starrocks

DECIMAL(38,18) / DECIMAL(38,18) silently returns NULL due to overflow, while equivalent multiplication works correctly

Chiusa

#73.784 aperta il 25 mag 2026

Vedi su GitHubGuida contributor
 (2 commenti) (0 reazioni) (0 assegnatari)Java (1246 fork)batch import
good first issuetype/bug

Metriche repository

Star
 (5717 stelle)
Metriche merge PR
 (Merge medio 1g 5h) (1000 PR mergiate in 30 g)

Descrizione

Issue

When dividing two DECIMAL(38,18) values (the maximum supported decimal precision in StarRocks), the result silently returns NULL due to precision overflow. The equivalent operation using multiplication with POW(..., -1) returns the correct result.

Steps to reproduce Returns NULL (bug)

SELECT CAST(2672.925686105492400095 AS DECIMAL(38,18))
     / CAST(421.193403692563637349 AS DECIMAL(38,18));

Returns 6.346076796721411 (works)

SELECT CAST(2672.925686105492400095 AS DECIMAL(38,18))
     * POW(CAST(421.193403692563637349 AS DECIMAL(38,18)), -1);

Workaround: explicit CAST to DOUBLE before division (works)

SELECT CAST(CAST(2672.925686105492400095 AS DECIMAL(38,18)) AS DOUBLE)
     / CAST(CAST(421.193403692563637349 AS DECIMAL(38,18)) AS DOUBLE);

Expected behavior

The session variable decimal_overflow_to_double should apply to the / operator the same way it applies to *.

Actual behavior

Division of two DECIMAL(38,18) values silently returns NULL. No error, no warning.

Starrocks version: 3.5.14

Guida contributor

Direzione di ricerca
Investigate the division operator implementation for DECIMAL(38,18) in StarRocks. Compare the overflow handling logic between division and multiplication. Check if the `decimal overflow to double` session variable is properly applied to division. Look at the source code in the repository, possibly in `src/exprs/` or `fe/fe core/src/main/java/com/starrocks/expression/`. Examine the behavior when the result precision exceeds 38 and see if casting to double is a viable workaround. Ensure that the fix aligns with the existing multiplication behavior.
Tech stack
javasql
Dominio
backenddatabase
Tipo issue
Bug
DifficoltàQuanto dovrebbe essere impegnativa per un nuovo contributor.
3
Tempo stimatoTempo stimato per completare e verificare uno scope piccolo.
Mezza giornata
Stato attivitàQuanto è probabile che la issue sia ancora attiva e reviewable.
Nuova
ChiarezzaQuanto chiaramente la issue descrive problema, scope e risultato atteso.
Chiara
Prerequisiti
SQL knowledgeStarRocks basic understanding
Adatta ai principiantiQuanto la issue è adatta a contributor alla prima esperienza.
50