[
https://issues.apache.org/jira/browse/TAJO-1944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15024843#comment-15024843
]
ASF GitHub Bot commented on TAJO-1944:
--------------------------------------
GitHub user charsyam opened a pull request:
https://github.com/apache/tajo/pull/876
TAJO-1944: Support text resultset for REST
This is just for review. and I just add csv only now :)
I worried about 3 points.
first of all, memory usages for other type.
I think most users want to download all data as csv one time.
second, add new method for NonForwardQueryResultScanner to get tuple list.
third, removing base64 checking for consistency with other type(csv, binary)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/charsyam/tajo feature/tajo-output
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/tajo/pull/876.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 #876
----
----
> 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.11.1
>
>
> 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)
