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/08 22:55:13 UTC

[jira] [Closed] (DRILL-2666) Query against json profile with large number of fragments fails

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

Sudheesh Katkam closed DRILL-2666.
----------------------------------
    Resolution: Not A Problem

> Query against json profile with large number of fragments fails
> ---------------------------------------------------------------
>
>                 Key: DRILL-2666
>                 URL: https://issues.apache.org/jira/browse/DRILL-2666
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: Execution - Flow
>    Affects Versions: 0.8.0
>            Reporter: Krystal
>            Assignee: Sudheesh Katkam
>             Fix For: 0.9.0
>
>         Attachments: cancelled_query2.json.gz, drill2666.log, small_cancelled_query2.json
>
>
> git.commit.id=417ad38f7239c6dc1ff0421cbd5a2358d1437c87
> I have a json profile that contains about 300 fragments.  When I try to run queries against it, the query would fail with "You tried to do a batch data read operation when you were in a state of STOP" error.  Below is an example:
> {code}
> 0: jdbc:drill:schema=dfs.hbase> select t3.majorId from (select t2.majorFragmentId majorId,t2.minorFragmentProfile.minorFragmentId minorId,flatten(t2.minorFragmentProfile.operatorProfile) oProfile from (select t1.col.majorFragmentId majorFragmentId,flatten(t1.col.minorFragmentProfile) minorFragmentProfile from (select flatten(t.fragmentprofile) col from `dfs.drillTestDir`.`/ui_profiles/cancelled_query2.json`t) t1) t2) t3 group by t3.majorId,t3.oProfile.operatorId,t3.oProfile.operatorType order by t3.majorId,t3.oProfile.operatorId;
> Query failed: RemoteRpcException: Failure while running fragment., You tried to do a batch data read operation when you were in a state of STOP.  You can only do this type of operation when you are in a state of OK or OK_NEW_SCHEMA. [ 4de479a5-ce93-4a3f-89b4-3aa55481869c on qa-node114.qa.lab:31010 ]
> [ 4de479a5-ce93-4a3f-89b4-3aa55481869c on qa-node114.qa.lab:31010 ]
> {code}
> For json profile files that contain smaller number of fragments, the queries run fine.  



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