Mailing-List: contact issues-help@drill.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@drill.apache.org
Date: Wed, 18 Feb 2015 22:26:12 +0000 (UTC)
From: "Parth Chandra (JIRA)" <jira@apache.org>
To: issues@drill.apache.org
Message-ID: <JIRA.12764420.1420058695000.80770.1424298372236@Atlassian.JIRA>
In-Reply-To: <JIRA.12764420.1420058695000@Atlassian.JIRA>
References: <JIRA.12764420.1420058695000@Atlassian.JIRA>
 <JIRA.12764420.1420058695225@arcas>
Subject: [jira] [Updated] (DRILL-1916) FragmentState, QueryState not
 documented;  states not well specified
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/DRILL-1916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Parth Chandra updated DRILL-1916:
---------------------------------
    Priority: Minor  (was: Major)

> FragmentState, QueryState not documented;  states not well specified
> --------------------------------------------------------------------
>
>                 Key: DRILL-1916
>                 URL: https://issues.apache.org/jira/browse/DRILL-1916
>             Project: Apache Drill
>          Issue Type: Improvement
>            Reporter: Daniel Barclay (Drill/MapR)
>            Assignee: Daniel Barclay (Drill/MapR)
>            Priority: Minor
>             Fix For: 1.0.0
>
>
> The FragmentState and QueryState protobuf enumerations are not documented.
> In particular, the meanings of the states is not well specified.
> For example, is not clear whether QueryState.CANCELED or FragmentState.CANCELLED (AGH! Be consistent!) means that cancellation has been started or means that cancellation has been completed.  (If cancellation has started but has not completed, should the query or fragment be in the CANCELLED state already?)
> (Separately:  Might a transitional state be required (at this global/high level)?)


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