Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

Tutorial Exercise 2: select * from intermediate_access_logs not working as expected, why?

Solved Go to solution

Tutorial Exercise 2: select * from intermediate_access_logs not working as expected, why?

Explorer

In Hive query editor, it shows "The operation has no results.".

In Impala, it shows:

Your query has the following error(s):

AnalysisException: Failed to load metadata for table: 'intermediate_access_logs' CAUSED BY: TableLoadingException: Failed to load metadata for table: intermediate_access_logs CAUSED BY: InvalidStorageDescriptorException: Impala does not support tables of this type. REASON: SerDe library 'org.apache.hadoop.hive.contrib.serde2.RegexSerDe' is not supported.

 

Thanks.

1 ACCEPTED SOLUTION

Accepted Solutions

Re: Tutorial Exercise 2: select * from intermediate_access_logs not working as expected, why?

Explorer

I repeated the process and it works now, but the last script is showing no result, I will open a different post for that.

3 REPLIES 3

Re: Tutorial Exercise 2: select * from intermediate_access_logs not working as expected, why?

Explorer

I double checked and confirmed the log exists in hdfs:

 

[cloudera@quickstart examples]$ hadoop fs -ls /user/hive/warehouse/original_access_logs
Found 1 items
-rw-r--r-- 1 hdfs supergroup 39593868 2016-05-28 06:23 /user/hive/warehouse/original_access_logs/access.log.2

 

 

Re: Tutorial Exercise 2: select * from intermediate_access_logs not working as expected, why?

Explorer

I repeated the process and it works now, but the last script is showing no result, I will open a different post for that.

Re: Tutorial Exercise 2: select * from intermediate_access_logs not working as expected, why?

Master Collaborator
intermediate_access_logs was created as part of the ETL process in the
tutorial. That process is done via Hive because it uses Hive SerDe's and
other Hive-only features. The final table created in that process
(tokenized_access_logs, if I remember correctly) is the one you should be
able to query in Impala. Also, don't forget to 'invalidate metadata' when
the ETL process is finished, since Impala doesn't cache metadata.