You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@drill.apache.org by Charles Givre <cg...@gmail.com> on 2018/11/29 15:26:58 UTC
Drill support for SQLPad
All,
There is a really nice open source tool out there called SQLPad. In addition to executing basic SQL Queries, SQLPad enables to to export results and produce basic visualizations. Until recently, SQLPad did not support Drill however, I just wrote a first attempt at Drill support which you can download here:
https://github.com/cgivre/sqlpad/tree/drill <https://github.com/cgivre/sqlpad/tree/drill>
Please check it out and let me know what you think.
Best,
— C
Re: Drill support for SQLPad
Posted by Boaz Ben-Zvi <bb...@mapr.com>.
Just got it to run on my Mac; looks nice (though the results are
flushed to the left, like 55_____ instead of _____55 )
Thanks Charles for making SQLPad work with Drill !
And for anyone else wanting to try (on a Mac), here are the steps used:
$ git clone https://github.com/cgivre/sqlpad.git
$ cd sqlpad/
$ git checkout drill
$ curl -o-
https://raw.githubusercontent.com/creationix/nvm/v0.33.11/install.sh | bash
$ source ~/.bashrc ### to get the nvm in the path
<< install "node" from https://nodejs.org/en/download/ >>
$ sudo npm i npm -g ### need sudo for write access to
/usr/local/lib/node_modules
$ npm install ### had some errors, so ran the following
$ npm audit fix ### still has some errors downloading fsevents-binaries
$ npm start
At this point, it opens your browser and connects to localhost:3000 .
Start Drill in embedded mode, and in the browser configure a Drill
connection ( to 127.0.0.1:8048 , don't care about user/password).
Run queries ......
Thanks,
Boaz
On 11/29/18 7:26 AM, Charles Givre wrote:
> All,
> There is a really nice open source tool out there called SQLPad. In addition to executing basic SQL Queries, SQLPad enables to to export results and produce basic visualizations. Until recently, SQLPad did not support Drill however, I just wrote a first attempt at Drill support which you can download here:
>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_cgivre_sqlpad_tree_drill&d=DwIFaQ&c=cskdkSMqhcnjZxdQVpwTXg&r=PqKay2uOMZUqopDRKNfBtZSlsp2meGOxWNAVHxHnXCk&m=SDFB6Jw9G8FdLYUKjQoQK8aUTMY05hzjbfcCgSQIvxI&s=zTMNxDd3-5PocjYj_K7wajK_3dCsEUVJmnEW5UszMiQ&e= <https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_cgivre_sqlpad_tree_drill&d=DwIFaQ&c=cskdkSMqhcnjZxdQVpwTXg&r=PqKay2uOMZUqopDRKNfBtZSlsp2meGOxWNAVHxHnXCk&m=SDFB6Jw9G8FdLYUKjQoQK8aUTMY05hzjbfcCgSQIvxI&s=zTMNxDd3-5PocjYj_K7wajK_3dCsEUVJmnEW5UszMiQ&e=>
>
> Please check it out and let me know what you think.
> Best,
> — C
Re: Drill support for SQLPad
Posted by Charles Givre <cg...@gmail.com>.
And… I just got the JDBC module to work. Stand by
> On Nov 30, 2018, at 14:39, Charles Givre <cg...@gmail.com> wrote:
>
> @Kunal,
> I messed with the various node JDBC drivers and got really stuck. Not with the code, but getting the drivers to install properly is insanely difficult. I couldn’t get them to work in either Linux or on my Mac. They have a lot of dependencies and judging from the amount of stackoverflow articles on the subject this is a really common problem. I couldn’t even get them installed. I would be very concerned that if we had the JDBC capabilities bundled with Drill/SQLPad, it could cause a lot of difficulty. (FYI, I am absolutely not a JS/Node guy and really am hacking my way through this)
>
> In contrast, the REST interface works without any issues. I do think that it would be worth figuring out how to get the JDBC connector to work with SQLPad, and I’ll keep working on it, but I can see the challenges.
>
> In any event, I wonder if we could use SQLPad as a basis for a new and improved UI for Drill. It offers a lot in terms of visualization, and ease of use. Personally, I’d really like to see us move away from the raw JSON in the storage plugin config to a more polished UI, but that’s another matter.
>
> Anyway, any suggestions re: JDBC and Node would be greatly appreciated.
>
>
>> On Nov 30, 2018, at 12:32, salim achouche <sa...@gmail.com> wrote:
>>
>> One benefit of the REST based UI is that it does handle change-of-schema
>> events per dataset (addition / removal of columns) whereas SQLline doesn't.
>> I was wondering if SQLPad can be made to consume Drill's dynamic datasets.
>>
>> On Thu, Nov 29, 2018 at 2:56 PM Kunal Khatua <ku...@apache.org> wrote:
>>
>>> I think getting the interface to work with JDBC would be a killer feature
>>> as it will eliminate the out of heap space issue we encounter with the REST
>>> API approach.
>>>
>>> I did come across a couple of projects that exposed JDBC access via a web
>>> interface, but nothing that seemed straightforward and opensource. I'll
>>> need to dig up my graveyard of experiments to see which one of these came
>>> closest to that.
>>>
>>> In the meanwhile, if you are able to figure out the basic functionality
>>> with JDBC, I can work with you to make it a full-fledged query component
>>> for Drill.
>>> On 11/29/2018 2:06:01 PM, Charles Givre <cg...@gmail.com> wrote:
>>> Hi Kunal
>>> My branch of SQLpad does work right out of the box with Drill but it only
>>> works with the REST interface at the moment. I submitted a PR to SQLpad so
>>> we will see if they accept it.
>>>
>>> Now that I’ve figured out their data model I could probably get it to work
>>> with JDBC as well. At this point it probably could be adapted to be Drills
>>> main UI but you would have to add the storage plugin config page and a few
>>> others and that is beyond what I have time for at the moment. I will work
>>> on getting SQLpad to use JDBC as well.
>>>
>>>
>>> Sent from my iPhone
>>>
>>>> On Nov 29, 2018, at 16:25, Kunal Khatua wrote:
>>>>
>>>> +1 if you can get it deployed and running smoothly out of the box.
>>>> We can then hack around Drill to host this as the Query interface on the
>>> Drill server's webpage instead of using the current mashup of libraries,
>>> and take away the inherent challenges of maintaining the web-based Query
>>> interface within the Drill server.
>>>>
>>>> ~ KK
>>>> On 11/29/2018 10:59:49 AM, Parth Chandra wrote:
>>>> Sure. Any improvements we can get in the UI would be cool.
>>>>
>>>>> On Thu, Nov 29, 2018 at 10:52 AM Charles Givre wrote:
>>>>>
>>>>> Hi Parth,
>>>>> SQLPad doesn’t currently support JDBC, but I think it could be extended
>>> to
>>>>> do so. I found some node modules for JDBC (
>>>>> https://www.npmjs.com/package/nodejdbc
>>>>> https://www.npmjs.com/package/nodejdbc>), but I’m not the world’s best
>>>>> JavaScript programmer, so it took me a while to hack the current one
>>>>> together. I’ll have a go at it, now that I “know” what I’m doing.
>>>>>
>>>>> Regardless… I think it could be done with what’s out there. SQLPad does
>>>>> offer a huge improvement over what Drill’s current UI offers and I do
>>> think
>>>>> it would be really great to include or borrow code (with appropriate
>>>>> attribution) from it for the Drill UI. The current UI uses REST anyway,
>>> so
>>>>> it wouldn’t be any different.
>>>>>
>>>>> I always wonder why the developers of tools like this don’t include
>>>>> generic interfaces such as JDBC and ODBC rather than building
>>> tool-specific
>>>>> drivers, but that’s another discussion.
>>>>>
>>>>>
>>>>>> On Nov 29, 2018, at 13:40, Parth Chandra wrote:
>>>>>>
>>>>>> I once considered whether we could incorporate SQLPad as the query
>>>>>> execution interface in the web UI, but never got around to looking into
>>>>> it.
>>>>>> The problem with using the REST api is that it becomes unwieldy when
>>> the
>>>>>> number of records returned by the query becomes large. I haven't looked
>>>>> at
>>>>>> the code in SQLPad, but is there a way to use the JDBC/ODBC API's ?
>>>>>>
>>>>>>> On Thu, Nov 29, 2018 at 7:33 AM Charles Givre wrote:
>>>>>>>
>>>>>>> All,
>>>>>>> There is a really nice open source tool out there called SQLPad. In
>>>>>>> addition to executing basic SQL Queries, SQLPad enables to to export
>>>>>>> results and produce basic visualizations. Until recently, SQLPad did
>>>>> not
>>>>>>> support Drill however, I just wrote a first attempt at Drill support
>>>>> which
>>>>>>> you can download here:
>>>>>>>
>>>>>>> https://github.com/cgivre/sqlpad/tree/drill
>>>>>>> https://github.com/cgivre/sqlpad/tree/drill>
>>>>>>>
>>>>>>> Please check it out and let me know what you think.
>>>>>>> Best,
>>>>>>> — C
>>>>>
>>>>>
>>>
>>
>>
>> --
>> Regards,
>> Salim
>
Re: Drill support for SQLPad
Posted by Charles Givre <cg...@gmail.com>.
@Kunal,
I messed with the various node JDBC drivers and got really stuck. Not with the code, but getting the drivers to install properly is insanely difficult. I couldn’t get them to work in either Linux or on my Mac. They have a lot of dependencies and judging from the amount of stackoverflow articles on the subject this is a really common problem. I couldn’t even get them installed. I would be very concerned that if we had the JDBC capabilities bundled with Drill/SQLPad, it could cause a lot of difficulty. (FYI, I am absolutely not a JS/Node guy and really am hacking my way through this)
In contrast, the REST interface works without any issues. I do think that it would be worth figuring out how to get the JDBC connector to work with SQLPad, and I’ll keep working on it, but I can see the challenges.
In any event, I wonder if we could use SQLPad as a basis for a new and improved UI for Drill. It offers a lot in terms of visualization, and ease of use. Personally, I’d really like to see us move away from the raw JSON in the storage plugin config to a more polished UI, but that’s another matter.
Anyway, any suggestions re: JDBC and Node would be greatly appreciated.
> On Nov 30, 2018, at 12:32, salim achouche <sa...@gmail.com> wrote:
>
> One benefit of the REST based UI is that it does handle change-of-schema
> events per dataset (addition / removal of columns) whereas SQLline doesn't.
> I was wondering if SQLPad can be made to consume Drill's dynamic datasets.
>
> On Thu, Nov 29, 2018 at 2:56 PM Kunal Khatua <ku...@apache.org> wrote:
>
>> I think getting the interface to work with JDBC would be a killer feature
>> as it will eliminate the out of heap space issue we encounter with the REST
>> API approach.
>>
>> I did come across a couple of projects that exposed JDBC access via a web
>> interface, but nothing that seemed straightforward and opensource. I'll
>> need to dig up my graveyard of experiments to see which one of these came
>> closest to that.
>>
>> In the meanwhile, if you are able to figure out the basic functionality
>> with JDBC, I can work with you to make it a full-fledged query component
>> for Drill.
>> On 11/29/2018 2:06:01 PM, Charles Givre <cg...@gmail.com> wrote:
>> Hi Kunal
>> My branch of SQLpad does work right out of the box with Drill but it only
>> works with the REST interface at the moment. I submitted a PR to SQLpad so
>> we will see if they accept it.
>>
>> Now that I’ve figured out their data model I could probably get it to work
>> with JDBC as well. At this point it probably could be adapted to be Drills
>> main UI but you would have to add the storage plugin config page and a few
>> others and that is beyond what I have time for at the moment. I will work
>> on getting SQLpad to use JDBC as well.
>>
>>
>> Sent from my iPhone
>>
>>> On Nov 29, 2018, at 16:25, Kunal Khatua wrote:
>>>
>>> +1 if you can get it deployed and running smoothly out of the box.
>>> We can then hack around Drill to host this as the Query interface on the
>> Drill server's webpage instead of using the current mashup of libraries,
>> and take away the inherent challenges of maintaining the web-based Query
>> interface within the Drill server.
>>>
>>> ~ KK
>>> On 11/29/2018 10:59:49 AM, Parth Chandra wrote:
>>> Sure. Any improvements we can get in the UI would be cool.
>>>
>>>> On Thu, Nov 29, 2018 at 10:52 AM Charles Givre wrote:
>>>>
>>>> Hi Parth,
>>>> SQLPad doesn’t currently support JDBC, but I think it could be extended
>> to
>>>> do so. I found some node modules for JDBC (
>>>> https://www.npmjs.com/package/nodejdbc
>>>> https://www.npmjs.com/package/nodejdbc>), but I’m not the world’s best
>>>> JavaScript programmer, so it took me a while to hack the current one
>>>> together. I’ll have a go at it, now that I “know” what I’m doing.
>>>>
>>>> Regardless… I think it could be done with what’s out there. SQLPad does
>>>> offer a huge improvement over what Drill’s current UI offers and I do
>> think
>>>> it would be really great to include or borrow code (with appropriate
>>>> attribution) from it for the Drill UI. The current UI uses REST anyway,
>> so
>>>> it wouldn’t be any different.
>>>>
>>>> I always wonder why the developers of tools like this don’t include
>>>> generic interfaces such as JDBC and ODBC rather than building
>> tool-specific
>>>> drivers, but that’s another discussion.
>>>>
>>>>
>>>>> On Nov 29, 2018, at 13:40, Parth Chandra wrote:
>>>>>
>>>>> I once considered whether we could incorporate SQLPad as the query
>>>>> execution interface in the web UI, but never got around to looking into
>>>> it.
>>>>> The problem with using the REST api is that it becomes unwieldy when
>> the
>>>>> number of records returned by the query becomes large. I haven't looked
>>>> at
>>>>> the code in SQLPad, but is there a way to use the JDBC/ODBC API's ?
>>>>>
>>>>>> On Thu, Nov 29, 2018 at 7:33 AM Charles Givre wrote:
>>>>>>
>>>>>> All,
>>>>>> There is a really nice open source tool out there called SQLPad. In
>>>>>> addition to executing basic SQL Queries, SQLPad enables to to export
>>>>>> results and produce basic visualizations. Until recently, SQLPad did
>>>> not
>>>>>> support Drill however, I just wrote a first attempt at Drill support
>>>> which
>>>>>> you can download here:
>>>>>>
>>>>>> https://github.com/cgivre/sqlpad/tree/drill
>>>>>> https://github.com/cgivre/sqlpad/tree/drill>
>>>>>>
>>>>>> Please check it out and let me know what you think.
>>>>>> Best,
>>>>>> — C
>>>>
>>>>
>>
>
>
> --
> Regards,
> Salim
Re: Drill support for SQLPad
Posted by salim achouche <sa...@gmail.com>.
One benefit of the REST based UI is that it does handle change-of-schema
events per dataset (addition / removal of columns) whereas SQLline doesn't.
I was wondering if SQLPad can be made to consume Drill's dynamic datasets.
On Thu, Nov 29, 2018 at 2:56 PM Kunal Khatua <ku...@apache.org> wrote:
> I think getting the interface to work with JDBC would be a killer feature
> as it will eliminate the out of heap space issue we encounter with the REST
> API approach.
>
> I did come across a couple of projects that exposed JDBC access via a web
> interface, but nothing that seemed straightforward and opensource. I'll
> need to dig up my graveyard of experiments to see which one of these came
> closest to that.
>
> In the meanwhile, if you are able to figure out the basic functionality
> with JDBC, I can work with you to make it a full-fledged query component
> for Drill.
> On 11/29/2018 2:06:01 PM, Charles Givre <cg...@gmail.com> wrote:
> Hi Kunal
> My branch of SQLpad does work right out of the box with Drill but it only
> works with the REST interface at the moment. I submitted a PR to SQLpad so
> we will see if they accept it.
>
> Now that I’ve figured out their data model I could probably get it to work
> with JDBC as well. At this point it probably could be adapted to be Drills
> main UI but you would have to add the storage plugin config page and a few
> others and that is beyond what I have time for at the moment. I will work
> on getting SQLpad to use JDBC as well.
>
>
> Sent from my iPhone
>
> > On Nov 29, 2018, at 16:25, Kunal Khatua wrote:
> >
> > +1 if you can get it deployed and running smoothly out of the box.
> > We can then hack around Drill to host this as the Query interface on the
> Drill server's webpage instead of using the current mashup of libraries,
> and take away the inherent challenges of maintaining the web-based Query
> interface within the Drill server.
> >
> > ~ KK
> > On 11/29/2018 10:59:49 AM, Parth Chandra wrote:
> > Sure. Any improvements we can get in the UI would be cool.
> >
> >> On Thu, Nov 29, 2018 at 10:52 AM Charles Givre wrote:
> >>
> >> Hi Parth,
> >> SQLPad doesn’t currently support JDBC, but I think it could be extended
> to
> >> do so. I found some node modules for JDBC (
> >> https://www.npmjs.com/package/nodejdbc
> >> https://www.npmjs.com/package/nodejdbc>), but I’m not the world’s best
> >> JavaScript programmer, so it took me a while to hack the current one
> >> together. I’ll have a go at it, now that I “know” what I’m doing.
> >>
> >> Regardless… I think it could be done with what’s out there. SQLPad does
> >> offer a huge improvement over what Drill’s current UI offers and I do
> think
> >> it would be really great to include or borrow code (with appropriate
> >> attribution) from it for the Drill UI. The current UI uses REST anyway,
> so
> >> it wouldn’t be any different.
> >>
> >> I always wonder why the developers of tools like this don’t include
> >> generic interfaces such as JDBC and ODBC rather than building
> tool-specific
> >> drivers, but that’s another discussion.
> >>
> >>
> >>> On Nov 29, 2018, at 13:40, Parth Chandra wrote:
> >>>
> >>> I once considered whether we could incorporate SQLPad as the query
> >>> execution interface in the web UI, but never got around to looking into
> >> it.
> >>> The problem with using the REST api is that it becomes unwieldy when
> the
> >>> number of records returned by the query becomes large. I haven't looked
> >> at
> >>> the code in SQLPad, but is there a way to use the JDBC/ODBC API's ?
> >>>
> >>>> On Thu, Nov 29, 2018 at 7:33 AM Charles Givre wrote:
> >>>>
> >>>> All,
> >>>> There is a really nice open source tool out there called SQLPad. In
> >>>> addition to executing basic SQL Queries, SQLPad enables to to export
> >>>> results and produce basic visualizations. Until recently, SQLPad did
> >> not
> >>>> support Drill however, I just wrote a first attempt at Drill support
> >> which
> >>>> you can download here:
> >>>>
> >>>> https://github.com/cgivre/sqlpad/tree/drill
> >>>> https://github.com/cgivre/sqlpad/tree/drill>
> >>>>
> >>>> Please check it out and let me know what you think.
> >>>> Best,
> >>>> — C
> >>
> >>
>
--
Regards,
Salim
Re: Drill support for SQLPad
Posted by Kunal Khatua <ku...@apache.org>.
I think getting the interface to work with JDBC would be a killer feature as it will eliminate the out of heap space issue we encounter with the REST API approach.
I did come across a couple of projects that exposed JDBC access via a web interface, but nothing that seemed straightforward and opensource. I'll need to dig up my graveyard of experiments to see which one of these came closest to that.
In the meanwhile, if you are able to figure out the basic functionality with JDBC, I can work with you to make it a full-fledged query component for Drill.
On 11/29/2018 2:06:01 PM, Charles Givre <cg...@gmail.com> wrote:
Hi Kunal
My branch of SQLpad does work right out of the box with Drill but it only works with the REST interface at the moment. I submitted a PR to SQLpad so we will see if they accept it.
Now that I’ve figured out their data model I could probably get it to work with JDBC as well. At this point it probably could be adapted to be Drills main UI but you would have to add the storage plugin config page and a few others and that is beyond what I have time for at the moment. I will work on getting SQLpad to use JDBC as well.
Sent from my iPhone
> On Nov 29, 2018, at 16:25, Kunal Khatua wrote:
>
> +1 if you can get it deployed and running smoothly out of the box.
> We can then hack around Drill to host this as the Query interface on the Drill server's webpage instead of using the current mashup of libraries, and take away the inherent challenges of maintaining the web-based Query interface within the Drill server.
>
> ~ KK
> On 11/29/2018 10:59:49 AM, Parth Chandra wrote:
> Sure. Any improvements we can get in the UI would be cool.
>
>> On Thu, Nov 29, 2018 at 10:52 AM Charles Givre wrote:
>>
>> Hi Parth,
>> SQLPad doesn’t currently support JDBC, but I think it could be extended to
>> do so. I found some node modules for JDBC (
>> https://www.npmjs.com/package/nodejdbc
>> https://www.npmjs.com/package/nodejdbc>), but I’m not the world’s best
>> JavaScript programmer, so it took me a while to hack the current one
>> together. I’ll have a go at it, now that I “know” what I’m doing.
>>
>> Regardless… I think it could be done with what’s out there. SQLPad does
>> offer a huge improvement over what Drill’s current UI offers and I do think
>> it would be really great to include or borrow code (with appropriate
>> attribution) from it for the Drill UI. The current UI uses REST anyway, so
>> it wouldn’t be any different.
>>
>> I always wonder why the developers of tools like this don’t include
>> generic interfaces such as JDBC and ODBC rather than building tool-specific
>> drivers, but that’s another discussion.
>>
>>
>>> On Nov 29, 2018, at 13:40, Parth Chandra wrote:
>>>
>>> I once considered whether we could incorporate SQLPad as the query
>>> execution interface in the web UI, but never got around to looking into
>> it.
>>> The problem with using the REST api is that it becomes unwieldy when the
>>> number of records returned by the query becomes large. I haven't looked
>> at
>>> the code in SQLPad, but is there a way to use the JDBC/ODBC API's ?
>>>
>>>> On Thu, Nov 29, 2018 at 7:33 AM Charles Givre wrote:
>>>>
>>>> All,
>>>> There is a really nice open source tool out there called SQLPad. In
>>>> addition to executing basic SQL Queries, SQLPad enables to to export
>>>> results and produce basic visualizations. Until recently, SQLPad did
>> not
>>>> support Drill however, I just wrote a first attempt at Drill support
>> which
>>>> you can download here:
>>>>
>>>> https://github.com/cgivre/sqlpad/tree/drill
>>>> https://github.com/cgivre/sqlpad/tree/drill>
>>>>
>>>> Please check it out and let me know what you think.
>>>> Best,
>>>> — C
>>
>>
Re: Drill support for SQLPad
Posted by Charles Givre <cg...@gmail.com>.
Hi Kunal
My branch of SQLpad does work right out of the box with Drill but it only works with the REST interface at the moment. I submitted a PR to SQLpad so we will see if they accept it.
Now that I’ve figured out their data model I could probably get it to work with JDBC as well. At this point it probably could be adapted to be Drills main UI but you would have to add the storage plugin config page and a few others and that is beyond what I have time for at the moment. I will work on getting SQLpad to use JDBC as well.
Sent from my iPhone
> On Nov 29, 2018, at 16:25, Kunal Khatua <ku...@apache.org> wrote:
>
> +1 if you can get it deployed and running smoothly out of the box.
> We can then hack around Drill to host this as the Query interface on the Drill server's webpage instead of using the current mashup of libraries, and take away the inherent challenges of maintaining the web-based Query interface within the Drill server.
>
> ~ KK
> On 11/29/2018 10:59:49 AM, Parth Chandra <pa...@apache.org> wrote:
> Sure. Any improvements we can get in the UI would be cool.
>
>> On Thu, Nov 29, 2018 at 10:52 AM Charles Givre wrote:
>>
>> Hi Parth,
>> SQLPad doesn’t currently support JDBC, but I think it could be extended to
>> do so. I found some node modules for JDBC (
>> https://www.npmjs.com/package/nodejdbc
>> https://www.npmjs.com/package/nodejdbc>), but I’m not the world’s best
>> JavaScript programmer, so it took me a while to hack the current one
>> together. I’ll have a go at it, now that I “know” what I’m doing.
>>
>> Regardless… I think it could be done with what’s out there. SQLPad does
>> offer a huge improvement over what Drill’s current UI offers and I do think
>> it would be really great to include or borrow code (with appropriate
>> attribution) from it for the Drill UI. The current UI uses REST anyway, so
>> it wouldn’t be any different.
>>
>> I always wonder why the developers of tools like this don’t include
>> generic interfaces such as JDBC and ODBC rather than building tool-specific
>> drivers, but that’s another discussion.
>>
>>
>>> On Nov 29, 2018, at 13:40, Parth Chandra wrote:
>>>
>>> I once considered whether we could incorporate SQLPad as the query
>>> execution interface in the web UI, but never got around to looking into
>> it.
>>> The problem with using the REST api is that it becomes unwieldy when the
>>> number of records returned by the query becomes large. I haven't looked
>> at
>>> the code in SQLPad, but is there a way to use the JDBC/ODBC API's ?
>>>
>>>> On Thu, Nov 29, 2018 at 7:33 AM Charles Givre wrote:
>>>>
>>>> All,
>>>> There is a really nice open source tool out there called SQLPad. In
>>>> addition to executing basic SQL Queries, SQLPad enables to to export
>>>> results and produce basic visualizations. Until recently, SQLPad did
>> not
>>>> support Drill however, I just wrote a first attempt at Drill support
>> which
>>>> you can download here:
>>>>
>>>> https://github.com/cgivre/sqlpad/tree/drill
>>>> https://github.com/cgivre/sqlpad/tree/drill>
>>>>
>>>> Please check it out and let me know what you think.
>>>> Best,
>>>> — C
>>
>>
Re: Drill support for SQLPad
Posted by Kunal Khatua <ku...@apache.org>.
+1 if you can get it deployed and running smoothly out of the box.
We can then hack around Drill to host this as the Query interface on the Drill server's webpage instead of using the current mashup of libraries, and take away the inherent challenges of maintaining the web-based Query interface within the Drill server.
~ KK
On 11/29/2018 10:59:49 AM, Parth Chandra <pa...@apache.org> wrote:
Sure. Any improvements we can get in the UI would be cool.
On Thu, Nov 29, 2018 at 10:52 AM Charles Givre wrote:
> Hi Parth,
> SQLPad doesn’t currently support JDBC, but I think it could be extended to
> do so. I found some node modules for JDBC (
> https://www.npmjs.com/package/nodejdbc
> https://www.npmjs.com/package/nodejdbc>), but I’m not the world’s best
> JavaScript programmer, so it took me a while to hack the current one
> together. I’ll have a go at it, now that I “know” what I’m doing.
>
> Regardless… I think it could be done with what’s out there. SQLPad does
> offer a huge improvement over what Drill’s current UI offers and I do think
> it would be really great to include or borrow code (with appropriate
> attribution) from it for the Drill UI. The current UI uses REST anyway, so
> it wouldn’t be any different.
>
> I always wonder why the developers of tools like this don’t include
> generic interfaces such as JDBC and ODBC rather than building tool-specific
> drivers, but that’s another discussion.
>
>
> > On Nov 29, 2018, at 13:40, Parth Chandra wrote:
> >
> > I once considered whether we could incorporate SQLPad as the query
> > execution interface in the web UI, but never got around to looking into
> it.
> > The problem with using the REST api is that it becomes unwieldy when the
> > number of records returned by the query becomes large. I haven't looked
> at
> > the code in SQLPad, but is there a way to use the JDBC/ODBC API's ?
> >
> > On Thu, Nov 29, 2018 at 7:33 AM Charles Givre wrote:
> >
> >> All,
> >> There is a really nice open source tool out there called SQLPad. In
> >> addition to executing basic SQL Queries, SQLPad enables to to export
> >> results and produce basic visualizations. Until recently, SQLPad did
> not
> >> support Drill however, I just wrote a first attempt at Drill support
> which
> >> you can download here:
> >>
> >> https://github.com/cgivre/sqlpad/tree/drill
> >> https://github.com/cgivre/sqlpad/tree/drill>
> >>
> >> Please check it out and let me know what you think.
> >> Best,
> >> — C
>
>
Re: Drill support for SQLPad
Posted by Parth Chandra <pa...@apache.org>.
Sure. Any improvements we can get in the UI would be cool.
On Thu, Nov 29, 2018 at 10:52 AM Charles Givre <cg...@gmail.com> wrote:
> Hi Parth,
> SQLPad doesn’t currently support JDBC, but I think it could be extended to
> do so. I found some node modules for JDBC (
> https://www.npmjs.com/package/nodejdbc <
> https://www.npmjs.com/package/nodejdbc>), but I’m not the world’s best
> JavaScript programmer, so it took me a while to hack the current one
> together. I’ll have a go at it, now that I “know” what I’m doing.
>
> Regardless… I think it could be done with what’s out there. SQLPad does
> offer a huge improvement over what Drill’s current UI offers and I do think
> it would be really great to include or borrow code (with appropriate
> attribution) from it for the Drill UI. The current UI uses REST anyway, so
> it wouldn’t be any different.
>
> I always wonder why the developers of tools like this don’t include
> generic interfaces such as JDBC and ODBC rather than building tool-specific
> drivers, but that’s another discussion.
>
>
> > On Nov 29, 2018, at 13:40, Parth Chandra <pa...@apache.org> wrote:
> >
> > I once considered whether we could incorporate SQLPad as the query
> > execution interface in the web UI, but never got around to looking into
> it.
> > The problem with using the REST api is that it becomes unwieldy when the
> > number of records returned by the query becomes large. I haven't looked
> at
> > the code in SQLPad, but is there a way to use the JDBC/ODBC API's ?
> >
> > On Thu, Nov 29, 2018 at 7:33 AM Charles Givre <cg...@gmail.com> wrote:
> >
> >> All,
> >> There is a really nice open source tool out there called SQLPad. In
> >> addition to executing basic SQL Queries, SQLPad enables to to export
> >> results and produce basic visualizations. Until recently, SQLPad did
> not
> >> support Drill however, I just wrote a first attempt at Drill support
> which
> >> you can download here:
> >>
> >> https://github.com/cgivre/sqlpad/tree/drill <
> >> https://github.com/cgivre/sqlpad/tree/drill>
> >>
> >> Please check it out and let me know what you think.
> >> Best,
> >> — C
>
>
Re: Drill support for SQLPad
Posted by Charles Givre <cg...@gmail.com>.
Hi Parth,
SQLPad doesn’t currently support JDBC, but I think it could be extended to do so. I found some node modules for JDBC (https://www.npmjs.com/package/nodejdbc <https://www.npmjs.com/package/nodejdbc>), but I’m not the world’s best JavaScript programmer, so it took me a while to hack the current one together. I’ll have a go at it, now that I “know” what I’m doing.
Regardless… I think it could be done with what’s out there. SQLPad does offer a huge improvement over what Drill’s current UI offers and I do think it would be really great to include or borrow code (with appropriate attribution) from it for the Drill UI. The current UI uses REST anyway, so it wouldn’t be any different.
I always wonder why the developers of tools like this don’t include generic interfaces such as JDBC and ODBC rather than building tool-specific drivers, but that’s another discussion.
> On Nov 29, 2018, at 13:40, Parth Chandra <pa...@apache.org> wrote:
>
> I once considered whether we could incorporate SQLPad as the query
> execution interface in the web UI, but never got around to looking into it.
> The problem with using the REST api is that it becomes unwieldy when the
> number of records returned by the query becomes large. I haven't looked at
> the code in SQLPad, but is there a way to use the JDBC/ODBC API's ?
>
> On Thu, Nov 29, 2018 at 7:33 AM Charles Givre <cg...@gmail.com> wrote:
>
>> All,
>> There is a really nice open source tool out there called SQLPad. In
>> addition to executing basic SQL Queries, SQLPad enables to to export
>> results and produce basic visualizations. Until recently, SQLPad did not
>> support Drill however, I just wrote a first attempt at Drill support which
>> you can download here:
>>
>> https://github.com/cgivre/sqlpad/tree/drill <
>> https://github.com/cgivre/sqlpad/tree/drill>
>>
>> Please check it out and let me know what you think.
>> Best,
>> — C
Re: Drill support for SQLPad
Posted by Parth Chandra <pa...@apache.org>.
I once considered whether we could incorporate SQLPad as the query
execution interface in the web UI, but never got around to looking into it.
The problem with using the REST api is that it becomes unwieldy when the
number of records returned by the query becomes large. I haven't looked at
the code in SQLPad, but is there a way to use the JDBC/ODBC API's ?
On Thu, Nov 29, 2018 at 7:33 AM Charles Givre <cg...@gmail.com> wrote:
> All,
> There is a really nice open source tool out there called SQLPad. In
> addition to executing basic SQL Queries, SQLPad enables to to export
> results and produce basic visualizations. Until recently, SQLPad did not
> support Drill however, I just wrote a first attempt at Drill support which
> you can download here:
>
> https://github.com/cgivre/sqlpad/tree/drill <
> https://github.com/cgivre/sqlpad/tree/drill>
>
> Please check it out and let me know what you think.
> Best,
> — C
Re: Drill support for SQLPad
Posted by Ted Dunning <te...@gmail.com>.
That's cool.
On Thu, Nov 29, 2018, 07:33 Charles Givre <cgivre@gmail.com wrote:
> All,
> There is a really nice open source tool out there called SQLPad. In
> addition to executing basic SQL Queries, SQLPad enables to to export
> results and produce basic visualizations. Until recently, SQLPad did not
> support Drill however, I just wrote a first attempt at Drill support which
> you can download here:
>
> https://github.com/cgivre/sqlpad/tree/drill <
> https://github.com/cgivre/sqlpad/tree/drill>
>
> Please check it out and let me know what you think.
> Best,
> — C