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

David Alves commented on DRILL-58:
----------------------------------

+1 on most Jacques said, particularly on keeping it simple with servlets and 
using RPC as the sole comms mechanism (I just mentioned REST as one possibility 
done the line that would allow to have the app client side only, but REST might 
also make sense for other use cases, in any case it was not a suggestion that 
we try an go for it now).

Just a few additional thoughs:

I'm all for not making running jetty mandatory but *giving the option* to run a 
web ui embedded would ease a lot the deployment work for transient deployments 
and would provide a nice "aha" moment to whoever is trying drill for the first 
time.
I've started making a drill service for apache whirr and I'm thinking that 
installing a completely different set of tools (as in ruby on rails for 
instance) will make the deployment times much steeper and the deployment harder 
to manage.

The way I see it we could provide two ways (both explicitly configured): 
embedded in jetty and as a separate daemon on whatever container is preferred. 
In any case I'd prefer a jvm friendly container + framework.
Also there's a lot of examples on this in the hadoop ecosystem.
 
                
> Create a WEB UI war that can be deployed along with Drillbits
> -------------------------------------------------------------
>
>                 Key: DRILL-58
>                 URL: https://issues.apache.org/jira/browse/DRILL-58
>             Project: Apache Drill
>          Issue Type: Improvement
>            Reporter: David Alves
>            Assignee: Michael Hausenblas
>
> A while ago Michael created a simple web UI to submit queries to Drill.
> It'd be nice if we could package it in war for and deploy it in Drillbits 
> through jetty.
> Hive web ui (the way it's deployed) might be a good starting point.

--
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

Reply via email to