Hello,
For your query, pre-partitioning is performed on if() expressions. Since
the output of if() expressions is skewed, the resultant query plan is
inefficient.
We think that the pre-partitioning columns should be restricted to those
found in grouping sets (which I think is the case in Trino).
Hi Denys,
Thanks so much for looking into this . I have filed below JIRA for this
issue
https://issues.apache.org/jira/browse/HIVE-28567
Thanks,
Ratnesh
On Wed, Oct 9, 2024 at 1:45 PM Denys Kuzmenko wrote:
> Hi Ratnesh,
>
> Thanks for reporting the issue. Would you be able to create a JIRA tick
Hi.
It's great to see this article. This indicates that since Hive 4.0, downstream
vendors of the Hive project have also started to become more active. For the
project's activity, this is a good thing. It shows that more and more
developers and users are starting to try version 4.0.
Back to
Hi everyone,
We have published a blog article that reports the performance improvement
from three patches HIVE-28488, HIVE-28489, and HIVE-28490 which we
submitted some time ago. It evaluates Hive 4.0.1 on MR3 and Trino 453 on
the 10TB TPC-DS benchmark, but the results could be useful to users of
Hi Ratnesh,
Thanks for reporting the issue. Would you be able to create a JIRA ticket with
the same?
I did a quick search and found escape chars being added only in case of direct
SQL [1]
{code}
// The following syntax is required for using LIKE clause wildcards '_'
and '%' as literals.
