You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@drill.apache.org by Charles Givre <cg...@gmail.com> on 2018/12/24 16:50:42 UTC
SQLPad Support for Drill (JDBC)
Hello all,
After speaking with the developer of SQLPad and getting a little assistance, I managed to get SQLPad to work using JDBC!
What works: You can establish a connection to Drill, execute queries, and visualize the results.
What’s not done: It doesn’t get the schema metadata, available tables etc. yet to populate the drop downs. I’ll keep working on that.
Here is a link to my fork with the code:
https://github.com/cgivre/sqlpad/tree/jdbc
Also, here is a link to my branch with the Drill Embedded integration: (No JDBC)
https://github.com/cgivre/sqlpad/tree/drill
Thanks to Rick Bergfalk for his assistance with this. Please let me know what you think!
— C
Re: SQLPad Support for Drill (JDBC)
Posted by Charles Givre <cg...@gmail.com>.
HI Kunal,
Did you run npm install before trying this out? You may have to install the node module for java and jdbc separately.
—C
> On Dec 28, 2018, at 13:26, Kunal Khatua <ku...@apache.org> wrote:
>
> Hi Charles
>
> Can you provide steps of where the JDBC driver needs to be located ? I managed to start up the server but I hit a signin message:
> Cannot GET /sqlpad/signin
> I see the following in the server output:
> [root@kk127 sqlpad]# npm start > sqlpad@2.8.0 start /root/drill/cgivre/sqlpad > concurrently "npm run start-server-dev" "npm run start-client-dev" [0] [0] > sqlpad@2.8.0 start-server-dev /root/drill/cgivre/sqlpad [0] > node-dev server/server.js --dir ./db --port 3010 --debug --base-url '/sqlpad' [0] [1] [1] > sqlpad@2.8.0 start-client-dev /root/drill/cgivre/sqlpad [1] > react-scripts start [1] [0] optional driver ../drivers/jdbc not available [0] optional driver ../drivers/unixodbc not available [0] [0] NO FRONT END TEMPLATE DETECTED [0] If not running in dev mode please report this issue. [0] [0] Loading users.. [0] Loading connections.. [0] Loading queries.. [0] Loading cache.. [0] Loading config.. [1] Starting the development server... [1] [0] Schema is up to date (v3). [0] [0] Welcome to SQLPad!. Visit http://localhost:3010/sqlpad to get started [0] GET /sqlpad/ 302 14.718 ms - 72 [0] GET /sqlpad/signin 404 4.511 ms - 152 [1] Compiled successfully! [1] [1] You can now view sqlpad in the browser. [1] [1] Local: http://localhost:3000/ [1] On Your Network: http://10.10.100.127:3000/ [1] [1] Note that the development build is not optimized. [1] To create a production build, use npm run build. [1] [0] GET /sqlpad/ 302 2.275 ms - 72 [0] GET /sqlpad/signin 404 1.506 ms - 152 [0] GET /sqlpad/ 302 1.155 ms - 72 [0] GET /sqlpad/signin 404 1.263 ms - 152
>
> On 12/24/2018 9:09:11 AM, Charles Givre <cg...@gmail.com> wrote:
> Hello all,
> After speaking with the developer of SQLPad and getting a little assistance, I managed to get SQLPad to work using JDBC!
>
> What works: You can establish a connection to Drill, execute queries, and visualize the results.
> What’s not done: It doesn’t get the schema metadata, available tables etc. yet to populate the drop downs. I’ll keep working on that.
>
> Here is a link to my fork with the code:
> https://github.com/cgivre/sqlpad/tree/jdbc
>
> Also, here is a link to my branch with the Drill Embedded integration: (No JDBC)
> https://github.com/cgivre/sqlpad/tree/drill
>
> Thanks to Rick Bergfalk for his assistance with this. Please let me know what you think!
> — C
>
>
>
Re: SQLPad Support for Drill (JDBC)
Posted by Charles Givre <cg...@gmail.com>.
HI Kunal,
Did you run npm install before trying this out? You may have to install the node module for java and jdbc separately.
—C
> On Dec 28, 2018, at 13:26, Kunal Khatua <ku...@apache.org> wrote:
>
> Hi Charles
>
> Can you provide steps of where the JDBC driver needs to be located ? I managed to start up the server but I hit a signin message:
> Cannot GET /sqlpad/signin
> I see the following in the server output:
> [root@kk127 sqlpad]# npm start > sqlpad@2.8.0 start /root/drill/cgivre/sqlpad > concurrently "npm run start-server-dev" "npm run start-client-dev" [0] [0] > sqlpad@2.8.0 start-server-dev /root/drill/cgivre/sqlpad [0] > node-dev server/server.js --dir ./db --port 3010 --debug --base-url '/sqlpad' [0] [1] [1] > sqlpad@2.8.0 start-client-dev /root/drill/cgivre/sqlpad [1] > react-scripts start [1] [0] optional driver ../drivers/jdbc not available [0] optional driver ../drivers/unixodbc not available [0] [0] NO FRONT END TEMPLATE DETECTED [0] If not running in dev mode please report this issue. [0] [0] Loading users.. [0] Loading connections.. [0] Loading queries.. [0] Loading cache.. [0] Loading config.. [1] Starting the development server... [1] [0] Schema is up to date (v3). [0] [0] Welcome to SQLPad!. Visit http://localhost:3010/sqlpad to get started [0] GET /sqlpad/ 302 14.718 ms - 72 [0] GET /sqlpad/signin 404 4.511 ms - 152 [1] Compiled successfully! [1] [1] You can now view sqlpad in the browser. [1] [1] Local: http://localhost:3000/ [1] On Your Network: http://10.10.100.127:3000/ [1] [1] Note that the development build is not optimized. [1] To create a production build, use npm run build. [1] [0] GET /sqlpad/ 302 2.275 ms - 72 [0] GET /sqlpad/signin 404 1.506 ms - 152 [0] GET /sqlpad/ 302 1.155 ms - 72 [0] GET /sqlpad/signin 404 1.263 ms - 152
>
> On 12/24/2018 9:09:11 AM, Charles Givre <cg...@gmail.com> wrote:
> Hello all,
> After speaking with the developer of SQLPad and getting a little assistance, I managed to get SQLPad to work using JDBC!
>
> What works: You can establish a connection to Drill, execute queries, and visualize the results.
> What’s not done: It doesn’t get the schema metadata, available tables etc. yet to populate the drop downs. I’ll keep working on that.
>
> Here is a link to my fork with the code:
> https://github.com/cgivre/sqlpad/tree/jdbc
>
> Also, here is a link to my branch with the Drill Embedded integration: (No JDBC)
> https://github.com/cgivre/sqlpad/tree/drill
>
> Thanks to Rick Bergfalk for his assistance with this. Please let me know what you think!
> — C
>
>
>
Re: SQLPad Support for Drill (JDBC)
Posted by Kunal Khatua <ku...@apache.org>.
Hi Charles
Can you provide steps of where the JDBC driver needs to be located ? I managed to start up the server but I hit a signin message:
Cannot GET /sqlpad/signin
I see the following in the server output:
[root@kk127 sqlpad]# npm start > sqlpad@2.8.0 start /root/drill/cgivre/sqlpad > concurrently "npm run start-server-dev" "npm run start-client-dev" [0] [0] > sqlpad@2.8.0 start-server-dev /root/drill/cgivre/sqlpad [0] > node-dev server/server.js --dir ./db --port 3010 --debug --base-url '/sqlpad' [0] [1] [1] > sqlpad@2.8.0 start-client-dev /root/drill/cgivre/sqlpad [1] > react-scripts start [1] [0] optional driver ../drivers/jdbc not available [0] optional driver ../drivers/unixodbc not available [0] [0] NO FRONT END TEMPLATE DETECTED [0] If not running in dev mode please report this issue. [0] [0] Loading users.. [0] Loading connections.. [0] Loading queries.. [0] Loading cache.. [0] Loading config.. [1] Starting the development server... [1] [0] Schema is up to date (v3). [0] [0] Welcome to SQLPad!. Visit http://localhost:3010/sqlpad to get started [0] GET /sqlpad/ 302 14.718 ms - 72 [0] GET /sqlpad/signin 404 4.511 ms - 152 [1] Compiled successfully! [1] [1] You can now view sqlpad in the browser. [1] [1] Local: http://localhost:3000/ [1] On Your Network: http://10.10.100.127:3000/ [1] [1] Note that the development build is not optimized. [1] To create a production build, use npm run build. [1] [0] GET /sqlpad/ 302 2.275 ms - 72 [0] GET /sqlpad/signin 404 1.506 ms - 152 [0] GET /sqlpad/ 302 1.155 ms - 72 [0] GET /sqlpad/signin 404 1.263 ms - 152
On 12/24/2018 9:09:11 AM, Charles Givre <cg...@gmail.com> wrote:
Hello all,
After speaking with the developer of SQLPad and getting a little assistance, I managed to get SQLPad to work using JDBC!
What works: You can establish a connection to Drill, execute queries, and visualize the results.
What’s not done: It doesn’t get the schema metadata, available tables etc. yet to populate the drop downs. I’ll keep working on that.
Here is a link to my fork with the code:
https://github.com/cgivre/sqlpad/tree/jdbc
Also, here is a link to my branch with the Drill Embedded integration: (No JDBC)
https://github.com/cgivre/sqlpad/tree/drill
Thanks to Rick Bergfalk for his assistance with this. Please let me know what you think!
— C
Re: SQLPad Support for Drill (JDBC)
Posted by Kunal Khatua <ku...@apache.org>.
Hi Charles
Can you provide steps of where the JDBC driver needs to be located ? I managed to start up the server but I hit a signin message:
Cannot GET /sqlpad/signin
I see the following in the server output:
[root@kk127 sqlpad]# npm start > sqlpad@2.8.0 start /root/drill/cgivre/sqlpad > concurrently "npm run start-server-dev" "npm run start-client-dev" [0] [0] > sqlpad@2.8.0 start-server-dev /root/drill/cgivre/sqlpad [0] > node-dev server/server.js --dir ./db --port 3010 --debug --base-url '/sqlpad' [0] [1] [1] > sqlpad@2.8.0 start-client-dev /root/drill/cgivre/sqlpad [1] > react-scripts start [1] [0] optional driver ../drivers/jdbc not available [0] optional driver ../drivers/unixodbc not available [0] [0] NO FRONT END TEMPLATE DETECTED [0] If not running in dev mode please report this issue. [0] [0] Loading users.. [0] Loading connections.. [0] Loading queries.. [0] Loading cache.. [0] Loading config.. [1] Starting the development server... [1] [0] Schema is up to date (v3). [0] [0] Welcome to SQLPad!. Visit http://localhost:3010/sqlpad to get started [0] GET /sqlpad/ 302 14.718 ms - 72 [0] GET /sqlpad/signin 404 4.511 ms - 152 [1] Compiled successfully! [1] [1] You can now view sqlpad in the browser. [1] [1] Local: http://localhost:3000/ [1] On Your Network: http://10.10.100.127:3000/ [1] [1] Note that the development build is not optimized. [1] To create a production build, use npm run build. [1] [0] GET /sqlpad/ 302 2.275 ms - 72 [0] GET /sqlpad/signin 404 1.506 ms - 152 [0] GET /sqlpad/ 302 1.155 ms - 72 [0] GET /sqlpad/signin 404 1.263 ms - 152
On 12/24/2018 9:09:11 AM, Charles Givre <cg...@gmail.com> wrote:
Hello all,
After speaking with the developer of SQLPad and getting a little assistance, I managed to get SQLPad to work using JDBC!
What works: You can establish a connection to Drill, execute queries, and visualize the results.
What’s not done: It doesn’t get the schema metadata, available tables etc. yet to populate the drop downs. I’ll keep working on that.
Here is a link to my fork with the code:
https://github.com/cgivre/sqlpad/tree/jdbc
Also, here is a link to my branch with the Drill Embedded integration: (No JDBC)
https://github.com/cgivre/sqlpad/tree/drill
Thanks to Rick Bergfalk for his assistance with this. Please let me know what you think!
— C