I think it could be useful and pretty easy to implement. Feel free to file
blueprint+spec.
Andrew.
On Mon, May 11, 2015 at 9:49 AM, Sergey Lukjanov
wrote:
> Hi,
>
> do you think it could be implemented based on job binaries? It sounds like
> it's a type of job binary that should be always uploa
ck-dev] [Sahara] improve oozie engine for common lib
management
Hi Sergey
yes, it is based on job binaries. what we should do is provide a user friendly
interface, to let user know how to set oozie.libpath( may be we can show it as
"share lib path" in the job execution config horizon
Hi Sergey
yes, it is based on job binaries. what we should do is provide a user
friendly interface, to let user know how to set oozie.libpath( may be we
can show it as "share lib path" in the job execution config horizon page)
there are two scenarios as below:
(1) if Job A and Job B all need lib A
Hi,
do you think it could be implemented based on job binaries? It sounds like
it's a type of job binary that should be always uploaded to Oozie for the
tenant where it lives. (A bit crazy, but could useful).
Thanks.
On Mon, May 11, 2015 at 6:39 PM, lu jander wrote:
> Hi, All
> Currently, oozi
Hi, All
Currently, oozie share lib is not well known and can be hardly used by the
users, so I think we can make it less oozieness and more friendly for the
users, it can be used for running jobs which are using third party libs. If
many jobs use the same libs, oozie share lib can make it as a com
