Marwa Saleh created PHOENIX-5086:
------------------------------------
Summary: Prepare statement fails: Lost Bound parameter in
TO_TIMESTAMP function
Key: PHOENIX-5086
URL: https://issues.apache.org/jira/browse/PHOENIX-5086
Project: Phoenix
Issue Type: Bug
Affects Versions: 5.0.0
Reporter: Marwa Saleh
Please note the issue happens in case of SELECT and works fine in case of
UPSERT.
Prepared Statement SQL:
{noformat}
SELECT "DOC_KEY" FROM XYZ WHERE "DOC_MODIFY_DATE" >=
TO_TIMESTAMP(?,'yyyy-MM-dd HH:mm:ss.SSS','UTC'); {noformat}
{code:java}
preparedStatement.setString(1, "2018-12-30 14:38:24.208"); {code}
{code:java}
Stack trace:
Caused by: org.apache.calcite.avatica.AvaticaSqlException: Error -1 (00000) :
Remote driver error: RuntimeException: java.sql.SQLException: ERROR 2004
(INT05): Parameter value unbound. Parameter at index 1 is unbound ->
SQLException: ERROR 2004 (INT05): Parameter value unbound. Parameter at index 1
is unbound
at org.apache.calcite.avatica.Helper.createException(Helper.java:54)
at org.apache.calcite.avatica.Helper.createException(Helper.java:41)
at
org.apache.calcite.avatica.AvaticaConnection.executeQueryInternal(AvaticaConnection.java:520)
at
org.apache.calcite.avatica.AvaticaPreparedStatement.executeQuery(AvaticaPreparedStatement.java:133)
{code}
Possible to be patched?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
