You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "Cliff Buchanan (JIRA)" <ji...@apache.org> on 2014/06/20 03:49:26 UTC

[jira] [Updated] (DRILL-1030) Fragment 0 reports startTime too early

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

Cliff Buchanan updated DRILL-1030:
----------------------------------

    Attachment: 0001-startTime-begins-when-operator-starts-execution.patch

Un-finalizing startTime in fragmentStats and instead setting it from FragmentExecutor.

> Fragment 0 reports startTime too early
> --------------------------------------
>
>                 Key: DRILL-1030
>                 URL: https://issues.apache.org/jira/browse/DRILL-1030
>             Project: Apache Drill
>          Issue Type: Bug
>            Reporter: Cliff Buchanan
>            Assignee: Cliff Buchanan
>            Priority: Minor
>         Attachments: 0001-startTime-begins-when-operator-starts-execution.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.2#6252)