[
https://issues.apache.org/jira/browse/IMPALA-14635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18046373#comment-18046373
]
ASF subversion and git services commented on IMPALA-14635:
----------------------------------------------------------
Commit 6649b92cb2fe1d90b537af19b9fb76afcc473fbf in impala's branch
refs/heads/master from Zoltan Borok-Nagy
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=6649b92cb ]
IMPALA-14635: We should not check for exact file sizes in
iceberg-metadata-tables.test
The Impala version string is written into the Parquet footer. This
means in our tests we shouldn't check for exact file sizes of tables
written during data loading/testing.
Change-Id: I589ade5f81879ede54ff41466b77b5db3349a14f
Reviewed-on: http://gerrit.cloudera.org:8080/23802
Reviewed-by: Impala Public Jenkins <[email protected]>
Reviewed-by: Riza Suminto <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>
> We should not check for exact file sizes in iceberg-metadata-tables.test
> -------------------------------------------------------------------------
>
> Key: IMPALA-14635
> URL: https://issues.apache.org/jira/browse/IMPALA-14635
> Project: IMPALA
> Issue Type: Bug
> Components: Test
> Reporter: Zoltán Borók-Nagy
> Assignee: Zoltán Borók-Nagy
> Priority: Major
> Labels: impala-iceberg
>
> We should not check for exact file sizes in iceberg-metadata-tables.test
> We have the following check right now:
>
> {noformat}
> ---- QUERY
> select * from functional_parquet.iceberg_query_metadata.`partitions`;
> ---- RESULTS
> 3,3,1053,1,1,0,0,regex:.*,regex:\d+rmatting_ is done here{noformat}
> 1053 corresponds to total_data_file_size_in_bytes. This can be different when
> the Impala version string is stored in the Parquet files (e.g. SNAPSHOT vs
> RELEASE have different lengths).
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
