[
https://issues.apache.org/jira/browse/IMPALA-6985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16467389#comment-16467389
]
Balazs Jeszenszky commented on IMPALA-6985:
-------------------------------------------
Looking at the Hive-side jira, I don't think Impala should be fixing this as
it's within specification and it would add overhead (by having to keep these
fields up to date).
> Impala View Does Not Populate Table Input/Output Format Class
> -------------------------------------------------------------
>
> Key: IMPALA-6985
> URL: https://issues.apache.org/jira/browse/IMPALA-6985
> Project: IMPALA
> Issue Type: Improvement
> Components: Catalog
> Reporter: BELUGA BEHR
> Priority: Major
>
> When a view is created in Impala, the InputFormat and OutputFormat fields are
> set to NULL. This is breaking some aspects of Hive. See: [HIVE-19424].
> Perhaps Impala can play nice here and set these fields the same as Hive.
> {code:sql}
> -- hive
> CREATE VIEW test_view_hive AS select * from sample_07;
> -- impala
> CREATE VIEW test_view_impala AS select * from sample_07;
> {code}
> {code:sql}
> -- Impala
> DESCRIBE extended test_view_impala;
> InputFormat - (blank)
> OutputFormat - (blank)
> DESCRIBE extended test_view_hive;
> InputFormat - org.apache.hadoop.mapred.TextInputFormat
> OutputFormat - org.apache.hadoop.hive.ql.io.HiveIgnoreKeyTextOutputFormat
> {code}
> You can see the difference in the Hive Metastore.
> {code}
> MariaDB [hive1]> SELECT TBLS.TBL_NAME FROM TBLS JOIN SDS ON
> TBLS.SD_ID=SDS.SD_ID WHERE SDS.INPUT_FORMAT IS NULL;
> +------------------+
> | TBL_NAME |
> +------------------+
> | test_view_impala |
> +------------------+
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
