[ 
https://issues.apache.org/jira/browse/IMPALA-10627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17386461#comment-17386461
 ] 

ASF subversion and git services commented on IMPALA-10627:
----------------------------------------------------------

Commit 0061bd3433db5b72b6c6bf2f6646255272976cda in impala's branch 
refs/heads/master from Attila Jeges
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=0061bd3 ]

IMPALA-10820: Fix calculating default block size for parquest files

This patch fixes a bug introduced in IMPALA-10627. Because of the bug
the wrong default block size was used for parquet files which broke
TestInsertWideTable.test_insert_wide_table e2e test.

Testing:
- Run test_insert_wide_table with exhaustive strategy.

Change-Id: Iac8c6dd80dfe84cb7b3d2106713eae87ce923934
Reviewed-on: http://gerrit.cloudera.org:8080/17719
Reviewed-by: Zoltan Borok-Nagy <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>


> Use standard Iceberg table properties
> -------------------------------------
>
>                 Key: IMPALA-10627
>                 URL: https://issues.apache.org/jira/browse/IMPALA-10627
>             Project: IMPALA
>          Issue Type: Bug
>            Reporter: Zoltán Borók-Nagy
>            Assignee: Attila Jeges
>            Priority: Major
>              Labels: impala-iceberg
>
> Iceberg lists the following properties:
> [https://iceberg.apache.org/configuration/]
> We should also use these properties if possible, e.g. write.format.default, 
> write.<fileformat>.compression-codec
> Currently Impala use the table property 'iceberg.file_format' to determine 
> the data file format for reads/writes. In the future, read operations should 
> automatically detect the file formats (IMPALA-10610), but for writes we 
> should use 'write.format.default'.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

Reply via email to