GitHub user manishgupta88 opened a pull request:
https://github.com/apache/carbondata/pull/1080 [CARBONDATA-1217] Failure in data load when we first load the bad record and then valid record and bad record action is set to Fail
Problem: Failure in data load when we first load the bad record and then valid record and bad record action is set to Fail
Analysis:
When we load bad record into the table and bad record action is set to "FAIL", then data load will fail. During load a bad record logger static map is maintained which holds the key for bad record. When data load fails due to bad record exception is thrown and key from bad record logger static map is not cleared because of which when valid data is loaded next time data load fails because the key still exists in the map.
Fix: Remove the bad record logger key from map even though data load fails.
You can merge this pull request into a Git repository by running:
$ git pull
https://github.com/manishgupta88/incubator-carbondata valid_invaid_record_load_fix
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/carbondata/pull/1080.patchTo close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1080
----
commit 27bcd05ee2f5a251dfc1617f044b0e9340b3ba64
Author: manishgupta88 <
[hidden email]>
Date: 2017-06-23T06:15:10Z
Problem: Failure in data load when we first load the bad record and then valid record and bad record action is set to Fail
Analysis:
When we load bad record into the table and bad record action is set to "FAIL", then data load will fail. During load a bad record logger static map is maintained which holds the key for bad record. When data load fails due to bad record exception is thrown and key from bad record logger static map is not cleared because of which when valid data is loaded next time data load fails because the key still exists in the map.
Fix: Remove the bad record logger key from map even though data load fails.
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at
[hidden email] or file a JIRA ticket
with INFRA.
---
Locked
