Hi: Ranger usersync syncs users from various sources to make these users available during security policy authoring via Ranger UI. At the time of resource access, enforcement of policies is performed by Ranger plugins which depend on the actual service (for example HiveServer2 in case of Hive plugin, HDFS Namenode in case of HDFS plugin) to pass the identity of the user and the groups they belong to. To answer your question, sync source used for ranger usersync does not really affect the actual access enforcement. As long as the users in your text file are consistent with the real user source (LDAP/Unix or AD), ranger policies will work fine. Hope this helps. ... View more

@PJ Yes, its the same even for Userid's but make sure that user doesn't belongs to any other groups. Even if he belongs the 1st policy will get higher priority. Hope this helps. ... View more

Hi @PJ, the honest truth is there is no good reason not to use ORC format. You can use another format like Parquet but it won't provide ACID, LLAP cache, or the same level of performance. I would say the decision is similar to not using indexes in a relational system or not running statistics. ORC is simply best practice for high performance data warehousing in Hive. Keep in mind that LLAP will allow you to cache raw text files. This may be an option if you have some strict SLA preventing you from incurring the conversion delay of the text file to ORC. ... View more