[
https://issues.apache.org/jira/browse/HDFS-17791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18019963#comment-18019963
]
ASF GitHub Bot commented on HDFS-17791:
---------------------------------------
github-actions[bot] commented on PR #7696:
URL: https://github.com/apache/hadoop/pull/7696#issuecomment-3287231089
We're closing this stale PR because it has been open for 100 days with no
activity. This isn't a judgement on the merit of the PR in any way. It's just a
way of keeping the PR queue manageable.
If you feel like this was a mistake, or you would like to continue working
on it, please feel free to re-open it and ask for a committer to remove the
stale tag and review again.
Thanks all for your contribution.
> libhdfs client error message for "file not found" includes lengthy, unneeded
> stack trace
> ----------------------------------------------------------------------------------------
>
> Key: HDFS-17791
> URL: https://issues.apache.org/jira/browse/HDFS-17791
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: libhdfs
> Affects Versions: 3.3.6
> Reporter: Carl Vuosalo
> Priority: Minor
> Labels: pull-request-available
>
> The {{libhdfs}} client outputs a full Java stack trace in its error message
> for a "file not found" error when trying to open a non-existent file. Our
> HDFS application processes numerous queries checking for the presence of
> files, so "file not found" errors are frequent. Each such error generates a
> very lengthy and useless Java stack trace. These traces have no diagnostic
> value, since the cause of the error is that the file doesn't exist.
> A fix for this problem is proposed by pull request
> [#7696|https://github.com/apache/hadoop/pull/7696],
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
