[
https://issues.apache.org/jira/browse/CALCITE-1236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15284634#comment-15284634
]
Josh Elser commented on CALCITE-1236:
-------------------------------------
For context: I had intentionally *not* done this because application-level
errors such as this are not avatica-server errors (e.g. the client needs to
know the error, but the server doesn't. The server worked exactly as expected
and is happy). However, I can also recognize the worth, when an avatica server
instance is deployed centrally for some organization, and some analysis of
errors that occurred after the fact would be nice to have in the server's log.
> Add Calcite exceptions into Phoenix Query Server logs
> -----------------------------------------------------
>
> 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)
