[HIVE-8739] handle Derby and Oracle errors with joins and filters in Direct SQL in a invalid-DB-specific path

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.0.0
• Component/s: Metastore
• Assignee: Sergey Shelukhin
• Reporter: Sergey Shelukhin
• Created: 05/Nov/14 02:00
• Updated: 28/Sep/22 11:34
• Resolved: 15/Nov/14 16:27

Issue Links

• is related to: HIVE-10296 Cast exception observed when hive runs a multi join query on metastore (postgres), since postgres pushes the filter into the join, and ignores the condition before applying cast
• relates to: DERBY-6358 WHERE clause should be evaluated after the joins in the FROM clause
• relates to: HIVE-25965 SQLDataException when obtaining partitions from HMS via direct SQL over Derby
• relates to: DERBY-7132 SQLDataException when executing CAST inside a CASE WHEN clause
• supercedes: HIVE-8293 Metastore direct SQL failed for Oracle becasue ORA-01722: invalid number