[
https://issues.apache.org/jira/browse/CALCITE-1236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh Elser resolved CALCITE-1236.
---------------------------------
Resolution: Fixed
Fixed in
https://git1-us-west.apache.org/repos/asf?p=calcite.git;a=commit;h=a15aa88bb2820d8de008375d9033fc5c22fc1775.
All exceptions caught by the Jetty handler implementation will be logged at
the DEBUG level (downstream can enable/disable as they see fit). By default,
downstream will continue to not be spammed by bad clients.
> Log exceptions sent back to client in server log
> ------------------------------------------------
>
> Key: CALCITE-1236
> URL: https://issues.apache.org/jira/browse/CALCITE-1236
> Project: Calcite
> Issue Type: Improvement
> Reporter: Duo Xu
> Assignee: Josh Elser
> Fix For: avatica-1.8.0
>
>
> In Phoenix Query Server, for example, if the client sends a SQL query with
> wrong syntax, the server will return a 500 response with the exception stack
> traces. But there is no error messages in PQS logs indicating this.
> It would be good to log these exceptions into Phoenix Query Server logs, so
> the user can monitoring and analyze the logs later.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
