Re: Auto-Organize Layout

Elli, Joe gave an excellent talk last year at OSCON 2015. Shows a bit of the provenance features and searchability of NiFi. https://www.youtube.com/watch?v=sQCgtCoZyFQ ​Full videos and tutorials are here: https://nifi.apache.org/videos.html Thad +ThadGuidry

Re: Auto-Organize Layout

Joe, Responses to your bullets: 1) I wasn't aware of the details of how provenance works. After reading about it, it seems quite powerful and it may help for some cases. I especially like the ability to replay files and track timing of events. However, there are some problems I think I've expe

Re: Auto-Organize Layout

Re: Emphasising important processors, is there a resize feature to make some boxes on the canvas bigger/smaller than others? Then the main flow could be "follow the big boxes" Or! Allow them to auto-size based on volume. That would be neat. On Wed, Jan 20, 2016 at 3:49 PM, Joe Witt wrote: > Ell

Re: Auto-Organize Layout

Elli, Ok great feedback. I'll categorize these in the following ways (if you disagree please share) 1) How best to handle log/debug sort of flows One thing to consider is that with our provenance and content archival it eliminated the need for many uses of LogAttribute and for PutFile for these

Re: Auto-Organize Layout

Joe, What I'm referring to as far as emphasizing "important" processors is that there are many places in my workflow where I do a PutFile for logging purposes, and I have one for success and a separate one for failure. So for many of my main processors, there are two connectors to PutFiles. This

Re: Auto-Organize Layout

+1 to adding capabilities that will allow users to build the desired layout more efficiently. Allowing them to more easily align components, snap-to-grid, lock, and bend connections would all fall into this category. I'm a little indifferent to supporting an auto-layout feature. I've tried a numbe

Re: Auto-Organize Layout

Elli "it is sometimes too easy to mis-align processors by dragging them accidentally" Great point I must admit I too do that. Often in really important demos. I've gotten good at making jokes about it. Probably should have gotten good at submitting a JIRA :-) I'd like to understand more abo

Re: Auto-Organize Layout

+1 for "snap to grid" feature Sent from my iPhone > On Jan 19, 2016, at 4:20 PM, dan bress wrote: > > Maybe not exactly "auto-layout" but I would back a notion of having the > components snap to a coarser grain grid than what we currently have. > Sometimes I care a lot about having everything l

Re: Auto-Organize Layout

I also think that some way to help layout the flow would be very useful. One of the hardest parts of creating an easy to read workflow is the designing a good layout, and in many cases I simply want to be able to select a few processors and line them up (horizontally or vertically). Also, it is

Re: Auto-Organize Layout

I don't care so much about having it lined up, in this case (although *OCD!*), more about knowing that I could view the data in a common-way on any nifi, globally, if i choose to click a "view->auto-layout->up-down" or "view->auto-layout->left-right". Again, this doesn't overwrite flow.xml file.

Re: Auto-Organize Layout

"Sometimes I care a lot about having everything line up in the graph" -- That should be our slogan for a NiFi TShirt. On Tue, Jan 19, 2016 at 4:20 PM, dan bress wrote: > Maybe not exactly "auto-layout" but I would back a notion of having the > components snap to a coarser grain grid than what we

Re: Auto-Organize Layout

Maybe not exactly "auto-layout" but I would back a notion of having the components snap to a coarser grain grid than what we currently have. Sometimes I care a lot about having everything line up in the graph horizontally and vertically, and it always takes a long time to achieve this. I could see

Re: Auto-Organize Layout

I like your idea Rob, that would help with lining up relationships too (straight lines). On Matt's note, I don't think there should be a "standard" either, although best practices are always out there. On Matt's note of putting failures up above processes, we do that too. Totally depends on who m

Re: Auto-Organize Layout

I agree with Matt's points. I was just replying with something similar basically saying I think trying to set a standard would not be well-received. I believe what could be more useful are layout tools that would help users place components to help achieve their preferred layouts. For example, the

Re: Auto-Organize Layout

Ryan, Setting a standard is a difficult thing to do. The complexity that can exist in many flows would make enforcing a standard difficult. The first example you provide of success to points right while failures point up is not recommended. It would be better to have failures point down

Re: Auto-Organize Layout

Hi Rob, Yea we did, it was at the end of the meeting. I think it would be useful to have a couple default type views that help standardize flow layout across the community. For example, when we organize processors left-to-right, failure relationships always point up, and success alway

Re: Auto-Organize Layout

Ryan - I think we spoke briefly (at a very high level) about this at a prior meetup. What alternate views did you have in mind, and in what ways do you think they'd be useful? Rob On Tue, Jan 19, 2016 at 10:56 AM, Ryan H wrote: > It'd be pretty awesome if NiFi provided the ability to auto-organ

Auto-Organize Layout

It'd be pretty awesome if NiFi provided the ability to auto-organize a layout. Maybe even just a auto-organized layout that doesn't change the flow.xml, just an alternate view. Looking at these demos here: http://js.cytoscape.org/#demos Ryan