I believe it's entirely different issue. If you follow the code in BinaryArithmeticOperatorNode with a custom user arithmetic type in mind, then you should be able to see how the resolve logic doesn't work correctly. Note that our custom type has values of type com.ibm.icu.math.BigDecimal, and this is what we would like to get back from an arithmetic HQL expression when one of the values is of this type.