tree ca1f205153489b47583002b55c359cb0161361b2
parent d5e8d4d68007899df17f390a756422d511d746d5
author Abhishek Agarwal <1477457+abhishekagarwal87@users.noreply.github.com> 1625743517 +0530
committer GitHub <noreply@github.com> 1625743517 +0530
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJg5uCdCRBK7hj4Ov3rIwAAbS4IAHkUTR9TpeWocHkepwg+KZXr
 F/uNiVXcK6DwkCQxrCZUEYW0gkeG0o2M/kEQQXrLhJMWkMa6lggig3Z4tddxbddS
 vyJv73Oy2hcwtm54ElqvUNs51Eyr/egYPxlNf2erteiFZflbcspasv/CIvXkSZrg
 +R7AnFBocojveHXx1/qzWNbB/YODnksyvkQYrdb/Q8Qgi1YhRB4WOHVe7gN4J7o8
 OTM7Ar89bzNXpepy5LlpWDi6z9xyAqhrImCdXODuPwyUptD4yXKbc96neQzxTmUx
 /DKYFR3wgRr15I2rq4N8E9LJIAERMd9pT8n1VCJizcSoHaTRFQhTyO0w2IJT8Co=
 =Mcw7
 -----END PGP SIGNATURE-----
 

Better error message for unsupported double values (#11409)

A constant expression may evaluate to Double.NEGATIVE_INFINITY/Double.POSITIVE_INFINITY/Double.NAN e.g. log10(0). When using such an expression in native queries, the user will get the corresponding value without any error. In SQL, however, the user will run into NumberFormatException because we convert the double to big-decimal while constructing a literal numeric expression. This probably should be fixed in calcite - see https://issues.apache.org/jira/browse/CALCITE-2067. This PR adds a verbose error message so that users can take corrective action without scratching their heads.