-
Notifications
You must be signed in to change notification settings - Fork 393
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
hive3.1.2 on hadoop 3.2.1 JsonSerDe #225
Comments
can you attach files with the table definition and the sample data that causes the error ? The create table is garbled and without the data you're running I can't reproduce the error. |
I can hit this issue as well. This is likely an incompatibility issue with Hive 3.x due to some model change in the hive timestamp object. I can repro with the follow statement and running on Hive version 3.1.2
|
thanks, I'll have a look |
load json type data
use JsonSerDe(1.3.8)
CREATE EXTERNAL TABLE
test001
(e
string COMMENT 'from deserializer',p
string COMMENT 'from deserializer',t
timestamp COMMENT 'from deserializer',app
string COMMENT 'from deserializer')PARTITIONED BY (
dt
string)ROW FORMAT SERDE
'org.openx.data.jsonserde.JsonSerDe'
WITH SERDEPROPERTIES (
'ignore.malformed.json'='true')
STORED AS TEXTFILE;
there'not any problem when load data to hive;
but I get a issues exception msg on running SQL(select t from test001).
the exception msg is :
Exception in thread "main" java.lang.AbstractMethodError: Method org/openx/data/jsonserde/objectinspector/primitive/JavaStringTimestampObjectInspector.getPrimitiveWritableObject(Ljava/lang/Object;)Lorg/apache/hadoop/hive/serde2/io/TimestampWritableV2; is abstract
at org.openx.data.jsonserde.objectinspector.primitive.JavaStringTimestampObjectInspector.getPrimitiveWritableObject(JavaStringTimestampObjectInspector.java)
at org.apache.hadoop.hive.serde2.lazy.LazyUtils.writePrimitiveUTF8(LazyUtils.java:308)
at org.apache.hadoop.hive.serde2.lazy.LazySimpleSerDe.serialize(LazySimpleSerDe.java:292)
at org.apache.hadoop.hive.serde2.lazy.LazySimpleSerDe.serializeField(LazySimpleSerDe.java:247)
there is no problem when run SQL(select p from test001).
The text was updated successfully, but these errors were encountered: