We have it working with security now that we put the hive-site.xml into Oozie's classpath :) thanks! On a related note, it would be easier configuration-wise if we didn't have to put this in the classpath and could add something to oozie-site.xml, similar to what we do for the hadoop confs. I had created OOZIE-1724 for this and I'll try to do it soon.
However, we do still see a minor issue (with and without security), that we were working around before. We're not using a JMS broker, but Oozie still seems to think that it will receive notifications from HCat. This is causing it to use the fallback polling (i.e. we have to wait 10min) instead of the regular polling (i.e. a 1min wait). I tried looking through the code and it appears that Oozie does this if it HCatClient has a topic name; is that the correct condition? We have not configured HCat for JMS notifications. Any ideas why this is happening? On Thu, Apr 17, 2014 at 9:42 AM, Mona Chitnis <[email protected]> wrote: > User does not need to pass the following properties in coordinator > job.properties. Thanks Venkat for mentioning about hive-site.xml in Oozie > class path. I¹d forgotten to mention that. That will contain these > following properties and Oozie will pick them up. Oozie communicates with > HCat server as super-user to find out about data partitions available. > > Robert, > > Can you copy here the thrift errors seen, if they aren¹t getting solved by > checking these properties? > > ‹ > Mona > > On 4/17/14, 8:50 AM, "Venkat Ranganathan" <[email protected]> > wrote: > > >hive.metastore.sasl.enabled=true > >hive.metastore.kerberos.principal=hive/<host>@<realm> > > > >
