Hello @AHassan    Did you try increasing the hive tez container memory and see if this fixes your issue or not. After connecting to beeline, try checking the hive tez container size first using the below command SET hive.tez.container.size; Once found, try increase the container size to twice the current size. Lets say if you have the container size as 5 GB, then try setting to 10GB and re-run the query. SET hive.tez.container.size=10240MB  The reason I am asking to increase the container size is because I can see the attempts failing due to OOM.   If still the above fails, tune the below. tez.runtime.io.sort.mb should not be more than 2 GB (ideally it should be 40% of the tez container size)  tez.runtime.unordered.output.buffer.size-mb=1000 (ideally it should be 10% of the tez container size) ... View more

Hello @anujseeker    The best option to submit queries to hive is to use HIVESERVER2 and not hive cli. Hive cli is deprecated.   Coming to your main query as to you are unable to create database. You need check the hive cli logs present here (/tmp/<userid>/hive) to gather more info as why the path was not created and the Hive Metastore logs present here (/var/log/hive/). This is because hive cli (client) here talks directly to HMS and bypasses hiveserver2.   If you could share the details from hive cli log and HMS logs, it would be easier to further guide you through the next steps.   Regards, Tushar   https://cwiki.apache.org/confluence/display/Hive/LanguageManual+Cli ... View more

@avlasenko  It seems Impala is having trouble communicating with HMS.   Could you please check if you are able to perform the same from Hive? ... View more

@ateka_18    VIEW is just a query statement saved in HMS. So basically its the size of the table you gather and to do so, the best option is below.   hdfs dfs -ls <path of the table>   With regards to the error you are observing, it clearly says that analyze table is not supported for views. You can get the same for tables. ... View more

Hey @banshidhar_saho    Glad to hear it works.   regarding permission, it depends upon acl permissions you give. In the previous comment I had updated rwx for group. You can set it something for "other"   hdfs dfs -setfacl -m default:group:<group-name>:rwx <Path>   hdfs dfs -setfacl -m default:other::- <path>   Can you try the above and update if it works. ... View more

@pphot  Yes hdfs acls will come into picture even if you use Impala. After all Impala is a client for hdfs service.   If hdfs path has permissions, let's say no permission for impala user then impala will be unable to read data from hdfs and eventually your query will fail with permission denied error.   Let me know if the above clarifies your doubt. ... View more

@banshidhar_saho    This is the expected behavior as in Hadoop there are no groups based on user name. It does not use the OS level groups, instead it inherits it from parent directory. The reason is that group resolution happens on NameNode where groups related to the user may not exist.   To fix the case in your environment, modify the owner of the parent directory. This will cause new files to use the correct group. Run:-->hdfs dfs -chown -R username:groupname <PATH to DIR> This will recursively change the owner and group for the given <PATH>. (Note: do this with hdfs user)   You can further use acls' to ensure the groups you are trying have access to it.   hdfs dfs -setfacl -m default:group:<group-name>:rwx <Path>   Let me know if this helps ... View more

@drgenious    Could you please connect to impala-shell and submit the same query just to bee confirmed that the error is not from impala. ... View more