Hi All,
Can someone look into this and revert if possible?
Thanks.
On Thu, 12 Jul 2018 12:56 Anup Tiwari, wrote:
> Hi All,
>
> We have a use case where we want to assign a row number to a table based
> on 3 column ( uid, update_date, flag) i.e. if value of any of the column
> gets changed, we
> I'm using Hive 1.2.1 with LLAP on HDP 2.6.5. Tez AM is 3GB, there are 3
> daemons for a total of 34816 MB.
Assuming you're using Hive2 here (with LLAP) and LLAP kinda sucks for ETL
workloads, but this is a different problem.
> PARTITIONED BY (DATAPASSAGGIO string, ORAPASSAGGIO string)
> CLU
Hello Sungwoo!
I think its possible that reoptimization is kicking in, because the first
execution have bumped into an exception.
I think the plans should not be changing permanently; unless
"hive.query.reexecution.stats.persist.scope" is set to a wider scope than query.
To check that indeed