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 3CE5717EAD for ; Mon, 23 Feb 2015 00:21:13 +0000 (UTC) Received: (qmail 13622 invoked by uid 500); 23 Feb 2015 00:21:13 -0000 Delivered-To: apmail-drill-issues-archive@drill.apache.org Received: (qmail 13592 invoked by uid 500); 23 Feb 2015 00:21:13 -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 13582 invoked by uid 99); 23 Feb 2015 00:21:13 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 23 Feb 2015 00:21:13 +0000 Date: Mon, 23 Feb 2015 00:21:13 +0000 (UTC) From: "Jacques Nadeau (JIRA)" To: issues@drill.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (DRILL-1030) Fragment 0 reports startTime too early 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-1030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Nadeau updated DRILL-1030: ---------------------------------- Component/s: Execution - Flow > Fragment 0 reports startTime too early > -------------------------------------- > > Key: DRILL-1030 > URL: https://issues.apache.org/jira/browse/DRILL-1030 > Project: Apache Drill > Issue Type: Bug > Components: Execution - Flow > Reporter: Cliff Buchanan > Assignee: Steven Phillips > Priority: Minor > Fix For: 0.8.0 > > Attachments: 0001-DRILL-1030-startTime-begins-when-operator-start.patch > > > * Currently, the startTime for fragment 0 matches the query start time, even though fragment 0 executes last. > * This is apparently because a minor fragment's startTime is being logged when the its FragmentContext is first created, not when it actually begins execution. > * Fragment 0 has its FragmentContext way before it starts executing so its incoming buffers will be available. -- This message was sent by Atlassian JIRA (v6.3.4#6332)