phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-2314) Cannot prepare parameterized statement with a 'like' predicate
Date Wed, 23 Dec 2015 20:45:46 GMT

    [ https://issues.apache.org/jira/browse/PHOENIX-2314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15070174#comment-15070174
] 

Josh Elser commented on PHOENIX-2314:
-------------------------------------

bq. I am using an HDP stack provisioned by Ambari. 

Not to outright call you a liar, but Ambari+HDP doesn't install HBase or Phoenix to {{/usr/local}}.
It's going to be installing to {{/usr/hdp/...}} :). That's why I was a bit confused by the
paths you shared before.

bq. If I'm not mistaken, queryserver.py:121 seems to indicate that the HBase path is used.

I believe you are mistaken. {{phoenix_utils.phoenix_queryserver_jar}} should be a path to
{{<phoenix_installation>/lib/phoenix-server-$VERSION-runnable.jar}}. {{hbase_config_path}}
is the configuration directory for HBase (like I said earlier, getting {{hbase-site.xml}}).

Try modifying {{queryserver.py}} to print out {{java_cmd}} before it is invoked so that you
can see what the actual values in the classpath are. That should help remove any doubt about
where the jar is coming from.

> Cannot prepare parameterized statement with a 'like' predicate
> --------------------------------------------------------------
>
>                 Key: PHOENIX-2314
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-2314
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 4.5.2
>         Environment: Using Fiddler or cURL to communicate with a Phoenix 4.5.2 queryserver
using Avatica wire protocol
>            Reporter: Kevin Liew
>              Labels: avatica, phoenix
>
> *POST*
> {noformat}
> request: { "request":"prepare", "connectionId":"1646a1b9-334e-4a21-ade8-47c3d0c8e5a3",
"sql":"select * from emp where first_name like ?", "maxRowCount":-1 }
> Host: 192.168.203.156:8765
> Content-Length: 0
> {noformat}
> _select * from emp where first_name like ?_
> *RESPONSE*
> {noformat}
> HTTP/1.1 500 org.apache.phoenix.schema.TypeMismatchException: ERROR 203 (22005): Type
mismatch. BOOLEAN for null
> Date: Wed, 07 Oct 2015 22:42:26 GMT
> Cache-Control: must-revalidate,no-cache,no-store
> Content-Type: text/html; charset=ISO-8859-1
> Content-Length: 368
> Connection: close
> Server: Jetty(9.2.z-SNAPSHOT)
> <html>
> <head>
> <meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1"/>
> <title>Error 500 </title>
> </head>
> <body>
> <h2>HTTP ERROR: 500</h2>
> <p>Problem accessing /. Reason:
> <pre>    org.apache.phoenix.schema.TypeMismatchException: ERROR 203 (22005): Type
mismatch. BOOLEAN for null</pre></p>
> <hr /><i><small>Powered by Jetty://</small></i>
> </body>
> </html>
> {noformat}
> _org.apache.phoenix.schema.TypeMismatchException: ERROR 203 (22005): Type mismatch. BOOLEAN
for null_



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

Mime
View raw message