[
https://issues.apache.org/jira/browse/CARBONDATA-3980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
SHREELEKHYA GAMPA updated CARBONDATA-3980:
------------------------------------------
Description:
When the partition column is loaded with a bad record value, load fails with 'Job aborted' message in cluster. However in complete stack trace we can see the actual error message. ('Data load failed due to bad record: The value with column name projectjoindate and column data type TIMESTAMP is not a valid TIMESTAMP type')
Bug id: BUG2020082802430
PR link:
https://github.com/apache/carbondata/pull/3919 was:
When the partition column is loaded with a bad record value, load fails with 'Job aborted' message in cluster. However in complete stack trace we can see the actual error message. ('Data load failed due to bad record: The value with column name projectjoindate and column data type TIMESTAMP is not a valid TIMESTAMP type')
Bug id: BUG2020082802430
Remaining Estimate: (was: 0h)
> Load fails with aborted exception when Bad records action is unspecified
> ------------------------------------------------------------------------
>
> Key: CARBONDATA-3980
> URL:
https://issues.apache.org/jira/browse/CARBONDATA-3980> Project: CarbonData
> Issue Type: Bug
> Reporter: SHREELEKHYA GAMPA
> Priority: Minor
> Time Spent: 10m
>
> When the partition column is loaded with a bad record value, load fails with 'Job aborted' message in cluster. However in complete stack trace we can see the actual error message. ('Data load failed due to bad record: The value with column name projectjoindate and column data type TIMESTAMP is not a valid TIMESTAMP type')
> Bug id: BUG2020082802430
> PR link:
https://github.com/apache/carbondata/pull/3919--
This message was sent by Atlassian Jira
(v8.3.4#803005)
Locked
