[DRILL-3902] Bad error message: core cause not included in text; maybe wrong kind

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Done
• Fix Version/s: 1.13.0
• Assignee: Vitalii Diravka
• Reporter: Daniel Barclay
• Created: 06/Oct/15 21:33
• Updated: 06/Dec/18 17:19
• Resolved: 06/Dec/18 17:19

Description

When trying to use an empty directory as a table causes Drill to fail by hitting an IndexOutOfBoundsException, the final error message includes the text from the IndexOutOfBoundsException's getMessage()--but fails to mention IndexOutOfBoundsException itself (or equivalent information):

0: jdbc:drill:zk=localhost:2181> SELECT *   FROM `dfs`.`root`.`/tmp/empty_directory`;
Error: VALIDATION ERROR: Index: 0, Size: 0


[Error Id: 66ff61ed-ea41-4af9-87c5-f91480ef1b21 on dev-linux2:31010] (state=,code=0)
0: jdbc:drill:zk=localhost:2181> 

Also, since this isn't a coherent/intentional validation error but an internal error, shouldn't this be a SYSTEM ERROR message?

(Does the SYSTEM ERROR case including the exception class name in the message?)

Daniel

Issue Links

• Is contained by: DRILL-2618 BasicFormatMatcher calls getFirstPath(...) without checking # of paths is not zero