[
https://issues.apache.org/jira/browse/TAJO-1944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15070624#comment-15070624
]
ASF GitHub Bot commented on TAJO-1944:
--------------------------------------
Github user jihoonson commented on a diff in the pull request:
https://github.com/apache/tajo/pull/876#discussion_r48397759
--- Diff:
tajo-core-tests/src/test/java/org/apache/tajo/ws/rs/resources/TestQueryResultResource.java
---
@@ -26,6 +26,7 @@
import org.apache.tajo.exception.ErrorUtil;
import org.apache.tajo.storage.RowStoreUtil;
import org.apache.tajo.storage.Tuple;
+import org.apache.tajo.storage.thirdparty.orc.IntegerColumnStatistics;
--- End diff --
Unnecessary import.
> Support text resultset for REST
> --------------------------------
>
> Key: TAJO-1944
> URL: https://issues.apache.org/jira/browse/TAJO-1944
> Project: Tajo
> Issue Type: Task
> Components: REST API
> Reporter: Jihoon Son
> Assignee: DaeMyung Kang
> Fix For: 0.12.0
>
>
> See the discussion at http://markmail.org/message/gpvzw7fcbo4rrtkt.
> Currently, our REST api returns result sets in a binary form. This makes
> users to use our REST api difficult.
> However, see another discussion at
> https://mail-archives.apache.org/mod_mbox/tajo-dev/201503.mbox/%3ccafu6yh0dgbvwqnbyw3hrp-6dvzp4fg65mnpueqqgwuoq_x_...@mail.gmail.com%3E.
> Since we plan to support other types of clients using REST api, we also need
> to support binary result sets.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
