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

second88 updated DRILL-5837:
----------------------------
    Environment: 
OS: Windows 7 32-bit
Reporting tools: Crystal Reports 2008, Crystal Reports 2016
       Priority: Major  (was: Minor)
    Description: 
The following 5 methods of java.sql.DatabaseMetaData in JDBC API should return 
false but they currently return true for Drill JDBC connection:
supportsCatalogsInDataManipulation()
supportsCatalogsInProcedureCalls()
supportsCatalogsInTableDefinitions()
supportsCatalogsInIndexDefinitions()
supportsCatalogsInPrivilegeDefinitions()

As far as I know, the synthetic catalog "DRILL" cannot be used in the creation 
of table, view and function in Drill.
For example, the following statement is incorrect:
{code:sql}
CREATE TABLE DRILL.df.tmp.`name_key` (N_NAME, N_NATIONKEY) AS SELECT 
N_NATIONKEY, N_NAME FROM 
dfs.`/Users/drilluser/apache-drill-1.0/sample-data/nation.parquet`
{code}

For consistency, all 5 methods should return false though only 
supportsCatalogsInProcedureCalls() and supportsCatalogsInTableDefinitions() are 
currently meaningful to Drill.

Crystal Reports 2008 & 2016 currently do not work with Drill in report creation 
wizard (no schemata nor views are shown for report creation) due to the 
incorrect return values of at least the following methods of DatabaseMetaData:
supportsCatalogsInDataManipulation()
supportsCatalogsInProcedureCalls()
supportsCatalogsInTableDefinitions()

  was:
The following 5 methods of java.sqlDatabaseMetaData in JDBC API should return 
false but they currently return true for Drill JDBC connection:
supportsCatalogsInDataManipulation()
supportsCatalogsInProcedureCalls()
supportsCatalogsInTableDefinitions()
supportsCatalogsInIndexDefinitions()
supportsCatalogsInPrivilegeDefinitions()

As far as I know, the synthetic catalog "DRILL" cannot be used in the creation 
of table, view and function in Drill.
For example, the following statement is incorrect:
{code:sql}
CREATE TABLE DRILL.df.tmp.`name_key` (N_NAME, N_NATIONKEY) AS SELECT 
N_NATIONKEY, N_NAME FROM 
dfs.`/Users/drilluser/apache-drill-1.0/sample-data/nation.parquet`
{code}

For consistency, all 5 methods should return false though only 
supportsCatalogsInProcedureCalls() and supportsCatalogsInTableDefinitions() are 
currently meaningful to Drill.


> Methods of DatabaseMetaData with names start with supportsCatalogs in JDBC 
> API should return false
> --------------------------------------------------------------------------------------------------
>
>                 Key: DRILL-5837
>                 URL: https://issues.apache.org/jira/browse/DRILL-5837
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: Client - JDBC, Metadata
>    Affects Versions: 1.10.0
>         Environment: OS: Windows 7 32-bit
> Reporting tools: Crystal Reports 2008, Crystal Reports 2016
>            Reporter: second88
>
> The following 5 methods of java.sql.DatabaseMetaData in JDBC API should 
> return false but they currently return true for Drill JDBC connection:
> supportsCatalogsInDataManipulation()
> supportsCatalogsInProcedureCalls()
> supportsCatalogsInTableDefinitions()
> supportsCatalogsInIndexDefinitions()
> supportsCatalogsInPrivilegeDefinitions()
> As far as I know, the synthetic catalog "DRILL" cannot be used in the 
> creation of table, view and function in Drill.
> For example, the following statement is incorrect:
> {code:sql}
> CREATE TABLE DRILL.df.tmp.`name_key` (N_NAME, N_NATIONKEY) AS SELECT 
> N_NATIONKEY, N_NAME FROM 
> dfs.`/Users/drilluser/apache-drill-1.0/sample-data/nation.parquet`
> {code}
> For consistency, all 5 methods should return false though only 
> supportsCatalogsInProcedureCalls() and supportsCatalogsInTableDefinitions() 
> are currently meaningful to Drill.
> Crystal Reports 2008 & 2016 currently do not work with Drill in report 
> creation wizard (no schemata nor views are shown for report creation) due to 
> the incorrect return values of at least the following methods of 
> DatabaseMetaData:
> supportsCatalogsInDataManipulation()
> supportsCatalogsInProcedureCalls()
> supportsCatalogsInTableDefinitions()



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to