[DRILL-2999] Parse-error exception logged to stdout/stderr (visible in SQLLine output)

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Fix Version/s: Future
• Component/s: SQL Parser
• Assignee: Unassigned
• Reporter: Daniel Barclay
• Created: 08/May/15 21:52
• Updated: 24/Jun/16 21:50

Description

For some Calcite/parsing exceptions that seem to be internal (seem to be caught and processed (translated) at a higher level), Calcite or parsing logging is writing "SEVERE"-level logging messages to stdout or stderr.

When SQLLine runs Drill in embedded mode, those logging lines show up intermixed in the SQLLine output"

0: jdbc:drill:zk=local> bad syntax;
May 08, 2015 2:42:23 PM org.apache.calcite.runtime.CalciteException <init>
SEVERE: org.apache.calcite.runtime.CalciteException: Non-query expression encountered in illegal context
May 08, 2015 2:42:23 PM org.apache.calcite.runtime.CalciteException <init>
SEVERE: org.apache.calcite.runtime.CalciteContextException: From line 1, column 1 to line 1, column 3: Non-query expression encountered in illegal context
Error: SYSTEM ERROR: Failure parsing SQL. Non-query expression encountered in illegal context


[Error Id: 87c20db6-58b1-4042-9060-42ee29945377 on dev-linux2:31016] (state=,code=0)
0: jdbc:drill:zk=local> 

(The "Error: SYSTEM ..." lines are the normal error from SQLLine including exception message text from Drill. The four lines starting with "May" or "SEVERE" are the extraneous logging output.)