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

Tim Armstrong updated IMPALA-8885:
----------------------------------
    Description: 
The error looks like this now:
{noformat}
File 'hdfs://nn/books/books1G.csv' has an invalid version number: .99 This 
could be due to stale metadata. Try running "refresh s3db.books_s3".
{noformat}

It seems to be reasonably common that this happens because a non-parquet file 
is being queried in a parquet table.

The error message should say something like "File 'hdfs://nn/books/books1G.csv' 
has an invalid Parquet version number: .99 and does not appear to be a valid 
Parquet file. This could be due to stale metadata. Try running "refresh 
s3db.books_s3"

  was:
The error looks like this now:
{noformat}
File 'hdfs://nn/books/books1G.csv' has an invalid version number: .99 This 
could be due to stale metadata. Try running "refresh s3db.books_s3".
{noformat}

It seems to be reasonably common that this happens because a non-parquet file 
is being queried in a parquet table.


> Improve parquet version metadata error
> --------------------------------------
>
>                 Key: IMPALA-8885
>                 URL: https://issues.apache.org/jira/browse/IMPALA-8885
>             Project: IMPALA
>          Issue Type: Improvement
>          Components: Backend
>            Reporter: Tim Armstrong
>            Assignee: Tim Armstrong
>            Priority: Major
>              Labels: supportability
>
> The error looks like this now:
> {noformat}
> File 'hdfs://nn/books/books1G.csv' has an invalid version number: .99 This 
> could be due to stale metadata. Try running "refresh s3db.books_s3".
> {noformat}
> It seems to be reasonably common that this happens because a non-parquet file 
> is being queried in a parquet table.
> The error message should say something like "File 
> 'hdfs://nn/books/books1G.csv' has an invalid Parquet version number: .99 and 
> does not appear to be a valid Parquet file. This could be due to stale 
> metadata. Try running "refresh s3db.books_s3"



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to