Mailing-List: contact dev-help@drill.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@drill.apache.org
Date: Sat, 13 Aug 2016 01:07:20 +0000 (UTC)
From: "Matt Keranen (JIRA)" <jira@apache.org>
To: dev@drill.apache.org
Message-ID: <JIRA.12997108.1471050429000.297582.1471050440474@Atlassian.JIRA>
In-Reply-To: <JIRA.12997108.1471050429000@Atlassian.JIRA>
References: <JIRA.12997108.1471050429000@Atlassian.JIRA> <JIRA.12997108.1471050429814@arcas>
Subject: [jira] [Created] (DRILL-4845) Malformed CSV throws
 IllegalArgumentException
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Sat, 13 Aug 2016 01:07:22 -0000

Matt Keranen created DRILL-4845:
-----------------------------------

             Summary: Malformed CSV throws IllegalArgumentException
                 Key: DRILL-4845
                 URL: https://issues.apache.org/jira/browse/DRILL-4845
             Project: Apache Drill
          Issue Type: Bug
          Components: Storage - Text & CSV
    Affects Versions: 1.6.0, 1.7.0
         Environment: CentOS 7
            Reporter: Matt Keranen


When reading CSV data, if lines are malformed, often an error such as the following is reported:

    Error: SYSTEM ERROR: IllegalArgumentException: length: -15150 (expected: >= 0)

Neither the error message reported to the client (with verbose errors on), nor on the drillbit describe what or where the problem is.

Perhaps the CSV parser can throw exceptions that would help in locating what in the source data is not parsing?


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)