[
https://issues.apache.org/jira/browse/IMPALA-13252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17884119#comment-17884119
]
ASF subversion and git services commented on IMPALA-13252:
----------------------------------------------------------
Commit eea3594e96e3d3fc0cf9d07be651d686537aaf36 in impala's branch
refs/heads/master from Riza Suminto
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=eea3594e9 ]
IMPALA-13397: Use TUniqueIdUtil.PrintId in HeartbeatContext.toString
Impala begin to consistently use PrintId to print TUniqueId since
IMPALA-13252. This patch add one more PrintId in
HeartbeatContext.toString to pass
TestBannedLogMessage.test_no_tuniqueid.
Change-Id: Ic9395fab07b5f85342da692a350ca21ec502a1ea
Reviewed-on: http://gerrit.cloudera.org:8080/21840
Reviewed-by: Michael Smith <michael.sm...@cloudera.com>
Tested-by: Impala Public Jenkins <impala-public-jenk...@cloudera.com>
> Filter update log message prints TUniqueId in non-standard format
> -----------------------------------------------------------------
>
> Key: IMPALA-13252
> URL: https://issues.apache.org/jira/browse/IMPALA-13252
> Project: IMPALA
> Issue Type: Bug
> Components: Backend
> Affects Versions: Impala 4.4.0
> Reporter: Michael Smith
> Assignee: Michael Smith
> Priority: Major
> Fix For: Impala 4.5.0, Impala 4.4.1
>
>
> Some error messages, such as
> {code}
> Filter update received for non-executing query with id:
> TUniqueId(hi=-8482965541048796556, lo=3501357296473079808)
> {code}
> print query id as the raw Thrift type rather than our colon-delimited format,
> e.g. "8a4673c8fbe83a74:309751e900000000". This makes it difficult to trace
> queries through logs.
> Normalize on the colon-delimited format.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
