GitHub user manishgupta88 opened a pull request:
https://github.com/apache/carbondata/pull/904
[CARBONDATA-1045] Mismatch in message display with insert and load
operation on failure due to bad records in update operation
Problem: When bad records action is set to fail and any IUD operation⦠is
executed and it fails due to bad records error message is not displayed
correctly because of which user is not clear with the cause of update operation
failure. Whereas in the same case in other operations like data load and insert
into, if there is any failure due to bad record proper error message is
displayed to the user for failure due to bad record.
Fix: Instead of forming own message get the executor failure message and
send it to update operation as exception message.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/manishgupta88/incubator-carbondata
IUD_bad_record_message
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/carbondata/pull/904.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #904
----
commit 822363f56cf9e79a6f7673b86b5afb3147a98bbc
Author: manishgupta88 <[email protected]>
Date: 2017-05-10T13:46:31Z
Problem: When bad records action is set to fail and any IUD operation is
executed and it fails due to bad records error message is not displayed
correctly because of which user is not clear with the cause of update operation
failure. Whereas in the same case in other operations like data load and insert
into, if there is any failure due to bad record proper error message is
displayed to the user for failure due to bad record.
Fix: Instead of forming own message get the executor failure message and
send it to update operation as exception message.
----
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
