[jira] [Created] (HIVE-25854) Port Iceberg Hive fix - ORC vectorization fails after split offsets are considered during split generation
Ádám Szita created HIVE-25854:
-
Summary: Port Iceberg Hive fix - ORC vectorization fails after
split offsets are considered during split generation
Key: HIVE-25854
URL: https://issues.apache.org/jira/browse/HIVE-25854
Project: Hive
Issue Type: Bug
Reporter: Ádám Szita
Assignee: Ádám Szita
Porting Iceberg commit:
{code:java}
339866d72784a3e90625037d3a9de4fdafc5fcef
Hive: ORC vectorization fails when split offsets are considered during split
generation (#3748 {code}
.. to fix issue with reading non-first splits of ORC files in vectorized mode
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (HIVE-25853) Security Vulnerability CVE-2021-44832 log4j2 upgrade to 2.17.1
GuangMing Lu created HIVE-25853: --- Summary: Security Vulnerability CVE-2021-44832 log4j2 upgrade to 2.17.1 Key: HIVE-25853 URL: https://issues.apache.org/jira/browse/HIVE-25853 Project: Hive Issue Type: Improvement Affects Versions: 4.0.0 Reporter: GuangMing Lu Security Vulnerability CVE-2021-44832 log4j2 upgrade to 2.17.1 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (HIVE-25852) Introduce IN clauses at the very end of query planning
Alessandro Solimando created HIVE-25852: --- Summary: Introduce IN clauses at the very end of query planning Key: HIVE-25852 URL: https://issues.apache.org/jira/browse/HIVE-25852 Project: Hive Issue Type: Bug Components: CBO Affects Versions: 4.0.0 Reporter: Alessandro Solimando Calcite "explodes" IN clauses into the equivalent OR form, and therefore it does not handle such clauses in most of the codebase (notably in _RexSimplify_). In Hive, the same happens, but _HivePointLookupOptimizerRule_ re-introduces IN clauses, and it happens in _applyPreJoinOrderingTransforms_ phase, which is pretty early and which mixes several other rules which might not fully support IN (notably, _HiveReduceExpressionsRule_ which is based on _RexSimplify_). The problem will become even harder in later versions of Calcite (current is 1.25) based on SARG, which does not support IN clauses. IN clauses can be converted into efficient runtime operators, we therefore want to keep them in the final plan, intuitively we just want this translation to happen in a later step, in order to leave the rest of the codebase (Hive and Calcite) unaware of IN clauses. The goal of the ticket is as follows: # re-convert the output expression of _HivePointLookupOptimizerRule_ into the OR form (keep the logic as-is to benefit from the rule) # add a rule, in the last step of the planning process, that only converts eligible OR expressions into IN clauses -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (HIVE-25851) Replace HiveRelMdPredicate with RelMdPredicate from Calcite
Alessandro Solimando created HIVE-25851: --- Summary: Replace HiveRelMdPredicate with RelMdPredicate from Calcite Key: HIVE-25851 URL: https://issues.apache.org/jira/browse/HIVE-25851 Project: Hive Issue Type: Improvement Components: CBO Affects Versions: 4.0.0 Reporter: Alessandro Solimando `HiveRelMdPredicates` was copied from `RelMdPredicates` in Calcite long ago, it has few differences which could be ported to the Calcite version, if needed. The goal of the ticket is to: # ascertain which are the additional features in `HiveRelMdPredicates`, port them to Calcite if needed # drop `HiveRelMdPredicates` in favour of `RelMdPredicates` in order to benefit from all the advances in such class -- This message was sent by Atlassian Jira (v8.20.1#820001)
