[
https://issues.apache.org/jira/browse/IMPALA-2210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18098285#comment-18098285
]
ASF subversion and git services commented on IMPALA-2210:
---------------------------------------------------------
Commit 848ef4735f49e9707456ffd0f0f2079f2e83414c in impala's branch
refs/heads/master from Peter Rozsa
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=848ef4735 ]
IMPALA-2210: Make Parquet the default file format
Change the default value of the DEFAULT_FILE_FORMAT query option from
TEXT to PARQUET. This affects all CREATE TABLE statements that do not
specify an explicit STORED AS clause, including plain CREATE TABLE,
CREATE TABLE AS SELECT, CREATE TABLE LIKE PARQUET, and CREATE TABLE
with CLUSTERED BY.
Change-Id: I46a5d16dfd780aae41623ebfc9742dfbd2a596ea
Assisted-by: Claude Sonnet 4.5 (OpenCode)
Reviewed-on: http://gerrit.cloudera.org:8080/24569
Tested-by: Impala Public Jenkins <[email protected]>
Reviewed-by: Zoltan Borok-Nagy <[email protected]>
> Make Parquet the default file format
> ------------------------------------
>
> Key: IMPALA-2210
> URL: https://issues.apache.org/jira/browse/IMPALA-2210
> Project: IMPALA
> Issue Type: Improvement
> Components: Frontend
> Affects Versions: Impala 2.2.4
> Reporter: John Russell
> Assignee: Peter Rozsa
> Priority: Blocker
> Labels: incompatibility, newbie, usability
>
> I expect that by far the most common use case for CREATE TABLE LIKE PARQUET
> is to make a table where the specified Parquet file will be queried. That
> is, either:
> CREATE TABLE foo LIKE PARQUET '/blah/blah/file.parq' STORED AS PARQUET;
> LOAD DATA INFILE '/blah/blah/file.parq' INTO TABLE foo;
> or
> CREATE EXTERNAL TABLE foo LIKE PARQUET '/blah/blah/file.parq' STORED AS
> PARQUET LOCATION '/blah/blah';
> I have difficulty imagining a case where someone would do CREATE TABLE LIKE
> PARQUET and want the result to be a text table. Even if someone planned to
> convert Parquet -> text, they would need to have a Parquet table to begin
> with, in which case they would do CREATE TABLE text_table LIKE parquet_table,
> not CREATE TABLE LIKE PARQUET.
> It is easy to leave off the STORED AS PARQUET clause by mistake from a CTLP
> statement, because PARQUET already occurs earlier in the statement, resulting
> in a text table that throws conversion errors when queried. How about making
> Parquet the default format in this case, and requiring the STORED AS clause
> only to use a different file format? (Then if Impala implemented a CREATE
> TABLE LIKE AVRO syntax, the default in that case would be Avro.)
> Since I guess this would qualify as an incompatible change, we would need to
> think through the appropriate release vehicle.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
