Hi,
Wondering if there is a way to define ACLs so that a user can
start/stop/kill a workflow launched by another user (in kerberized cluster)?
The use case is the following: users a, b and c are working on a project X
and a business user has been created for project A. This business user is
used
th are set to false and
> only enabled if both are set to true (or not specified)."
>
> You may limit the number of concurrent actions by submitting them into a
> queue in YARN and configure the scheduler accordingly.
>
> BRs,
> Peter
>
> On Mon, Jun 27, 2016 at 5:2
Hi guys,
I am trying to submit workflows with around 50 actions. However depending
of how the workflow is defined and the number of actions, the time needed
by Oozie to accept the workflow may change a lot (I am not talking about
the execution time of actions, I’m really talking about the time
