carbondata-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ravindra Pesala (JIRA)" <>
Subject [jira] [Resolved] (CARBONDATA-400) [Bad Records] Load data is fail and displaying the string value in beeline as exception
Date Thu, 06 Apr 2017 10:05:41 GMT


Ravindra Pesala resolved CARBONDATA-400.
       Resolution: Fixed
    Fix Version/s: 1.1.0-incubating

> [Bad Records] Load data is fail and displaying the string value in beeline as exception
> ---------------------------------------------------------------------------------------
>                 Key: CARBONDATA-400
>                 URL:
>             Project: CarbonData
>          Issue Type: Bug
>          Components: data-load
>    Affects Versions: 0.1.0-incubating
>         Environment: 3node cluster
>            Reporter: MAKAMRAGHUVARDHAN
>            Assignee: Akash R Nilugal
>            Priority: Minor
>             Fix For: 1.1.0-incubating
>          Time Spent: 4h 40m
>  Remaining Estimate: 0h
> Steps
> 1. Create table
> CREATE TABLE String_test2 (string_col string) STORED BY 'org.apache.carbondata.format';
> 2. Load the data with parameter 'BAD_RECORDS_ACTION'='FORCE' and csv contains a string
value that is out of boundary.
> LOAD DATA INPATH 'hdfs://hacluster/Carbon/Priyal/string5.csv' into table String_test2
> Actual Result: Load data is failed and displaying the string value in beeline as exception
> Expected Result:Should display a correct error message and should  not print the exception
trace on the console.
> Exception thrown on console is as shown below.
> Error: com.univocity.parsers.common.TextParsingException: Error processing input: Length
of parsed input (100001) exceeds the maximum number of characters defined in your parser settings
> Hint: Number of characters processed may have exceeded limit of 100000 characters per
column. Use settings.setMaxCharsPerColumn(int) to define the maximum number of characters
a column can have
> Ensure your configuration is correct, with delimiters, quotes and escape sequences that
match the input format you are trying to parse
> Parser Configuration: CsvParserSettings:
>         Column reordering enabled=true
>         Empty value=null
>         Header extraction enabled=false
>         Headers=null
>         Ignore leading whitespaces=true
>         Ignore trailing whitespaces=true
>         Input buffer size=128
>         Input reading on separate thread=false
>         Line separator detection enabled=false
>         Maximum number of characters per column=100000
>         Maximum number of columns=20480
>         Null value=
>         Number of records to read=all
>         Parse unescaped quotes=true
>         Row processor=none
>         Selected fields=none
>         Skip empty lines=trueFormat configuration:
>         CsvFormat:
>                 Comment character=#
>                 Field delimiter=,
>                 Line separator (normalized)=\n
>                 Line separator sequence=\n
>                 Quote character="
>                 Quote escape character=quote escape
>                 Quote escape escape character=\0, line=0, char=100002. Content parsed:

This message was sent by Atlassian JIRA

View raw message