[
https://issues.apache.org/jira/browse/IMPALA-6993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Hecht resolved IMPALA-6993.
-------------------------------
Resolution: Fixed
Fix Version/s: Impala 3.1.0
Impala 2.13.0
> Don't print status stack trace when propagating thrift status in
> Coordinator::BackendState::Exec()
> --------------------------------------------------------------------------------------------------
>
> Key: IMPALA-6993
> URL: https://issues.apache.org/jira/browse/IMPALA-6993
> Project: IMPALA
> Issue Type: Improvement
> Components: Backend
> Affects Versions: Impala 3.0
> Reporter: Dan Hecht
> Assignee: Dan Hecht
> Priority: Major
> Fix For: Impala 2.13.0, Impala 3.1.0
>
>
> We should use Status::Expected() here, just like it's used above. The stack
> trace isn't interesting and the error is expected once we get down this path.
> (I'm not sure why we don't just use {{exec_status}} though, but presumably
> the prefix was added for a reason).
> {code:java}
> Status exec_status = Status(thrift_result.status);
> if (!exec_status.ok()) {
> const string& err_msg = Substitute(ERR_TEMPLATE, PrintId(query_id_),
> exec_status.msg().GetFullMessageDetails());
> VLOG_QUERY << err_msg;
> status_ = Status(err_msg);
> return;
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
