[
https://issues.apache.org/jira/browse/PHOENIX-3345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15543352#comment-15543352
]
Eric Lomore edited comment on PHOENIX-3345 at 10/3/16 8:43 PM:
---------------------------------------------------------------
Here's a test case that demonstrates this issue. [~maryannxue] and
[~jamestaylor] do you have any thoughts?
!variablestate.png!
was (Author: lomoree):
Here's a test case that demonstrates this issue. [~maryannxue] and
[~giacomotaylor] do you have any thoughts?
!variablestate.png!
> 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
> 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)
