You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@impala.apache.org by "bharath v (JIRA)" <ji...@apache.org> on 2018/11/15 01:11:00 UTC
[jira] [Resolved] (IMPALA-3149) Bind variable issue in ODBC
[ https://issues.apache.org/jira/browse/IMPALA-3149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
bharath v resolved IMPALA-3149.
-------------------------------
Resolution: Not A Problem
Fix Version/s: Not Applicable
Please take it up with the driver folks. Does not appear to be an Impala issue.
> Bind variable issue in ODBC
> ---------------------------
>
> Key: IMPALA-3149
> URL: https://issues.apache.org/jira/browse/IMPALA-3149
> Project: IMPALA
> Issue Type: Bug
> Components: Clients
> Affects Versions: Impala 2.2, Impala 2.3.0
> Reporter: Jiri Novak
> Priority: Minor
> Fix For: Not Applicable
>
>
> For some reason Cloudera Impal does not recognize bind variable in HAVING clause.
> If we execute the following simple query using .Net and ADO.Net
> {code:sql}
> SELECT COUNT(address.address_id)
> , address.country
> FROM quest_stage.address address
> GROUP BY address.country
> HAVING (COUNT(address.address_id) > ?)
> {code}
> It returns the following error
> Error:
> {noformat}
> [Cloudera][ImpalaODBC] (110) Error while executing a query in Impala: [HY000] : AnalysisException: Syntax error in line 5:
> HAVING (COUNT(address.address_id) > ?)
> ^
> Encountered: Unexpected character
> Expected: CASE, CAST, EXISTS, FALSE, IF, INTERVAL, NOT, NULL, TRUE, IDENTIFIER
> {noformat}
> Bind variable works correctly in WHERE clause. Also the query returns correct result if we use a number instead of the bind variable.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)