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

ASF GitHub Bot commented on TAJO-1249:
--------------------------------------

GitHub user charsyam opened a pull request:

    https://github.com/apache/tajo/pull/313

    TAJO-1249: Tajo Should Check File Format is allowed.

    Currently Tajo just show NullPointException when can't understand file 
format
    ```c
    default> create external table table1 ( id int, name text, score float, 
type text, mytime int, mytime2 date) using TEXT1 location 
'file:/Users/charsyam/tajo/table';
    ERROR: java.lang.NullPointerException
    ```
    It is better to return using verficationstate

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

    $ git pull https://github.com/charsyam/tajo feature/TAJO-1249

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

    https://github.com/apache/tajo/pull/313.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 #313
    
----
commit ad6ea76a77515899cd83d1124b19b09afd1467e2
Author: clark.kang <[email protected]>
Date:   2014-12-19T15:58:42Z

    TAJO-1249

----


> Tajo Should Check File Format is allowed.
> -----------------------------------------
>
>                 Key: TAJO-1249
>                 URL: https://issues.apache.org/jira/browse/TAJO-1249
>             Project: Tajo
>          Issue Type: Bug
>            Reporter: DaeMyung Kang
>            Assignee: DaeMyung Kang
>            Priority: Minor
>
> Currently Tajo just show NullPointException when can't understand file format
> ```c
> default> create external table table1 (       id int,       name text,       
> score float,       type text, mytime int, mytime2 date)       using TEXT1 
> location 'file:/Users/charsyam/tajo/table';
> ERROR: java.lang.NullPointerException
> ```
> It is better to return using verficationstate



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

Reply via email to