Hi all, Just to include the environmental info: - Bigtop 3.2.0 with MPACK in the distribution - Hive from the above MPACK - Ranger 2.4.0 that I downloaded, compiled and installed stand alone without using Ambari (which is not in the MPACK)
I triggered the update hive script in BGTP which tried to read a config file in the old format (I think for RANGER 0.7.0) Can anyone please help. Keng On Mon, Aug 28, 2023 at 5:36 PM bigtapp_root_aws quek < [email protected]> wrote: > Hi All, > I've installed a cluster using Bigtop's binary distribution and deployed > using its Ambari. > > As Ranger 2.4 is not in the repo, I had compiled and am deploying it > independently. However, I've encountered a serious issue when I was > deploying the Hive plugin for Ranger. It basically called BGTP files in > Amabri agent and looked even in looked for RANGER entries with the > configuration. > > The error file is attached. I don't understand a) why does my Ranger > plugin gets entangled in Ambari installation when Ranger is not even > distributed with Bigtop. b) why call for admin-properties in the > configuration in RANGER/0.5.0 or 0.7.1 when Ranger is now v2.4, not > included with Bigtop, not deployed by Ambari. > > Does any one have a solution to resolve this issue? > > > Keng >
