Return-Path: X-Original-To: apmail-hive-user-archive@www.apache.org Delivered-To: apmail-hive-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A8E1EEAE8 for ; Mon, 7 Jan 2013 02:39:38 +0000 (UTC) Received: (qmail 86387 invoked by uid 500); 7 Jan 2013 02:39:37 -0000 Delivered-To: apmail-hive-user-archive@hive.apache.org Received: (qmail 86064 invoked by uid 500); 7 Jan 2013 02:39:37 -0000 Mailing-List: contact user-help@hive.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hive.apache.org Delivered-To: mailing list user@hive.apache.org Received: (qmail 86041 invoked by uid 99); 7 Jan 2013 02:39:36 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 07 Jan 2013 02:39:36 +0000 X-ASF-Spam-Status: No, hits=1.7 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of wsxys08@gmail.com designates 209.85.215.45 as permitted sender) Received: from [209.85.215.45] (HELO mail-la0-f45.google.com) (209.85.215.45) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 07 Jan 2013 02:39:31 +0000 Received: by mail-la0-f45.google.com with SMTP id ep20so13947080lab.4 for ; Sun, 06 Jan 2013 18:39:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=fRPbhURwGe9Jp0QjFLfutno8y9Q0SAI81y4NxZKt1CE=; b=Xpcls9yYfUpGjky7hDyeDAdo/oxJvUQmvtCexDEzoxqL0RDORt/6CdMcUWO8LPimQh NK/m0Z9jt0v7yb/hqRzQmzdIwe7GPXkH3ll+Q743NDxaMVY6gVQtS0qZhRofBDmZ0kb0 yOlvLdmypRVhUP8lCPoyFfW08xEhmLiNotZjl1MEcTRfGIFlXira+wp1XI3upI7qJD4d qN0h7Bw75uVVeqpApQs4qAoPrCaWe3W95tXG0IdJIk9aiNbxIe3DHO1RwNHpvUFbDcoN ae6Yfc6GhuSIgqFjtlFq8DI0HyQ+r1ipMGRjB9K3PqthUu5SYrtcyJa/ejLE4/s1AmIs fEsQ== MIME-Version: 1.0 Received: by 10.112.46.199 with SMTP id x7mr24049391lbm.109.1357526349761; Sun, 06 Jan 2013 18:39:09 -0800 (PST) Received: by 10.114.92.144 with HTTP; Sun, 6 Jan 2013 18:39:09 -0800 (PST) In-Reply-To: <8B3E1399-FA62-4D3A-915C-529B35E80946@gmail.com> References: <8B3E1399-FA62-4D3A-915C-529B35E80946@gmail.com> Date: Mon, 7 Jan 2013 10:39:09 +0800 Message-ID: Subject: Re: Hive HWI ... request for your experience to be used Production From: Qiang Wang To: user@hive.apache.org Content-Type: multipart/alternative; boundary=bcaec5540568d9cd9904d2a9bbd6 X-Virus-Checked: Checked by ClamAV on apache.org --bcaec5540568d9cd9904d2a9bbd6 Content-Type: text/plain; charset=ISO-8859-1 Before running queries, a compile method will be called in class org.apache.hadoop.hive.ql.Driver. I think we can take some useful code out of this method. Qiang 2013/1/7 Edward Capriolo > I think a simple way would be to try tacking an explain in front of it. > Explains do not map reduce so they should be synchronous. > > Sent from my iPad > > On Jan 6, 2013, at 1:58 PM, Manish Malhotra > wrote: > > https://github.com/anjuke/hwi/issues/2 > > Added an issue for "Integrating HWI with Oozie" .. > its not an issue but a feature request. Please review and see if it make > sense atleast in long term. > > Plus i want to check 1 more usecase: > > 1. Query compilation: When user writes query on the UI, does it give > compilation problem in synchronous way instead of scheduling a query that > is not correct? > > Regards, > Manish > > > On Sun, Jan 6, 2013 at 10:45 AM, Manish Malhotra < > manish.hadoop.work@gmail.com> wrote: > >> Thanks Edward for explaining .... >> Im also very much interested in building a robust tool for bringing HIVE >> more into Enterprise world where any Data Analyst / ETL developer can use >> it. >> >> Regards, >> Manish >> >> >> On Sun, Jan 6, 2013 at 9:10 AM, Edward Capriolo wrote: >> >>> The hive code is apache licensed. If you want to add you work to hive >>> simple open a jira on http://issues.apache.org/jira/hive and produce a >>> patch that will apply to hive trunk. That will start the process. >>> >>> >>> >>> >>> On Saturday, January 5, 2013, Qiang Wang wrote: >>> > Hi Manish: >>> > Glad to talk with you. >>> > 1. We are willing and trying to make it an open source project >>> although we're not familiar with how to do so. We will study the licences >>> and chose a proper one. >>> > 2. If Apache Hive agree to add this to the codebase, we >>> will definitely do this. I think this HWI is not good enough yet. >>> > 3. ThreadPool is used to run queries. So synchronous mode can be >>> achieved by setting its size to 1. >>> > Regards, >>> > Qiang >>> > >>> > 2013/1/6 Manish Malhotra >>> >> >>> >> Thanks Quiang, >>> >> >>> >> And glad that somebody already doing the improvement. Sure let me try >>> it out. >>> >> Quick questions: >>> >> >>> >> 1. What is the license of this HWI version? Can somebody else >>> contribute to this as a true open source software and use it and make it >>> available for community as well? >>> >> 2. Any plans to merge this or add to Apache Hive codebase. >>> >> 3. Does it has synchronous mode of running queries or only scheduling >>> / async way? >>> >> Thanks for your reply and time, >>> >> Regards, >>> >> Manish >>> >> >>> >> On Fri, Jan 4, 2013 at 9:34 PM, Qiang Wang wrote: >>> >>> >>> >>> Hi Manish: >>> >>> >>> >>> Glad to receive your email because we are making efforts on HWI. >>> >>> We have improved the orignal and added some features and putted it >>> on github: >>> >>> https://github.com/anjuke/hwi >>> >>> >>> >>> It's far from mature and standard, but it's improving and has >>> already deployed for our company to use. >>> >>> After all, have a try and give some advice if you're interested in >>> it. >>> >>> Thanks >>> >>> Qiang >>> >>> >>> >>> 2013/1/5 Manish Malhotra >>> >>>> >>> >>>> Hi All, >>> >>>> >>> >>>> We are exploring HWI to be used in PROD environment for adhoc >>> queries etc. >>> >>>> Want to check out in the hive community that can somebody share >>> there experience while using the HWI in prod or any environment in terms of >>> its stability and performance. >>> >>>> Also evaluating to enhance to make it more useful with different >>> features. >>> >>>> Thanks for your time and help !! >>> >>>> Regards, >>> >>>> Manish >>> >>>> >>> >>>> >>> >>> >>> >> >>> > >>> > >>> >> >> > --bcaec5540568d9cd9904d2a9bbd6 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Before running queries, a compile method will be called in= class org.apache.hadoop.hive.ql.Driver. I think we can take some useful co= de out of this method.

