Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
1.14.0
-
None
-
None
-
None
Description
The web console, query result page appears to have been modified recently. (It now contains a handy link to the query profile.) But, the page no longer handles failed queries.
Using the web console, enter an invalid query. In this case, introducing a deliberate typo in the example query:
SELECT * FROM cp.`employee.json` LIMT 20
Note the misspelled "LIMT".
The query results page appears with the message: "No result found."
This sounds like the file existed, but was empty. Looking in the logs revealed that, in fact, the query failed. Look in the Error tab on the query profile:
PARSE ERROR: Encountered "20" at line 1, column 39.
Was expecting one of:
<EOF>
...