You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@tajo.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2014/10/02 09:35:33 UTC

[jira] [Commented] (TAJO-1030) Not supported JDBC APIs should return empty results instead of Exception

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

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

Github user hyunsik commented on the pull request:

    https://github.com/apache/tajo/pull/145#issuecomment-57593654
  
    @babokim could you check this issue? If possible, I'd like to add this patch in 0.9.0.


> 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)