You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "Sudheesh Katkam (JIRA)" <ji...@apache.org> on 2015/04/07 20:58:12 UTC
[jira] [Closed] (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 ]
Sudheesh Katkam closed DRILL-1030.
----------------------------------
> 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: Sudheesh Katkam
> Priority: Minor
> Fix For: 0.9.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)