You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@phoenix.apache.org by "Eric Lomore (JIRA)" <ji...@apache.org> on 2016/10/03 20:46:20 UTC

[jira] [Assigned] (PHOENIX-3345) SQLException code's not propagating as expected

     [ https://issues.apache.org/jira/browse/PHOENIX-3345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eric Lomore reassigned PHOENIX-3345:
------------------------------------

    Assignee: Eric Lomore

> SQLException code's not propagating as expected
> -----------------------------------------------
>
>                 Key: PHOENIX-3345
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-3345
>             Project: Phoenix
>          Issue Type: Sub-task
>            Reporter: Eric Lomore
>            Assignee: Eric Lomore
>         Attachments: variablestate.png
>
>
> Perhaps this is intended by Calcite, but when errors are thrown by execute() functions the error code that is initially thrown (say 1000) does not make its way to the final SQLException on top.
> This is prevalent in multiple tests throughout QueryCompilerTest.java. One such example is included below.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)