Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id C3C34200C80 for ; Thu, 11 May 2017 06:12:08 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id C143D160BB4; Thu, 11 May 2017 04:12:08 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 1ED3B160BC6 for ; Thu, 11 May 2017 06:12:07 +0200 (CEST) Received: (qmail 24279 invoked by uid 500); 11 May 2017 04:12:07 -0000 Mailing-List: contact issues-help@carbondata.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@carbondata.apache.org Delivered-To: mailing list issues@carbondata.apache.org Received: (qmail 24263 invoked by uid 99); 11 May 2017 04:12:07 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 11 May 2017 04:12:07 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id E11DA1A00CE for ; Thu, 11 May 2017 04:12:06 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id T_CGm_HsU3CF for ; Thu, 11 May 2017 04:12:06 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 76CB25F567 for ; Thu, 11 May 2017 04:12:05 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 91A02E0942 for ; Thu, 11 May 2017 04:12:04 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 18E7C21E0B for ; Thu, 11 May 2017 04:12:04 +0000 (UTC) Date: Thu, 11 May 2017 04:12:04 +0000 (UTC) From: "Manish Gupta (JIRA)" To: issues@carbondata.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (CARBONDATA-1045) Mismatch in message display with insert and load operation on failure due to bad records in update operation MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Thu, 11 May 2017 04:12:08 -0000 Manish Gupta created CARBONDATA-1045: ---------------------------------------- Summary: Mismatch in message display with insert and load oper= ation on failure due to bad records in update operation Key: CARBONDATA-1045 URL: https://issues.apache.org/jira/browse/CARBONDATA-1045 Project: CarbonData Issue Type: Bug Reporter: Manish Gupta Assignee: Manish Gupta Priority: Minor Fix For: 1.1.0 When bad records action is set to fail and any IUD operation=E2=80=A6 is ex= ecuted and it fails due to bad records error message is not displayed corre= ctly 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 in= sert into, if there is any failure due to bad record proper error message i= s displayed to the user for failure due to bad record. Steps to reproduce --------------------------- create table update_with_bad_record(item int, name String) stored by 'carbo= ndata' LOAD DATA LOCAL INPATH '' into table update_with_bad_record update update_with_bad_record set (item)=3D(3.45) dummy data ------------------- item,name 2,Apple -- This message was sent by Atlassian JIRA (v6.3.15#6346)