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

Wenzhe Zhou closed IMPALA-12381.
--------------------------------
    Fix Version/s: Impala 4.4.0
       Resolution: Won't Fix

We are going to change the syntax to create JDBC table without data source. See 
IMPALA-12793 for detail.

> Add jdbc related properties to JDBC data source object
> ------------------------------------------------------
>
>                 Key: IMPALA-12381
>                 URL: https://issues.apache.org/jira/browse/IMPALA-12381
>             Project: IMPALA
>          Issue Type: Sub-task
>          Components: Backend, Frontend
>            Reporter: Wenzhe Zhou
>            Assignee: Wenzhe Zhou
>            Priority: Major
>             Fix For: Impala 4.4.0
>
>
> Currently jdbc related properties are specified as initString when creating 
> table as below:
> CREATE TABLE alltypes_jdbc_datasource (
>  id INT, name STRING)
> PRODUCED BY DATA SOURCE JdbcDataSource (
> '{"database.type":"POSTGRES",
> "jdbc.url":"jdbc:postgresql://localhost:5432/functional",
> "jdbc.driver":"org.postgresql.Driver",
> "dbcp.username":"hiveuser",
> "dbcp.password":"password",
> "table":"alltypes"}');
> It's more convenient to move jdbc related properties to data source object as 
> data-source properties as following sample so that user don't need to specify 
> those properties for each table. 
> CREATE DATA SOURCE JdbcDataSource
> LOCATION '/test-warehouse/data-sources/jdbc-data-source.jar'
> CLASS 'org.apache.impala.extdatasource.jdbc.JdbcDataSource'
> API_VERSION 'V1'
> *DSPROPERTIES* (
> 'DATABSE.TYPE'='POSTGRES',
> 'JDBC.URL'='jdbc:postgresql://localhost:5432/functional',
> 'JDBC.DRIVER'='org.postgresql.Driver',
> 'DBCP.USERNAME'='hiveuser',
> 'DBCP.PASSWORD'='password');



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to