drill-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristine Hahn (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (DRILL-2693) doc programmatically submit queries to Drill
Date Fri, 11 Sep 2015 18:42:47 GMT

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

Kristine Hahn edited comment on DRILL-2693 at 9/11/15 6:42 PM:

Doc ready for review on my staging site: http://kristinehahn.github.io/drill/docs/using-the-jdbc-driver/#using-the-jdbc-url-format-for-a-direct-drillbit-connection

was (Author: krishahn):
Doc ready for review: http://kristinehahn.github.io/drill/docs/using-the-jdbc-driver/#using-the-jdbc-url-format-for-a-direct-drillbit-connection

> doc programmatically submit queries to Drill 
> ---------------------------------------------
>                 Key: DRILL-2693
>                 URL: https://issues.apache.org/jira/browse/DRILL-2693
>             Project: Apache Drill
>          Issue Type: Task
>          Components: Documentation
>            Reporter: Kristine Hahn
>            Assignee: Kristine Hahn
> Document how to start up an embedded Drillbit inside your
> an application. Use a complete JDBC driver (rather than
>  the remote-only driver).
> The standalone jdbc-all driver is designed to be a remote driver.  As such, you must
have zookeeper and a separate Drill daemon up and running to leverage it.  If you want to
embed a Drillbit inside your application, you'll need to source the same classpath that the
drillbit.sh start-up script sources.
> If you just try to use the jdbc jar that gets shipped, you get this exception:
>  java.sql.SQLException: Running Drill in embedded mode using the JDBC jar
> alone is not supported.

This message was sent by Atlassian JIRA

View raw message