What configuration value do I set to make Oozie aware of the new port for 
hive-server? All I see in docs/hive-default is 'hive.server2.thrift.port'.

Thanks,
Paul

-----Original Message-----
From: Robert Kanter [mailto:[email protected]] 
Sent: Monday, March 04, 2013 5:28 PM
To: [email protected]
Subject: Re: Hive action failing after upgrade to hive-server2

Yes.  Your hive-site.xml should be the same as what you used before, just make 
sure that you use the correct port.  Upgrading the sharelib isn't necessarily 
related to this.  I was just trying to play it safe by recommending that you 
use the sharelib that came with 4.2 instead of an older one; I believe some of 
the JARs in it have changed.

- Robert


On Mon, Mar 4, 2013 at 5:17 PM, Paul Chavez <[email protected]
> wrote:

> After Edward and your responses I reread the instructions or running 
> both versions concurrently and realized we probably had a port 
> conflict. I confirmed with our admin and he moved hive-server to a new 
> port. My understanding now is I need to put together a custom 
> hive-site.xml file and fix up the share lib, is that correct?
>
> Thanks,
> Paul
>
> On Mar 4, 2013, at 5:03 PM, "Robert Kanter" <[email protected]> wrote:
>
> > If the original Hive is running, you should be able to use it 
> > exactly the same way as before.  Make sure that the hive 
> > configurations your setting
> in
> > the Hive action are correct for your original Hive.  Also, make sure 
> > that you upgrade your sharelib (i.e. delete the current one and 
> > reupload it);
> I
> > think some JARs were changed, particularly with Hive, in CDH 4.2.
> >
> > - Robert
> >
> >
> >
> > On Mon, Mar 4, 2013 at 4:06 PM, Paul Chavez <
> [email protected]
> >> wrote:
> >
> >> Robert,
> >>
> >> Yes, hi, same Paul. Apologies if cross-posting is discouraged.
> >>
> >> What are my options for continuing to use Hive? We did restart the 
> >> original hive-server instance, but didn't seem to help. What do I 
> >> need
> to
> >> do to point at the old instance (which does not currently appear to 
> >> be interfering with hive-server2)?
> >>
> >> Thanks,
> >> Paul
> >>
> >>
> >> -----Original Message-----
> >> From: Robert Kanter [mailto:[email protected]]
> >> Sent: Monday, March 04, 2013 4:04 PM
> >> To: [email protected]
> >> Subject: Re: Hive action failing after upgrade to hive-server2
> >>
> >> Hi Paul,
> >> Is this same issue that you were asking about in the CDH-User list?  
> >> (is this the same Paul?)  Unfortunately, the Hive action in Oozie 
> >> isn't compatible with Hive Server 2.  We are working on this and we 
> >> hope
> (though
> >> I cannot promise) it will be done for CDH 4.3.
> >>
> >> Hi Edward,
> >> The reason that your Hive action isn't the default is because we 
> >> didn't know it existed.  If you'd like to contribute your Hive 
> >> action back to Oozie, please create a JIRA on 
> >> https://issues.apache.org/jira/browse/OOZIEexplaining why your Hive 
> >> action is better and post a patch; we're always looking for more 
> >> contributions.
> >> Also, I'm just curious, what is the advantage of your 2 shell 
> >> actions
> over
> >> the built-in shell action?
> >>
> >> thanks
> >> - Robert
> >>
> >>
> >>
> >> On Mon, Mar 4, 2013 at 2:31 PM, Edward Capriolo 
> >> <[email protected]
> >>> wrote:
> >>
> >>> Understood. Hive-thift-2 is NOT compatible with hive-thrift so 
> >>> getting it to work out of the box will be impossible. You will 
> >>> have to at least update some oozie jars.
> >>>
> >>> Edward
> >>>
> >>> On Mon, Mar 4, 2013 at 5:05 PM, Paul Chavez < 
> >>> [email protected]
> >>>> wrote:
> >>>
> >>>> I agree this should be easier. However as just an oozie user and 
> >>>> not an administrator of the stack I am not in a position to 
> >>>> implement the workaround you linked. This needs to work with 
> >>>> what's provided with CDH
> >>> 4.2
> >>>> out of the box. Is this the wrong list?
> >>>>
> >>>>
> >>>> -----Original Message-----
> >>>> From: Edward Capriolo [mailto:[email protected]]
> >>>> Sent: Monday, March 04, 2013 10:51 AM
> >>>> To: [email protected]
> >>>> Subject: Re: Hive action failing after upgrade to hive-server2
> >>>>
> >>>> now that all the concurrency bugs are "solved" with hive server 
> >>>> 2, I see no reason why the lighter thrift action I made is not the 
> >>>> default.
> >>> http://www.edwardcapriolo.com/roller/edwardcapriolo/entry/hive_and
> >>> _ooz
> >>> ie_featuring_hive
> >>>>
> >>>>
> >>>>
> >>>> On Mon, Mar 4, 2013 at 1:40 PM, Paul Chavez < 
> >>>> [email protected]
> >>>>> wrote:
> >>>>
> >>>>> Hello,
> >>>>>
> >>>>> I've had some coordinators running since the first of this year 
> >>>>> that run a nightly sqoop and then some hive scripts afterward.
> >>>>> Last week our cluster was upgraded to CDH 4.2 and HDFS HA, since 
> >>>>> then the actions fail on the first data load step. We also have 
> >>>>> always had a MySQL metastore database for hive.
> >>>>>
> >>>>> I'm pretty sure the issue lies with accessing the metastore, 
> >>>>> since the first LOAD statement actually moves the files to the 
> >>>>> new location but then fails with a qlMove exeption and the 
> >>>>> partition never appears in the table list.
> >>>>>
> >>>>> Previously I was attaching 4 javax.jod.option properties 
> >>>>> (ConnectionURL, ConnectionDriveName, ConnectionUserName,
> >>>>> ConnectionUserPassword) to the hive action itself to get this to
> >> work.
> >>>>> So far I have verified that the MySQL connector JAR is still in 
> >>>>> the oozie share lib as it was before. If I remove the 4 jdo 
> >>>>> properties I get a 'table not found' error. I recently updated 
> >>>>> the connectionURL slightly to the new format in hive-site.xml 
> >>>>> (appending some query params for encoding) and now I get a 
> >>>>> 'Exception while processing
> >>>> '<table_name>'.
> >>>>>
> >>>>> Previously hive was managed by 'us', now it's integrated with CM 4.5.
> >>>>> We also moved from hive-server to hive-server2. I know a lot of 
> >>>>> things changed at once, so hoping for some guidance as I'm a bit 
> >>>>> lost as to what needs to be fixed here.
> >>>>>
> >>>>> thank you,
> >>>>> Paul Chavez
> >>
>

Reply via email to