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

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

GitHub user babokim opened a pull request:

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

    TAJO-1030: Not supported JDBC APIs should return empty results instead of 
Exception

    

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

    $ git pull https://github.com/babokim/tajo TAJO-1030

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

    https://github.com/apache/tajo/pull/145.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 #145
    
----
commit b4a3d62006a6ebf485e56cbcd0201d450f1f9b69
Author: HyoungJun Kim <[email protected]>
Date:   2014-09-17T13:04:43Z

    TAJO-1030: Not supported JDBC APIs should return empty results instead of 
Exception

commit eb3f53d53987fc95eb5c6b5f07505047cde4c621
Author: HyoungJun Kim <[email protected]>
Date:   2014-09-17T13:41:51Z

    Merge branch 'master' of https://git-wip-us.apache.org/repos/asf/tajo

commit b7d071c08f8d71c726bb417bfe92d3b2aad4c78a
Author: HyoungJun Kim <[email protected]>
Date:   2014-09-17T14:09:44Z

    TAJO-1030: Not supported JDBC APIs should return empty results instead of 
Exception

----


> Not supported JDBC APIs should return empty results instead of Exception
> ------------------------------------------------------------------------
>
>                 Key: TAJO-1030
>                 URL: https://issues.apache.org/jira/browse/TAJO-1030
>             Project: Tajo
>          Issue Type: Improvement
>            Reporter: Hyunsik Choi
>            Assignee: Hyoungjun Kim
>            Priority: Minor
>
> Currently, some unsupported JDBC APIs throw Exception. They do not allow 
> exiting JDBC like BI solutions to connect Tajo. So, we should change them to 
> result in empty results with correct schemas.



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

Reply via email to