Qiang


2013/1/7 Edward Capriolo <edlinuxgu= ru@gmail.com>
I think a simple way would be to try tacking an expl= ain in front of it. Explains do not map reduce so they should be synchronou= s.

Sent from my iPad

On Jan 6, = 2013, at 1:58 PM, Manish Malhotra <manish.hadoop.work@gmail.com> wrote:
https://github.com/anju= ke/hwi/issues/2=A0

Added an issue for "Inte= grating HWI with Oozie" ..
its not an issue but a feature request. Please review and see if it ma= ke sense atleast in long term.=A0

Plus i want to check 1 more usecase:=A0

<= /div>
1. Query compilation: When user writes query on the UI, does it g= ive compilation problem in synchronous way instead of scheduling a query th= at is not correct?=A0

Regards,
Manish


On Sun, Jan 6, 2013 at 10:45 AM= , Manish Malhotra <manish.hadoop.work@gmail.com> = wrote:
Thanks Edward for explainin= g ....=A0
Im also very much interested in building a robust tool for br= inging HIVE more into Enterprise world where any Data Analyst / ETL develop= er can use it.=A0

Regards,
Manish


On Sun, Jan 6, 2013 at 9:1= 0 AM, Edward Capriolo <edlinuxguru@gmail.com> wrote:
The hive code is apache licensed. If you wan= t to add you work to hive simple open a jira on http://issues.apache.org/jira/hive and produce a patch that will apply to hive trunk. That will start the pr= ocess.




On Saturday, January 5, 2013, Qiang Wang <wsxys08@gmail.com> wrote:
&g= t; Hi=A0Manish:
> Glad to talk with you.
> 1. We are willing an= d trying to make it an open source project although we're not familiar = with how to do so. We will study the licences and chose a proper one.
> 2.=A0If Apache Hive=A0agree to add this to the codebase, we will=A0def= initely=A0do this. I think this HWI is not good enough yet.
> 3. Thre= adPool is used to run queries. So=A0synchronous mode can be achieved by set= ting its size to 1.
> Regards,
> Qiang
>
> 2013/1/6 Manish Malhotra <manish.hado= op.work@gmail.com>
>>
>> Thanks Quiang,
>>= ; =A0
>> And glad that somebody already doing the improvement. Sure let me = try it out.=A0
>> Quick questions:=A0
>> =A0
>> 1. What is the lic= ense of this HWI version? =A0Can somebody else contribute to this as a true= open source software and use it and make it available for community as wel= l?
>> 2. Any plans to merge this or add to Apache Hive codebase.=A0
&= gt;> 3. Does it has synchronous mode of running queries or only scheduli= ng =A0/ async way?=A0
>> Thanks for your reply and time,
>&g= t; Regards,
>> Manish
>>
>> On Fri, Jan 4, 2013 at 9:34 PM, Qia= ng Wang <wsxys08@= gmail.com> wrote:
>>>
>>> Hi Manish:
>= >>
>>> Glad to receive your email because we are making efforts on HW= I.
>>> We have improved the orignal and added some features and putte= d it on github:
>>> https://github.com/anjuke/hwi
>>>
>&= gt;> It's far from mature and=A0standard, but it's improving and= has already deployed for our company to use.
>>> After all, have a try and give some advice if you're inter= ested in it.
>>> Thanks
>>> Qiang
>>>>>> 2013/1/5 Manish Malhotra <manish.hadoop.work@gmail.com>
>>>>
>>>> Hi All,
>>>>
>>= ;>> We are exploring HWI to be used in PROD environment for adhoc que= ries etc.=A0
>>>> Want to check out in the hive community th= at can somebody share there experience while using the HWI in prod or any e= nvironment in terms of its stability and performance.=A0
>>>> Also evaluating to enhance to make it more useful with dif= ferent features.=A0
>>>> Thanks for your time and help !!=A0=
>>>> Regards,
>>>> Manish
>>>>= ;
>>>>
>>>
>>
>
>



--bcaec5540568d9cd9904d2a9bbd6--