Hi all. We would downgrad Hive 1.2.1 to 0.13.0 ( I mean, after an HDP 2.3 installation we have Hive 1.2.1). Bacause , before with HDP 2.1 our job run fine and now, with HDP 2.3 we have errors. We are on Productions and the fast way imho is a simple downgrade only for HIVE. It's a good idea ? In order to downgrade I read : Downgrade Hive The Hive downgrade process reverses the upgrade process: Downgrade WebHCat Start the previous Hive Server 2 instance Deregister the new Hive Server 2 instance Downgrade Hive Metastore servers When finished, validate the downgrade process. It's correct ? Someone already tested ? Thanks ... View more

I need your help about a behavior about Hive 1.2.1 (on HDP 2.3) , after an upgrade from Hortonworks HDP 2.1 to HDP 2.3. To be honest , we don’t believe that this upgrade cause the issue . The “bug” is only for partitioned table when we use the partitioned field. Example : create table prova_small (campo1 string, campo2 string) partitioned by (campo3 int); alter table prova_small add partition (campo3 = 1); insert into prova_small partition (campo3=1) values ('a', 'b'); select distinct campo3 from prova_small; The error is : Container exited with a non-zero exit code 1 ]]], Vertex did not succeed due to OWN_TASK_FAILURE, failedTasks:1 killedTasks:0, Vertex vertex_1456148658200_0114_3_00 [Map 1] killed/failed due to:OWN_TASK_FAILURE]Vertex killed, vertexName=Reducer 2, vertexId=vertex_1456148658200_0114_3_01, diagnostics=[Vertex received Kill while in RUNNING state., Vertex did not succeed due to OTHER_VERTEX_FAILURE, failedTasks:0 killedTasks:1, Vertex vertex_1456148658200_0114_3_01 [Reducer 2] killed/failed due to:OTHER_VERTEX_FAILURE]DAG did not succeed due to VERTEX_FAILURE. failedVertices:1 killedVertices:1 Any idea ? Thanks ... View more