Thanks Joe, With all the improvements in flight, I couldn't imagine it being a problem for all and not being addressed, yet I hadn't see anything in my cursory search of Jira.
Eric On Mon, Jun 20, 2016 at 7:14 AM, Joe Witt <[email protected]> wrote: > Eric > > You aren't doing anything wrong. It is indeed something that can be quite > annoying and with the upcoming 1.0 release is solved. > > Taking turns is the current answer and we typically see operations teams > coordinate via chat. However we can do far better. If you want an advance > look at this you can build the code presently on master. It is pretty > slick. As others change the flow you just see the flow on your browser > change automatically and this can happen while you are also making changes. > > In addressing this we are also supporting assigning rights to users for > specific portions of the flow. > > Hope that helps. > > Thanks > Joe > On Jun 20, 2016 6:04 AM, "Eric Brassell" <[email protected]> wrote: > >> Hello, >> We're exploring the use of Nifi in our org and it is working great except >> for the fact that if even 2 of us are editing flows on the same server >> simultaneously (in different process flows), the constant need to refresh >> to see the other person's changes makes it very unusable. I feel like we're >> missing something. Is this something that can be made less painful through >> configuration or do we simply need to "take turns" on the server? >> >> Thanks, >> Eric Brassell >> >
