drill-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Deneche A. Hakim (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (DRILL-2085) Failed to propagate error
Date Fri, 15 May 2015 18:24:00 GMT

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

Deneche A. Hakim resolved DRILL-2085.
-------------------------------------
    Resolution: Duplicate

DRILL-2548 made sure this can never happen

> Failed to propagate error
> -------------------------
>
>                 Key: DRILL-2085
>                 URL: https://issues.apache.org/jira/browse/DRILL-2085
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: Execution - Relational Operators
>            Reporter: Rahul Challapalli
>            Assignee: Deneche A. Hakim
>            Priority: Minor
>             Fix For: 1.1.0
>
>
> git.commit.id.abbrev=3e33880
> The below issue is only happening with order by operator
> Data Set :
> {code}
> {
>   "id" : 1,
>   "list" : [{"a":1}, {"a":2}]
> }
> {code}
> Query : 
> {code}
> select t.list, flatten(t.list) from `temp1.json` t order by t.id;
> Error: exception while executing query: null (state=,code=0)
> {code}
> Even the below log file does not indicate the appropriate error
> Log Contents :
> {code}
> 2015-01-27 21:19:27,835 [2b37ff20-7a96-5645-2038-02506c75874e:foreman] INFO  o.a.drill.exec.work.foreman.Foreman
- State change requested.  PENDING --> RUNNING
> 2015-01-27 21:19:27,896 [UserServer-1] INFO  o.a.drill.exec.work.foreman.Foreman - State
change requested.  RUNNING --> CANCELED
> 2015-01-27 21:19:27,910 [UserServer-1] INFO  o.a.drill.exec.work.foreman.Foreman - State
change requested.  CANCELED --> COMPLETED
> 2015-01-27 21:19:27,910 [UserServer-1] WARN  o.a.drill.exec.work.foreman.Foreman - Dropping
request to move to COMPLETED state as query is already at CANCELED state (which is terminal).
> {code}
> The actual issue seems to have been fixed by mehan't new fixes. So I am raising this
JIRA to track the issue with logging
> Let me know if you have any questions



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

Mime
View raw message