[
https://issues.apache.org/jira/browse/IMPALA-14464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18030662#comment-18030662
]
ASF subversion and git services commented on IMPALA-14464:
----------------------------------------------------------
Commit 69813a8c40f1406a1491f4dfb16b6173af4e3ce3 in impala's branch
refs/heads/master from Steve Carlin
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=69813a8c4 ]
IMPALA-14464: Calcite planner should allow semi-colon in statement
The Calcite planner now handles a sql statement that has a semi-colon
at the end. Note that impala-shell doesn't pass the semi-colon into
the server. This is only seen with a direct call to the server.
Change-Id: Ie690159cd03f28f6b793628aa946292af71b6970
Reviewed-on: http://gerrit.cloudera.org:8080/23517
Reviewed-by: Joe McDonnell <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>
> Calcite planner: allow semi-colon in direct connection
> ------------------------------------------------------
>
> Key: IMPALA-14464
> URL: https://issues.apache.org/jira/browse/IMPALA-14464
> Project: IMPALA
> Issue Type: Sub-task
> Reporter: Steve Carlin
> Assignee: Steve Carlin
> Priority: Major
>
> The following python produces an error for the Calcite planner (running
> impala-python3 with this script):
> {code:java}
> from impala.dbapi import connect
> conn = connect(host='localhost', port=21050)
> cursor = conn.cursor()
> # Running with regular Impala planner (as use_calcite_planner query option is
> false)
> # This works:
> cursor.execute('select 4;')
> # Running with Calcite, the same statement fails to parse.
> cursor.execute('set use_calcite_planner=true')
> cursor.execute('select 4;')
> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
