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

Posted to issues@tajo.apache.org by "Hyoungjun Kim (JIRA)" <ji...@apache.org> on 2014/10/14 14:57:33 UTC

[jira] [Assigned] (TAJO-1117) TajoConnection.getSchema() should throw SQLFeatureNotSupportedException.

     [ https://issues.apache.org/jira/browse/TAJO-1117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hyoungjun Kim reassigned TAJO-1117:
-----------------------------------

    Assignee:     (was: Hyoungjun Kim)

> TajoConnection.getSchema() should throw SQLFeatureNotSupportedException.
> ------------------------------------------------------------------------
>
>                 Key: TAJO-1117
>                 URL: https://issues.apache.org/jira/browse/TAJO-1117
>             Project: Tajo
>          Issue Type: Bug
>            Reporter: Hyoungjun Kim
>            Priority: Minor
>
> JDBC has two concepts which are related to the namespace. These are 'catalog' and 'schema'. These concepts are used differently for each database. 
> Please check the following the stackoverflow issue.
> http://stackoverflow.com/questions/7942520/relationship-between-catalog-schema-user-and-database-instance
> Currently Tajo uses catalog as database and Tajo doesn't support schema. But Tajo JDBC uses "public" as schema. Tajo should throw SQLFeatureNotSupportedException or return 'null'.   



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