When you mention getting the value set for properties, are you referring to values of the JSON payload you are receiving? If so, check out EvaluateJsonPath [1]. This would allow you to extract values to attributes that could later be used throughout for dictating the context of the flow. If not, could you please provide some additional information.
Regarding where the data producer "resides," either option works. However, we tend to do as much as we can within the flow so we can leverage all the features that NiFi brings to the table. This typically works out to managing the items in flow we have access to (in terms of connectivity, credentials, etc) and bringing them into the flow from sources where we do not. For your case of Twitter where we have functionality already present, we would certainly make use of that. Let us know if you have additional questions. [1] https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi.processors.standard.EvaluateJsonPath/index.html On Tue, Sep 22, 2015 at 3:02 AM, wizz <[email protected]> wrote: > Hi Joe, > > Thanks for the input! It makes sense. Gonna try the invokeHTTP. Is there > any > way to put dynamic value for properties that is "Supports Expression > Language: false"? Or is it possible to set values dynamically for many > processors from the start of the flow? > > Why I need the dynamic value properties? Because lets say I would like to > do any value set for properties based on the data from GetFile from JSON > and > from the values it determine the context of the flow: > { > "user_id": "123" > "url": "http://blah", > "dir": "blah", > "db_name": "blah" > } > > And also, from your expertise, it is better to have the data producer > inside > NiFi such as GetTwitter or you make them outside NiFi and get it using > GetKafka or GetFile. Btw, do you have any suggestion of framework to > produce > data outside NiFi? > > Many thanks for the speedy response!! > > > > -- > View this message in context: > http://apache-nifi-developer-list.39713.n7.nabble.com/Dynamic-Properties-for-Processor-tp2895p2908.html > Sent from the Apache NiFi Developer List mailing list archive at > Nabble.com. >
