You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@drill.apache.org by "Jason Altekruse (JIRA)" <ji...@apache.org> on 2013/06/20 00:48:21 UTC

[jira] [Commented] (DRILL-80) Connect full execution engine to sqlline

    [ https://issues.apache.org/jira/browse/DRILL-80?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13688584#comment-13688584 ] 

Jason Altekruse commented on DRILL-80:
--------------------------------------

I have been working on this the last few days and I am able to return results from the MockScanPOP operator to sqlline.

There is a remaining issue of organization that I am not sure how to fix. We really should be initially staring up drill in the test classes and then connect jdbc to the running cluster. Currently the Drill setup is happening in the same place where the reference interpreter was setup in EnumerableDrill. While this does work for getting results, we need to decouple the drill setup form the JDBC driver. I have been trying to walk through the execution of the JDBC/optiq code to see how we can pass information about a running drill instance to the EnumerableDrill object, but I cannot to find a good way to do it.

[~julianhyde] Do you have any suggestions about how to accomplish this?
                
> Connect full execution engine to sqlline
> ----------------------------------------
>
>                 Key: DRILL-80
>                 URL: https://issues.apache.org/jira/browse/DRILL-80
>             Project: Apache Drill
>          Issue Type: Improvement
>            Reporter: Jason Altekruse
>            Assignee: Jason Altekruse
>              Labels: optiq, sqlline
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> To test the system absolutely from end to end we need to hook up the full execution engine up to a client. This goal has already been accomplished with the reference interpreter and needs to be adapted to work with the full execution engine.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira