In terms of why there are restrictions, it is about intended usage and how given exposed properties are . Dynamic properties on those processors that have certain resources they are relying upon may not be as friendly as the framework is to these dynamic changes. Accordingly, the power of providing the capability to handle these changes is squarely on the developer of the component to determine and must be explicitly provided. Those properties that do support EL have this information conveyed in their associated help tooltip in the properties configuration as well as in the accompanying Usage documentation.
Certainly understand and appreciate the needs that some users have, but feel that this may map better to the Variable Registry feature proposal that is being considered [1]. We would appreciate any additional ideas or input in guiding that process. In terms of contributing new processors, we have developed a Contributor's Guide [2] identifying the mechanics of the process. Our Developer Guide [3] is a nice way to get insights into the API and framework as well as typical extension patterns. This should get you on your way for developing components and offering up the code for incorporation into the codebase. Of course, this developer list is also a great mechanism to help facilitate that process for anything that may be unclear or questions you may have along the way. We look forward to any contributions you would like to share with us! Thanks! [1] https://cwiki.apache.org/confluence/display/NIFI/Variable+Registry [2] https://cwiki.apache.org/confluence/display/NIFI/Contributor+Guide [3] https://nifi.apache.org/developer-guide.html On Thu, Sep 24, 2015 at 11:10 AM, wizz <[email protected]> wrote: > Hi Adrian, > > This gets very interesting! Firstly, thanks for the quick and immediate > response. What you just mentioned hit the right spot. > > A few things, when you said "GetTwitter does not support dynamic properties > for the credentials", it is true for GetTwitter and so it does for the > properties in other processors currently in the NiFi. So I wonder, why > there > is such restrictions on updating all of the properties dynamically? Why > don't NiFi core developers enable all properties to be dynamically while > there is functionality on the expression language? > > For the PutFile, I will do as what you suggested. It is something that I am > looking for but it just strange to me that not all properties support on > the > expression language :) > > Lastly, could you please direct me for contributing some new processor for > the NiFi? No immediate promise but I would like to add Spring Social into > NiFi. > > Thanks!! > > > > > -- > View this message in context: > http://apache-nifi-developer-list.39713.n7.nabble.com/Dynamic-Properties-for-Processor-tp2895p2960.html > Sent from the Apache NiFi Developer List mailing list archive at > Nabble.com. >
