You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tajo.apache.org by "Tajo QA (JIRA)" <ji...@apache.org> on 2015/09/02 08:01:45 UTC

[jira] [Commented] (TAJO-1432) Support compressed result stream

    [ https://issues.apache.org/jira/browse/TAJO-1432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14726806#comment-14726806 ] 

Tajo QA commented on TAJO-1432:
-------------------------------

{color:red}*-1 overall.*{color}  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12720853/TAJO-1432.patch
  against master revision release-0.9.0-rc0-434-g2c9305a.

      {color:red}-1 patch.{color}  The patch command could not apply the patch.

    {color:red}-1 patch.{color}  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/PreCommit-TAJO-Build/833//console

This message is automatically generated.

> Support compressed result stream
> --------------------------------
>
>                 Key: TAJO-1432
>                 URL: https://issues.apache.org/jira/browse/TAJO-1432
>             Project: Tajo
>          Issue Type: Improvement
>          Components: Java Client
>            Reporter: Yongjin Choi
>            Assignee: Yongjin Choi
>         Attachments: TAJO-1432.patch
>
>
> Sometimes, Tajo should return big result set (a few or tens of gigabytes!) given a query.
> In many cases, the network bandwidth between client (BI tool) and tajo master is expensive or not good enough.
> So, it would be great if the communication between client and tajo master could be compressed as a session option.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)