[ 
https://issues.apache.org/jira/browse/CARBONDATA-202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15458038#comment-15458038
 ] 

ASF GitHub Bot commented on CARBONDATA-202:
-------------------------------------------

GitHub user foryou2030 opened a pull request:

    https://github.com/apache/incubator-carbondata/pull/122

    [CARBONDATA-202] Handled exception thrown in beeline for all dictionary 

    # Why raise this pr?
    Exception thrown in Beeline for data loading when dictionary file content 
is not in correct format is not proper.
    # How to solve?
    use accumulator as flag, record the bad record in dictionary files, then 
throw exception


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/foryou2030/incubator-carbondata dictionary_ex

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-carbondata/pull/122.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 #122
    
----
commit 56b3a85ef8e371c302c94354d121ff267ddae329
Author: foryou2030 <foryou2...@126.com>
Date:   2016-09-02T09:18:37Z

    handled all dictionary exception

commit 6e99d68d3d616f5fd3e8a2b1a9dc07eb7edbb22d
Author: foryou2030 <foryou2...@126.com>
Date:   2016-09-02T09:19:33Z

    add testcase

----


> Exception thrown in Beeline for data loading when dictionary file content is 
> not in correct format
> --------------------------------------------------------------------------------------------------
>
>                 Key: CARBONDATA-202
>                 URL: https://issues.apache.org/jira/browse/CARBONDATA-202
>             Project: CarbonData
>          Issue Type: Bug
>            Reporter: Gin-zhj
>            Assignee: Gin-zhj
>            Priority: Minor
>
> Exception thrown in Beeline for data loading when dictionary file content is 
> not in correct format



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

Reply via email to