[jira] [Created] (DRILL-2679) Out-of-range messages should report range bounds

["Daniel Barclay (Drill) (JIRA)" <ji...@apache.org>]

Daniel Barclay (Drill) created DRILL-2679:
---------------------------------------------

             Summary: Out-of-range messages should report range bounds
                 Key: DRILL-2679
                 URL: https://issues.apache.org/jira/browse/DRILL-2679
             Project: Apache Drill
          Issue Type: Task
            Reporter: Daniel Barclay (Drill)


Error messages that report that a value is out of range should include the bounds of the range that was exceeded (and probably what the range applies to) in addition to the value that exceeded the range.

For example, in the following, although the error message does report the value that was out of range, and exactly where it was in the query, it does not report what bound was violated (apparently the maximum number of digits (18?), or maybe the maximum number of post-decimal digits, or possibly the maximum value of the digits taken as an integer?) nor say what the bound is for (DECIMAL literals?  DOUBLE PRECISION literals? something else?: 

> SELECT 0.12345678901234567890 FROM INFORMATION_SCHEMA.CATALOGS;
Apr 03, 2015 4:14:10 PM org.eigenbase.sql.validate.SqlValidatorException <init>
SEVERE: org.eigenbase.sql.validate.SqlValidatorException: Numeric literal '0.12345678901234567890' out of range
Apr 03, 2015 4:14:10 PM org.eigenbase.util.EigenbaseException <init>
SEVERE: org.eigenbase.util.EigenbaseContextException: From line 1, column 8 to line 1, column 29: Numeric literal '0.12345678901234567890' out of range
Query failed: SqlValidatorException: Numeric literal '0.12345678901234567890' out of range

Error: exception while executing query: Failure while executing query. (state=,code=0)
> 




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)