[
https://issues.apache.org/jira/browse/TAJO-176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13824824#comment-13824824
]
Jihoon Son commented on TAJO-176:
---------------------------------
There are some points which should be discussed.
* The first is the different handling of unimplemented functions. While some
unimplemented functions return a meaningless value such as 0, false, or "",
other functions throw an exception. It will be better to use the same way to
handle the unimplemented functions.
* There are *too many* wrong exception messages. For example,
getMaxColumnsInGroupBy() throws
SQLFeatureNotSupportedException("getMaxColumnsInGroupBy") instead of
SQLFeatureNotSupportedException("commit").
* In this patch, RpcConnectionPool is closed when TajoClient.close() is called.
I'm not sure that this is a valid action. If there are two or more TajoClients,
what will happen?
> Implement Tajo JDBC Driver
> --------------------------
>
> Key: TAJO-176
> URL: https://issues.apache.org/jira/browse/TAJO-176
> Project: Tajo
> Issue Type: New Feature
> Components: client
> Reporter: Hyunsik Choi
> Assignee: Keuntae Park
> Fix For: 0.8-incubating
>
> Attachments: TAJO-176.patch
>
>
> Tajo is required to be integrated with legacy BI or OLAP tools. For this,
> Tajo should provide a JDBC driver.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
