Re: Configuration Driven Property Updates

Joe, yes and no. Yes, sending the new configuration settings back to the server for validation is what is needed without closing the dialogue. But it also must refresh the dialogue with any newly added config info provided by the getSupportedProperties method of the processor being configured.

Re: Configuration Driven Property Updates

Mike, Just FYI, ControllerService's are configurable via the UI since 0.2.0 [1]. Also, I would also +1 for the second of Mark's options. Matt [1] https://nifi.apache.org/docs/nifi-docs/html/user-guide.html#Controller_Services_and_Reporting_Tasks On Thu, Oct 22, 2015 at 6:42 AM, Michael D.

Re: Configuration Driven Property Updates

I think the real issue is the treatment of Processor’s properties in general. In the currently discussed approach one of the discovered modules is itself a property of a Processor. On top of that a selected module's “property” presents a list of its own properties. IMHO the better way of

Re: Configuration Driven Property Updates

+1 for the second option. On Thu, Oct 22, 2015 at 9:08 AM, Mark Payne wrote: > I two thoughts on this concept. Firstly is the notion of Controller > Services. Rather than having properties that > change significantly depending on the strategy selected, each strategy >

Re: Configuration Driven Property Updates

Mike, I'm not quite following what you're trying to accomplish. The use case you described was a bit too meta for me to wrap my head around. It sounds like a dataflow abstraction layer with nifi as a backing engine. It sounds like you have some code, is it in a public repo so we could take a look

Re: Configuration Driven Property Updates

Hey Tony,    I do have working code but  not in a public repo. I am, in fact, trying to use NiFi as a backing engine. I think the bottom line is that I want to be able to add/remove some configuration properties based on the settings of other configuration properties. For example, I might

Re: Configuration Driven Property Updates

Mike, I have implemented a NiFi processor very similar to what you describe. A ServiceLoader discovers the plugins that are available to the processor and populates the allowableValues of a PropertyDescriptor. In the end I don't think there is a way to resolve your questions/issues in the UI.

Re: Configuration Driven Property Updates

Not to trivialize this but curious if we added an 'apply' type option there would that be a sufficient user experience? The core point is once you select a new strategy we need to send that fact to the server to see what effect that has. That happens when you hit ok but as you note that closes

Configuration Driven Property Updates

All,    I'm building a set of NiFi processors that allow data flow managers to dynamically configure reusable data processing modules wrapped inside NiFi processors. Imagine that we might want to use NiFi in some cases and Storm or Spark in others. The business logic in the processing modules