https://community.cloudera.com/t5/Support-Questions/quot-Error-parsing-row-file-quot-Table-consists-of-multiple/m-p/287896#M213309 <P>The error "<SPAN>Error converting column: 35 to TIMESTAMP" means there was an error when converting column 35 to the TIMESTAMP type.</SPAN></P><P>&nbsp;</P><P><SPAN>The error "Error parsing row: file: hdfs://blabla/foo_042019.csv, before offset: 2432696320" means there was an error while parsing the row at file offset&nbsp;2432696320, in the file&nbsp;foo_042019.csv.</SPAN></P><P>&nbsp;</P><P><SPAN>So it looks like there are several rows in your dataset where certain fields cannot be converted to TIMESTAMPs. You should be able to open up the file, and seek to the specified offset to find the rows that are corrupted.</SPAN></P><P>&nbsp;</P><P><SPAN>I believe, Hive does not throw an exception when given the same dataset, instead it converts the corrupted rows to NULL. The same behavior can be emulated in Impala by setting 'abort_on_error=false'. However, be warned that setting this option can mask data corruption issues. See&nbsp;<A href="https://impala.apache.org/docs/build/html/topics/impala_abort_on_error.html" target="_blank">https://impala.apache.org/docs/build/html/topics/impala_abort_on_error.html</A>&nbsp;for details.</SPAN></P> Fri, 17 Jan 2020 23:48:00 GMT SahilTakiar 2020-01-17T23:48:00Z