[TAJO-2103] JdbcMetadataProviderBase need to differentiate between database name in DBMS and database name in Tajo.

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: JDBC Storage
• Assignee: JaeHwa Jung
• Reporter: JaeHwa Jung
• Created: 28/Mar/16 04:54
• Updated: 17/May/16 23:44

Description

When using mapped_database configuration in JDBCTablespace, users can map actual database name in RDBMS to virtual database name in Tajo. If users set tajo-storage.json as follow:

{
  "spaces": {
    "pgsql_db1": {
      "uri": "jdbc:postgresql://hostname:port/db1",
      "configs": {
        "mapped_database": "tajo_db1",
        "connection_properties": {
          "user":     "tajo",
          "password": "xxxx"
        }
      }
    }
  }
}

In above example, the database db1 in PostgreSQL will be mapped the database tajo_db1 in Tajo. And users can write select statement, for example, "SELECT * from tajo_db1.Xyz".

But actually, if mapped database name is not equals to actual database name, users won't be able to get table in Tajo because JdbcMetadataProviderBase always get table with mapped database name. The provider need to differentiate between database name in DBMS and database name in Tajo.

Issue Links

• links to: GitHub Pull Request #990