[
https://issues.apache.org/jira/browse/TAJO-1699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14651428#comment-14651428
]
ASF GitHub Bot commented on TAJO-1699:
--------------------------------------
Github user hyunsik commented on a diff in the pull request:
https://github.com/apache/tajo/pull/662#discussion_r36056280
--- Diff: tajo-client/src/main/java/org/apache/tajo/client/QueryClient.java
---
@@ -94,11 +97,11 @@
*
* @return If failed, return null.
*/
- ResultSet executeQueryAndGetResult(final String sql) throws SQLException;
+ ResultSet executeQueryAndGetResult(final String sql) throws
TajoException;
--- End diff --
Take a look at the signature ``executeQuery`` and ``executeQueryWithJson``.
They return SubmitQueryResponse which contains ReturnState. So, we should allow
callers to handle the return state directly.
> Tajo Java Client version 2
> --------------------------
>
> Key: TAJO-1699
> URL: https://issues.apache.org/jira/browse/TAJO-1699
> Project: Tajo
> Issue Type: Improvement
> Components: Java Client
> Reporter: Hyunsik Choi
> Assignee: Hyunsik Choi
> Fix For: 0.11.0
>
>
> I propose Tajo Java Client version 2. Its motivations are as follows:
> * After TAJO-1625, the error propagation has been changed significantly.
> Java Client should make use the new error propagation system. Java Client
> should throw the proper exceptions.
> * Many Java API exposes internal data structure and protocol buffer data
> structure. It requires users to understand its internal behavior and
> architecture. We should hide them from users.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
