[
https://issues.apache.org/jira/browse/PHOENIX-3345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15553515#comment-15553515
]
ASF GitHub Bot commented on PHOENIX-3345:
-----------------------------------------
GitHub user lomoree opened a pull request:
https://github.com/apache/phoenix/pull/215
PHOENIX-3345 SQLException code's not propagating as expected
-- Primarily impacts unit tests in QueryCompilerTest.java
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/bloomberg/phoenix exceptions
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/phoenix/pull/215.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #215
----
commit a2c8bdf051773ff83dc6bb94ffcfd1edf2efd13b
Author: ERIC LOMORE <[email protected]>
Date: 2016-10-06T21:01:39Z
PHOENIX-3345 SQLException code's not propogating as expected
----
> 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)
