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.

CDH5 SerDe library 'org.apache.hadoop.hive.contrib.serde2.RegexSerDe' is not supported.

Solved Go to solution
Highlighted

CDH5 SerDe library 'org.apache.hadoop.hive.contrib.serde2.RegexSerDe' is not supported.

New Contributor

Hi Cloudera  People,

 

I am a beginner in Cloudera. I downloaded the VMQuickstart CDH5  and I try to do the tutorials but I can not finish the tutorial 3 because I have this error when I try to view in  Impala  the table " intermediate_access_logs"

 

Your query has the following error(s):

AnalysisException: Failed to load metadata for table: default.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.

 

Thansk for helping

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted

Re: CDH5 SerDe library 'org.apache.hadoop.hive.contrib.serde2.RegexSerDe' is not supported.

Master Collaborator
The intermediate_access_log table is not intended to be viewed directly,
especially not in Impala. In that tutorial step you're actually using Hive
to do an ETL (extract transform load) job. The Apache logs are in a format
that is hard to query directly through SQL, so we use one of Hive's
extensions to express a regular expression to break up the fields more
explicitly. After this step, the intermediate table is not useful. It's the
second table you create (tokenized_access_logs) that should be queried from
Impala.

View solution in original post

1 REPLY 1
Highlighted

Re: CDH5 SerDe library 'org.apache.hadoop.hive.contrib.serde2.RegexSerDe' is not supported.

Master Collaborator
The intermediate_access_log table is not intended to be viewed directly,
especially not in Impala. In that tutorial step you're actually using Hive
to do an ETL (extract transform load) job. The Apache logs are in a format
that is hard to query directly through SQL, so we use one of Hive's
extensions to express a regular expression to break up the fields more
explicitly. After this step, the intermediate table is not useful. It's the
second table you create (tokenized_access_logs) that should be queried from
Impala.

View solution in original post

Don't have an account?
Coming from Hortonworks? Activate your account here