Return-Path: X-Original-To: apmail-drill-issues-archive@minotaur.apache.org Delivered-To: apmail-drill-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 7C06017D5F for ; Thu, 19 Mar 2015 00:54:38 +0000 (UTC) Received: (qmail 62720 invoked by uid 500); 19 Mar 2015 00:54:38 -0000 Delivered-To: apmail-drill-issues-archive@drill.apache.org Received: (qmail 62689 invoked by uid 500); 19 Mar 2015 00:54:38 -0000 Mailing-List: contact issues-help@drill.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@drill.apache.org Delivered-To: mailing list issues@drill.apache.org Received: (qmail 62679 invoked by uid 99); 19 Mar 2015 00:54:38 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 19 Mar 2015 00:54:38 +0000 Date: Thu, 19 Mar 2015 00:54:38 +0000 (UTC) From: "Parth Chandra (JIRA)" To: issues@drill.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (DRILL-2498) Separate QueryResult into two messages QueryResult and QueryData MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/DRILL-2498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14368249#comment-14368249 ] Parth Chandra commented on DRILL-2498: -------------------------------------- If you're planning to change the protobuf definition, this will likely require a RPC version change for bit-to-user. The C++ client will definitely need to be updated. > 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 > Reporter: Deneche A. Hakim > Assignee: Deneche A. Hakim > > 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)