[
https://issues.apache.org/jira/browse/CALCITE-1236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15284639#comment-15284639
]
Josh Elser commented on CALCITE-1236:
-------------------------------------
And, this would also help enable admins to do some analysis to determine cases
when users might be running into product issues (and not tell someone about
it). For example, users might just think some error they get is "how it is"
when it is in fact a bug -- we want to make sure all parties can see the
exception if they want to.
> 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)
