You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@carbondata.apache.org by "Mohammad Shahid Khan (JIRA)" <ji...@apache.org> on 2017/06/23 06:57:00 UTC
[jira] [Updated] (CARBONDATA-1218) In case of data-load failure the
BadRecordsLogger.badRecordEntry map holding the task Status is not removing
the task Entry.
[ https://issues.apache.org/jira/browse/CARBONDATA-1218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mohammad Shahid Khan updated CARBONDATA-1218:
---------------------------------------------
Description:
In case of data-load failure the BadRecordsLogger.badRecordEntry map holding the task Status is not removing the task Entry.
Because of this the next load is getting failed even though the data being loaded has no bad records.
The map entry must be removed after load completion either success or fail.
was:
In case of data-load failure the BadRecordsLogger.badRecordEntry map holding the task Status is not removing the task Entry.
Because of this the next load is getting failed even though the data being loaded has no bad records.
> In case of data-load failure the BadRecordsLogger.badRecordEntry map holding the task Status is not removing the task Entry.
> ----------------------------------------------------------------------------------------------------------------------------
>
> Key: CARBONDATA-1218
> URL: https://issues.apache.org/jira/browse/CARBONDATA-1218
> Project: CarbonData
> Issue Type: Bug
> Reporter: Mohammad Shahid Khan
> Assignee: Mohammad Shahid Khan
>
> In case of data-load failure the BadRecordsLogger.badRecordEntry map holding the task Status is not removing the task Entry.
> Because of this the next load is getting failed even though the data being loaded has no bad records.
> The map entry must be removed after load completion either success or fail.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)