Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Threaded View
Sqoop >> mail # user >> sqoop-metastore connection persistance


Copy link to this message
-
RE: sqoop-metastore connection persistance in HSQLDB with Oozie
Thank you, this solution works. I created an "at" job by doing the following:

At 14:00
Sqoop metastore
Ctrl-d

For the past few runs it seems to be working, will this job persist until server reboot?

Thank you.

From: John Dasher [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, March 06, 2013 10:54 AM
To: [EMAIL PROTECTED]
Subject: Re: sqoop-metastore connection persistance in HSQLDB with Oozie

Artem,
 I created an 'at' job on the server where the sqoop-metastore lives. This runs once and persists the sqoop-metastore for the sqoop jobs running in Oozie.

Thanks,
John

From: Artem Ervits <[EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>>
Reply-To: "[EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>" <[EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>>
Date: Wednesday, March 6, 2013 10:30 AM
To: "[EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>" <[EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>>
Subject: RE: sqoop-metastore connection persistance in HSQLDB with Oozie

Anyone? I am trying to access the metastore from Oozie so that I could run incremental jobs saved in the metastore. Is there a setting that it will reopen a connection or keep the connection alive so that following jobs do not fail due to closed connection to hsqldb? I created a workflow that just does that "sqoop metastore" but with that job running, it's only open to the user that started that job and not the user accessing the metastore.

Thanks

From: Artem Ervits [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, March 05, 2013 2:53 PM
To: [EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>
Subject: sqoop-metastore connection persistance

Hello all,

I'm configuring sqoop metastore so that I will be able to execute incremental jobs from Oozie. I want to know how to make metastore connection persist? When the ssh session that starts sqoop metastore dies, I lose connection to the metatore and cannot execute the saved job. I thought I overcome the obstacle by adding another sqoop action prior to executing the incremental job doing "sqoop metastore" and then when that completes, run the incremental, but what it does is just open the connection and doesn't advance to the job execution step. What is the right way to persist the connection to the metastore?

Thank you.

--------------------

This electronic message is intended to be for the use only of the named recipient, and may contain information that is confidential or privileged.  If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of the contents of this message is strictly prohibited.  If you have received this message in error or are not the named recipient, please notify us immediately by contacting the sender at the electronic mail address noted above, and delete and destroy all copies of this message.  Thank you.

--------------------

This electronic message is intended to be for the use only of the named recipient, and may contain information that is confidential or privileged.  If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of the contents of this message is strictly prohibited.  If you have received this message in error or are not the named recipient, please notify us immediately by contacting the sender at the electronic mail address noted above, and delete and destroy all copies of this message.  Thank you.
--------------------

This electronic message is intended to be for the use only of the named recipient, and may contain information that is confidential or privileged.  If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of the contents of this message is strictly prohibited.  If you have received this message in error or are not the named recipient, please notify us immediately by contacting the sender at the electronic mail address noted above, and delete and destroy all copies of this message.  Thank you.

This electronic message is intended to be for the use only of the named recipient, and may contain information that is confidential or privileged.  If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of the contents of this message is strictly prohibited.  If you have received this message in error or are not the named recipient, please notify us immediately by contacting the sender at the electronic mail address noted above, and delete and destroy all copies of this message.  Thank you.