yashmayya commented on code in PR #15263:
URL: https://github.com/apache/pinot/pull/15263#discussion_r2052753412
##########
pinot-query-planner/src/main/java/org/apache/pinot/calcite/rel/rules/PinotEvaluateLiteralRule.java:
##########
@@ -258,13 +275,18 @@ private static Object convertResultValue(@Nullable Object
resultValue, RelDataTy
return TimestampUtils.toMillisSinceEpoch(resultValue.toString());
}
}
- // Return BigDecimal for numbers
- if (resultValue instanceof Integer || resultValue instanceof Long) {
+ // Use BigDecimal for INTEGER / BIGINT / DECIMAL literals
Review Comment:
Hm, I followed this logic to keep it consistent with Calcite which uses
`BigDecimal` for literals of these SQL types. I think it makes more sense to
try to align with Calcite rather than SSE as long as we're not breaking
anything here?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscr...@pinot.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@pinot.apache.org
For additional commands, e-mail: commits-h...@pinot.apache.org
