You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@impala.apache.org by "Yongjun Zhang (JIRA)" <ji...@apache.org> on 2018/09/13 20:28:00 UTC

[jira] [Resolved] (IMPALA-6442) Misleading file offset reporting in error messages

     [ https://issues.apache.org/jira/browse/IMPALA-6442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Yongjun Zhang resolved IMPALA-6442.
-----------------------------------
       Resolution: Fixed
    Fix Version/s: Impala 3.1.0

Many thanks to [~zi] for creating the jira, [~joemcdonnell], [~lv], and [~tarmstrong] for the review and commit.. Now it's in 3.1.0.


> Misleading file offset reporting in error messages
> --------------------------------------------------
>
>                 Key: IMPALA-6442
>                 URL: https://issues.apache.org/jira/browse/IMPALA-6442
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Backend
>    Affects Versions: Impala 2.11.0
>            Reporter: Zoltan Ivanfi
>            Assignee: Yongjun Zhang
>            Priority: Minor
>              Labels: parquet
>             Fix For: Impala 3.1.0
>
>
> {{HdfsParquetScanner::ProcessFooter}} has an error message "File $0 has invalid file metadata at file offset $1." However, the value reported as "file offset" is an offset from the _end_ of the file, not from its _beginning_. This is very misleading, since without explicitly stating that the offset is from the end, it is usually understood to be counted from the beginning.
> Additionally, although the function name is clearly about a "footer", two comments explicitly mention processing the "header". This falsely suggests that metadata is at the beginning of the file, when in reality it is at the end.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)