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

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

GitHub user charsyam opened a pull request:

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

    TAJO-1657: Tajo Rest API /database/{database-name]/tables should return 
table names only without invalid external table info

    Duplicated of #610 
    
    Tajo Rest API GET /databases/{database-name}/tables should return table 
name only without invalid external table info.
    current tables API return table name and external table info but, it always 
return false.

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

    $ git pull https://github.com/charsyam/tajo feature/fix-bug-rest-api-table2

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

    https://github.com/apache/tajo/pull/619.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 #619
    
----
commit 16ba96c4ddd4ead1d0f3dd6047c49cf5abcc1f42
Author: clark.kang <[email protected]>
Date:   2015-06-29T14:25:58Z

    fix bug for rest api for table

----


> Tajo Rest API /database/{database-name]/tables should return table names only 
> without invalid external table info
> -----------------------------------------------------------------------------------------------------------------
>
>                 Key: TAJO-1657
>                 URL: https://issues.apache.org/jira/browse/TAJO-1657
>             Project: Tajo
>          Issue Type: Bug
>            Reporter: DaeMyung Kang
>            Assignee: DaeMyung Kang
>
> Tajo Rest API GET /databases/{database-name}/tables should return table name 
> only without invalid external table info.
> current tables API return table name and external table info but, it always 
> return false. 



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

Reply via email to