Member since
06-02-2020
40
Posts
4
Kudos Received
8
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
4099 | 09-30-2020 09:27 AM | |
2567 | 09-29-2020 11:53 AM | |
4069 | 09-21-2020 11:34 AM | |
4323 | 09-19-2020 09:31 AM | |
2621 | 06-28-2020 08:34 AM |
09-30-2020
05:08 AM
@praneet Adding the value to the processor (+) is a suitable method. You just need to make sure you get the right string in that field. It's blocked out, but appears not just the actual token but prepended with "Bearer". Try just the token string. One thing I like to do for any API, before I start to work on invokeHttp configuration, is to use Postman to help me identify all of the required settings to test connection to an API. Once this is complete, I can definitively ensure that nifi invokeHttp is sending the same request. If this answer resolves your issue or allows you to move forward, please choose to ACCEPT this solution and close this topic. If you have further dialogue on this topic please comment here or feel free to private message me. If you have new questions related to your Use Case please create separate topic and feel free to tag me in your post. Thanks, Steven
... View more
09-30-2020
05:03 AM
@Manoj90 In addition o @PVVK point, you need to be careful with routing relationships back on the originating processor. During development I like to use a output port that I call End of Line or EOL1, EOL2, EOL3 as I need more in larger flows. This is to evaluate if something goes to fail, retry, etc. Later once I am certain the flow is working as I need, I either auto terminate these routes, or I route them out of my processor group to an Event Notification system. It looks like this: Using an output port to hold un needed routes during testing If this answer resolves your issue or allows you to move forward, please choose to ACCEPT this solution and close this topic. If you have further dialogue on this topic please comment here or feel free to private message me. If you have new questions related to your Use Case please create separate topic and feel free to tag me in your post. Thanks, Steven
... View more
09-30-2020
12:44 AM
Hi @kquintero, Can you put the attribute into flowFile content and see if the spaces are removed in the content as well? From what I know, attributes won't show extra spaces, but, the spaces are still present. Even when you hover over those values, you can still see the empty spaces.
... View more
09-29-2020
02:10 PM
Hi @vineet_harkut , To check if the required parameters are valid in MongoDB processor, what I would do is Suppose, there is a query like {"key":"someValue","name":"someOtherValue"}. And "someValue" and "someOtherValue" are values inside the attributes of the incoming flowFile with attribute-names "key" and "name" respectively. Hence, the resulting query in the GetMongo processor will be {"key":"${key}","name":"${name}"}. Before using the GetMongo processor, I would use RouteOnAttribute processor to check if the input to the query is a valid one. If the input is correct, I will make a query to the GetMongo processor. If the document for the query is not found, the GetMongo processor will return empty document (empty string) as content in the flowfile only when Send Empty Result is set to true inside the GetMongo processor. Later, when I use EvaluateJsonPath processor, the flowfile will be routed to "failure" when the flowfile is empty, as empty string is not a valid JSON or to "matched" if the match for the given jsonPath is found. This will put the same content inside the flowfile as $ corresponds to entire JSON object that we are getting from the input flowfIle. Now, you can add the remaining logic.
... View more
09-29-2020
11:53 AM
Hi @Sru111 , For FetchSFTP processor, change the Bulletin level to NONE. Then, that error won't appear. If there are any other errors like authentication error or communication timeout, bulletin won't appear for them as well. But, the flowFiles will still be routed to the respective relations.
... View more
09-29-2020
03:29 AM
Used below formula to resolve my problem ${field.value:substring(0,21):toDate("MMM dd,yyyy HH:mm:ss"):format("yyyy-MM-dd HH:mm:ss")}.${field.value:substring(22,28)} We separately added last 6 digit using .${field.value:substring(22,28)} after the time format.Otherwise, nifi can not process 6 digit microsecond.
... View more
09-28-2020
09:58 PM
At the end of the day I used Steve Matison and 'PVVK's solutions. First I used PVVK's to modify my flowfile into valid html, then I successfully was able to use SplitJson processor to break up the flowfiles cleanly. Then since there were multiple 'logEvent' entries in some of the records I saved off the header items as attributes and then used SteveMatison's method to break down each logEvent and added the header attributes back to it for processing. Thanks all!
... View more
09-21-2020
08:51 AM
Hi @praneet ! Look at the spec I used Input used: { "Подписка":"awdl" } Spec: [ { "operation": "shift", "spec": { "Подписка":"Подпиа" } } ] Output got: {"Подпиа":"awdl"} I was able to perform jolt without any problems in nifi-1.11.4 Tell me if you are still facing the issues.
... View more
09-21-2020
12:39 AM
@PVVK It works perfect! Thank you very much.
... View more
09-19-2020
06:32 AM
Hi @SashankRamaraju Parameter Context Groups(PMG) have to be added manually only. But, you can have a Parameter Context Group specific to environment. I mean, for example, a PMG with name 'Env variables' (say) has DEV values in DEV environment and PROD values in PROD environment. So, you will only be selecting the PMG 'Env variables' in all the environments, but, the config(values) is specific to environment. If it is mandatory to have 3 PMGs, selecting the PMG is manual, yet, if it is ok, you can use something like below. Generate FlowFile config: Generate FlowFile config UpdateAttribute config: UpdateAttribute config Here, I am trying to evaluate #{DEV_env}. And DEV is coming from the attribute env.
... View more
- « Previous
-
- 1
- 2
- Next »