hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <>
Subject [jira] [Commented] (HIVE-5199) Custom SerDe containing a nonSettable complex data type row object inspector throws cast exception with HIVE 0.11
Date Thu, 05 Sep 2013 14:37:51 GMT


Hive QA commented on HIVE-5199:

{color:red}Overall{color}: -1 at least one tests failed

Here are the results of testing the latest attachment:

{color:red}ERROR:{color} -1 due to 6 failed/errored test(s), 2910 tests executed
*Failed tests:*

Test results:
Console output:

Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
Tests failed with: TestsFailedException: 6 tests failed

This message is automatically generated.
> Custom SerDe containing a nonSettable complex data type row object inspector throws cast
exception with HIVE 0.11
> -----------------------------------------------------------------------------------------------------------------
>                 Key: HIVE-5199
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>    Affects Versions: 0.11.0
>            Reporter: Hari Sankar Sivarama Subramaniyan
>            Assignee: Hari Sankar Sivarama Subramaniyan
>            Priority: Critical
>         Attachments: CustomSerDes.jar, HIVE-5199.2.patch.txt, HIVE-5199.patch.txt
> The issue happens because of the changes in HIVE-3833.
> Consider a partitioned table with different custom serdes for the partition and tables.
The serde at table level, say, customSerDe1's object inspector is of settableDataType where
as the serde at partition level, say, customSerDe2's object inspector is of nonSettableDataType.
The current implementation introduced by HIVE-3833 does not convert nested Complex Data Types
which extend nonSettableObjectInspector to a settableObjectInspector type inside ObjectInspectorConverters.getConvertedOI().
However, it tries to typecast the nonSettableObjectInspector to a settableObjectInspector
inside  ObjectInspectorConverters.getConverter(ObjectInspector inputOI, ObjectInspector outputOI).
> The attached patch HIVE-5199.2.patch.txt contains a stand-alone test case.
> The below exception can happen via FetchOperator as well as MapOperator. 
> For example, consider the FetchOperator.
> Inside FetchOperator consider the following call:
> getRecordReader()->ObjectInspectorConverters. getConverter()
> The stack trace as follows:
> 2013-08-28 17:57:25,307 ERROR CliDriver ( - Failed
with exception
cannot be cast to org.apache.hadoop.hive.serde2.objectinspector.SettableMapObjectInspector
> java.lang.ClassCastException:
cannot be cast to org.apache.hadoop.hive.serde2.objectinspector.SettableMapObjectInspector
> at org.apache.hadoop.hive.ql.exec.FetchOperator.getNextRow(
> at org.apache.hadoop.hive.ql.exec.FetchOperator.pushRow(
> at org.apache.hadoop.hive.ql.exec.FetchTask.fetch(
> at org.apache.hadoop.hive.ql.Driver.getResults(
> at org.apache.hadoop.hive.cli.CliDriver.processLocalCmd(
> at org.apache.hadoop.hive.cli.CliDriver.processCmd(
> at org.apache.hadoop.hive.cli.CliDriver.processLine(
> at
> at org.apache.hadoop.hive.cli.CliDriver.main(
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(
> at java.lang.reflect.Method.invoke(
> at org.apache.hadoop.util.RunJar.main(
> Caused by: java.lang.ClassCastException:
cannot be cast to org.apache.hadoop.hive.serde2.objectinspector.SettableMapObjectInspector
> at org.apache.hadoop.hive.serde2.objectinspector.ObjectInspectorConverters.getConverter(
> at org.apache.hadoop.hive.serde2.objectinspector.ObjectInspectorConverters$StructConverter.<init>(
> at org.apache.hadoop.hive.serde2.objectinspector.ObjectInspectorConverters.getConverter(
> at org.apache.hadoop.hive.ql.exec.FetchOperator.getRecordReader(
> at org.apache.hadoop.hive.ql.exec.FetchOperator.getNextRow(

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message