phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Lomore (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (PHOENIX-3345) SQLException code's not propagating as expected
Date Mon, 03 Oct 2016 20:38:21 GMT

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

Eric Lomore updated PHOENIX-3345:
---------------------------------
    Description: 
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.

  was:
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.

Particularly prevalent in those test cases in QueryCompilerTest.java




> 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)

Mime
View raw message