You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2022/01/26 00:20:00 UTC

[jira] [Commented] (IMPALA-11062) The now_string option doesn't work in plannedstatement mode

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

ASF subversion and git services commented on IMPALA-11062:
----------------------------------------------------------

Commit 2e916968992321bf013bc229c89b070d47bb33fa in impala's branch refs/heads/master from Steve Carlin
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=2e91696 ]

IMPALA-11062: "now_string" option not working properly

The "now_string" option was not working when queries are
being sent through the "ExecutePlannedStatement" API. The
string needed to be copied over to the TQueryCtx object
used in RuntimeState.

Change-Id: I977b3a53553aaa40f8d82e7b5b6883b1a6a23065
Reviewed-on: http://gerrit.cloudera.org:8080/18108
Tested-by: Impala Public Jenkins <im...@cloudera.com>
Reviewed-by: Aman Sinha <am...@cloudera.com>


> The now_string option doesn't work in plannedstatement mode
> -----------------------------------------------------------
>
>                 Key: IMPALA-11062
>                 URL: https://issues.apache.org/jira/browse/IMPALA-11062
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Backend
>            Reporter: Steve Carlin
>            Priority: Major
>
> The "set now_string=<timestamp>" command isn't working properly when the query is being run through the ExecutePlannedStatement thrift API



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org