-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
sql cannot run using Presto, but can run using hive, when the type of column in orc file doesn't match the type defined in hive table #3679
Comments
Could you try Also, I would suggest you join the community Slack |
|
(For @Xuchaojing can you provide the full error stacktrace with and without |
in order to protect the security of the information, I changed the name of the table. change the real name to "abc". CREATE TABLE `ods.abc`(
`id` bigint,
`identifier` string,
`identifier_md5` string,
`channel` bigint,
`os_version` bigint,
`request_url` string)
COMMENT 'abc'
PARTITIONED BY (
`pt` string COMMENT 'full_partition')
ROW FORMAT SERDE
'org.apache.hadoop.hive.ql.io.orc.OrcSerde'
WITH SERDEPROPERTIES (
'field.delim'='\u0001',
'line.delim'='\n',
'serialization.format'='\u0001')
STORED AS INPUTFORMAT
'org.apache.hadoop.hive.ql.io.orc.OrcInputFormat'
OUTPUTFORMAT
'org.apache.hadoop.hive.ql.io.orc.OrcOutputFormat'
LOCATION
'hdfs://testHadoop/dataware/ods/abc'
TBLPROPERTIES (
'transient_lastDdlTime'='1574322027') the full error stacktrace when run sql using presto: |
@Xuchaojing You can get the full stactrace by |
this is the full stacktrace, and the version of the prestosql i used is 317.
|
@Xuchaojing Could you share two kinds of full stacktrace with:
|
the error stack is the same, whether true or false. |
Let's continue in this Slack thread https://prestosql.slack.com/archives/CGB0QHWSW/p1589011535253100 |
I think this is because the ORC reader that Hive uses converts the data type from |
Query 20200509_032316_00682_9pmv8 failed: Error opening Hive split hdfs://xxxxxxx (offset=33554432, length=33554432): Malformed ORC file. Can not read SQL type bigint from ORC stream .id of type STRING
so is it any suggestion about this issue?
The text was updated successfully, but these errors were encountered: