[
https://issues.apache.org/jira/browse/TAJO-812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13991537#comment-13991537
]
ASF GitHub Bot commented on TAJO-812:
-------------------------------------
GitHub user hyunsik opened a pull request:
https://github.com/apache/tajo/pull/6
TAJO-812: Some methods of TajoDatabaseMetaData should result in an empty
tuple list instead of SQLFeatureNotSupportedException.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/hyunsik/tajo TAJO-812
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/tajo/pull/6.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 #6
----
commit 291384cc3ac54087c7fa58934e9098e1390a9933
Author: Hyunsik Choi <[email protected]>
Date: 2014-05-07T03:51:55Z
TAJO-812: Some methods of TajoDatabaseMetaData should result in an empty
tuple list instead of SQLFeatureNotSupportedException.
commit f9a018756cec68a8e245ab269c195b9b84bfafe2
Author: Hyunsik Choi <[email protected]>
Date: 2014-05-07T03:52:23Z
Merge branch 'master' of https://git-wip-us.apache.org/repos/asf/tajo into
TAJO-812
----
> Some methods of TajoDatabaseMetaData should result in an empty tuple list
> instead of SQLFeatureNotSupportedException.
> ---------------------------------------------------------------------------------------------------------------------
>
> Key: TAJO-812
> URL: https://issues.apache.org/jira/browse/TAJO-812
> Project: Tajo
> Issue Type: Bug
> Components: JDBC
> Reporter: Hyunsik Choi
> Assignee: Hyunsik Choi
> Priority: Minor
> Fix For: 0.9.0, 0.8.1
>
>
> There are some methods that Tajo cannot support. getPrimaryKeys,
> getExportedKeys, and getImportedKeys are examples. Currently, these methods
> cause SQLFeatureNotSupportedException. But, they should return an empty list
> instead of the exception. This patch fixes this problem.
> In addition, this patch fixes some potential deadlock problem in
> NettyClientBase and NettyServerBase.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
