[
https://issues.apache.org/jira/browse/HIVE-22357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesus Camacho Rodriguez updated HIVE-22357:
-------------------------------------------
Fix Version/s: 4.0.0
Resolution: Fixed
Status: Resolved (was: Patch Available)
Pushed to master, thanks [~Rajkumar Singh]!
> Schema mismatch between the Hive table definition and the "hive.sql.query"
> Parameter
> ------------------------------------------------------------------------------------
>
> Key: HIVE-22357
> URL: https://issues.apache.org/jira/browse/HIVE-22357
> Project: Hive
> Issue Type: Improvement
> Components: Hive, HiveServer2
> Affects Versions: 3.1.0
> Reporter: Krishnadevan Purushothaman
> Assignee: Rajkumar Singh
> Priority: Critical
> Fix For: 4.0.0
>
> Attachments: HIVE-22357.patch, Hive-JDBC schema matching
> sensitivity.txt
>
>
> The problem is that, for certain types of schema mismatch between the Hive
> table definition and the "hive.sql.query" parameter, Hive simply returns no
> rows rather than throwing an error when queried.
> Ideally Hive would check for schema compatibility during table definition and
> throw an error if there's a problem - the earlier the better. But even if
> that cannot be made a requirement, I'd definitely expect an error rather than
> a silent failure (i.e. zero rows returned) at runtime.
> I'm attaching investigation of this issue in "Hive-JDBC schema matching
> sensitivity.txt".
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
