You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "Deneche A. Hakim (JIRA)" <ji...@apache.org> on 2015/04/02 04:25:53 UTC
[jira] [Commented] (DRILL-2498) Separate QueryResult into two
messages QueryResult and QueryData
[ https://issues.apache.org/jira/browse/DRILL-2498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14391996#comment-14391996 ]
Deneche A. Hakim commented on DRILL-2498:
-----------------------------------------
all unit tests are passing along with precommit and tpch100
> Separate QueryResult into two messages QueryResult and QueryData
> ----------------------------------------------------------------
>
> Key: DRILL-2498
> URL: https://issues.apache.org/jira/browse/DRILL-2498
> Project: Apache Drill
> Issue Type: Improvement
> Components: Execution - Flow, Execution - RPC
> Affects Versions: 0.7.0
> Reporter: Deneche A. Hakim
> Assignee: Deneche A. Hakim
> Fix For: 0.9.0
>
> Attachments: DRILL-2498.1.patch.txt, DRILL-2498.2.patch.txt, DRILL-2498.3.patch.txt
>
>
> Currently, both the Foreman and the ScreenRoot use QueryResult as part of a QueryWritableBatch to send data and/or query status. We should split this into two separate messages one for the data that will be sent from the ScreenRoot and another for the queryStatus that will be sent from the Foreman
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)