[
https://issues.apache.org/jira/browse/TAJO-1140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14184925#comment-14184925
]
ASF GitHub Bot commented on TAJO-1140:
--------------------------------------
GitHub user hyunsik opened a pull request:
https://github.com/apache/tajo/pull/213
TAJO-1140: Separate TajoClient into fine grained parts.
This is a code clean up and refactoring patch. This patch main does as
follows:
* Separate TajoClient into SessionConnection, QueryClient, and
CatalogAdminClient
* Keep backward compatibility
* Separate QueryClient into its interface and its implementation
* Separate CatalogAdminClient into its interface and its implementation
* Rename TajoConnection to JdbcConnection
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/hyunsik/tajo TAJO-1140
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/tajo/pull/213.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #213
----
commit fca180a66c7aa118e5ce12dc434206c782b86862
Author: Hyunsik Choi <[email protected]>
Date: 2014-10-27T07:46:22Z
TAJO-1140: Separate TajoClient into fine grained parts.
----
> Separate TajoClient into fine grained parts.
> --------------------------------------------
>
> Key: TAJO-1140
> URL: https://issues.apache.org/jira/browse/TAJO-1140
> Project: Tajo
> Issue Type: Improvement
> Components: client
> Reporter: Hyunsik Choi
> Assignee: Hyunsik Choi
> Fix For: 0.9.1
>
>
> TajoClient is a monolithic and concrete class including connection, catalog
> client, and query client.
> This patch separates TajoClient into three parts: connection, catalog client,
> query client. In addition, it separates catalog client and query client into
> interface and implementation. This separations will allow easily different
> client implementation (e.g., REST or Thrift) even through it requires more
> works.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
