[
https://issues.apache.org/jira/browse/TAJO-1030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14159376#comment-14159376
]
Hudson commented on TAJO-1030:
------------------------------
SUCCESS: Integrated in Tajo-master-build #388 (See
[https://builds.apache.org/job/Tajo-master-build/388/])
TAJO-1030: Not supported JDBC APIs should return empty results instead of
Exception. (Hyoungjun Kim via hyunsik) (hyunsik: rev
029054b45c158159325a68ac1491256e3abe71f4)
*
tajo-catalog/tajo-catalog-common/src/main/java/org/apache/tajo/catalog/CatalogConstants.java
* tajo-jdbc/src/main/java/org/apache/tajo/jdbc/TajoDatabaseMetaData.java
* tajo-core/src/test/java/org/apache/tajo/jdbc/TestTajoDatabaseMetaData.java
* CHANGES
* tajo-common/src/main/java/org/apache/tajo/common/type/TajoTypeUtil.java
* tajo-client/src/main/java/org/apache/tajo/jdbc/TajoResultSetMetaData.java
> 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
> Components: JDBC
> Reporter: Hyunsik Choi
> Assignee: Hyoungjun Kim
> Priority: Minor
> Fix For: 0.9.0
>
>
> 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)
