For others who are using CM, you can go to CM > Hive > Configuration > Hive Service Advanced Configuration Snippet (Safety Valve) for hive-site.xml then enter the new property name and value, save and restart Hive ... View more

Did you use Hue to query Impala? Did you actually experience query took 4.8 hours to return the result, or did you just noticed the start and end time from query profile that is long? Hue does not close query handler after query finishes so that users can still retrieve result later on. This time while query handler is open until closed will be counted towards the query start and end time in the profile. ... View more

Hi Matthieu, Are you able to share query PROFILE and enable ODBC driver TRACE logs so that we can see the error in more detail, both from client and server side? ... View more

For ODBC related query failure, the info we can check are: 1. Impala query PROFILE, to understand which step failed 2. Impala coordinator log, using the query_id from PROFILE and see where it failed 3. enable TRACE logs on ODBC driver, to see if there is any client side errors : https://www.cloudera.com/documentation/other/connectors/impala-odbc/latest/Cloudera-ODBC-Driver-for-Impala-Install-Guide.pdf search for LogLevel section. In Windows ODBC driver, normally under "Logging Options" button on the configuration window. ... View more

If "set parquet.column.index.access=true", this means the names of the columns in Parquet data is different compared with the columns defined in Hive. The workaround is to set this at the table level: ALTER TABLE parquet_table SET TBLPROPERTIES ('parquet.column.index.access'='true'); Hope above can help. ... View more

Couple of questions to understand the issue a bit more: 1. did you insert the data using Impala or hive? 2. did SELECT * from Hive works OK? 3. when query is running, do you see any warning or error messages from HS2 log? 4. Have you tried to remove some conditions to see if some of them might be the cause of the issue? 5. What version of CDH are you using? Thanks ... View more

Thanks for sharing!! ... View more

The point of sentry is to only allow users with specific permission to access certain things. To do that, sentry needs to manage everything by itself, not by end users. This is why we need to make the hive warehouse to be owned by "hive:hive" and 771, so that no end users can modify anything that hive and sentry control. Enabling impersonation will make the end user to create files owned by them, which makes "hive" user not able to manage those files/directories and user has direct access to them. That will break what sentry is designed to do. Hope above makes sense. Cheers ... View more