[
https://issues.apache.org/jira/browse/TAJO-176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keuntae Park updated TAJO-176:
------------------------------
Attachment: TAJO-176.patch
I've uploaded the patch for the issue
1. It implements read and metadata related part of jdbc interface
- TajoDriver, TajoConnection, TajoResultSet, TajoStatement,
TajoPreparedStatement
- TajoDatabaseMetaData, TajoResultSetMetaData
- renaming ResultSetImpl to TajoResultSet
2. TestCase
- TestTajoJdbc, TestResultSet
3. Usage
- Driver Class: org.apache.tajo.jdbc.TajoDriver
- Connection URL: jdbc:tajo://<tajo master host>:<tajo master client service
port>
- example:
Class.forName("org.apache.tajo.jdbc.TajoDriver").newInstance();
Connection conn =
DriverManager.getConnection("jdbc:tajo://127.0.0.1:26002");
4. modification in other modules
- At JDBC connection close time, TajoClient connection should be also closed
together, so every request from TajoClient to TajoMaster and QueryMaster is
modified to close rpc connection after the request
5. TODO
- For jar distribution (like tajo-jdbc.jar), it needs to handle library
dependency because TajoClient has dependency on (hdfs-core, hadoop-common,
hadoop-auth, yarn-core, tajo-*)
- sub project separation (maybe as 'tajo-jdbc') - currently implemented in
tajo-core-backend
> Implement Tajo JDBC Driver
> --------------------------
>
> Key: TAJO-176
> URL: https://issues.apache.org/jira/browse/TAJO-176
> Project: Tajo
> Issue Type: New Feature
> Components: client
> Reporter: Hyunsik Choi
> Fix For: 0.8-incubating
>
> Attachments: TAJO-176.patch
>
>
> Tajo is required to be integrated with legacy BI or OLAP tools. For this,
> Tajo should provide a JDBC driver.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
