Member since
04-02-2020
16
Posts
0
Kudos Received
0
Solutions
04-22-2020
09:17 AM
check this https://community.cloudera.com/t5/Support-Questions/Apache-Nifi-username-password-for-Rest-Api/td-p/206404
... View more
04-22-2020
08:39 AM
I am also facing the same issue of not able to update mongo records using exiting _id . I just need to update 2-3 fields in existing mongo document
... View more
04-22-2020
08:37 AM
Can anyone share screenshot of the processor configuration to understand this solution.
... View more
04-22-2020
08:34 AM
Yup working now 🙂 Now i am stuck up in PutMongo to update the existing document in collection. Please see my question and help me . need a push here 🙂
... View more
04-19-2020
11:20 PM
Attached is the screenshot for the solution E2E Flow Generate Flow File InvokeHttp.
... View more
04-16-2020
01:16 PM
Hi for this flow can you share what was teh content of the flow file. and what was the configuration in put mongo. I am facing the same issues. Thanks Rupesh
... View more
04-15-2020
01:27 PM
Hi, Can you share the template with us or the screenshot on which attribute (created or updated) and how it was added to the header of InvokeHTTP. Please share , I am facing the same issue. Thanks Rupesh
... View more
04-08-2020
09:42 PM
Hi Ferenc, I am using nifi-1.11.4. The SSL is working for other team members running on the same version. I am importing the flow from Nifi registry over HTTP. All flows are using parameter context. Yes, your guess might be correct as without SSL , the processor comes up perfectly. Please let me know what specific information you need regarding SSL. I will get from the platform team. I do not want to face this situation when flow are deployed on production. Thanks Rups.
... View more
04-06-2020
09:01 PM
Attached is the java stack. I am getting this error in the nifi.log whenever i am starting GetFile processor which is first processort in my list.
2020-04-07 01:17:01,371 ERROR [Timer-Driven Process Thread-5] o.a.nifi.processors.standard.InvokeHTTP InvokeHTTP[id=51048885-0171-1000-9a41-00f55a11ae71] Failed to properly initialize Processor. If still scheduled to run, NiFi will attempt to initialize and run the Processor again after the 'Administrative Yield Duration' has elapsed. Failure is due to java.lang.IndexOutOfBoundsException: Index: 0, Size: 0: java.lang.IndexOutOfBoundsException: Index: 0, Size: 0 java.lang.IndexOutOfBoundsException: Index: 0, Size: 0 at java.util.ArrayList.rangeCheck(ArrayList.java:657) at java.util.ArrayList.get(ArrayList.java:433) at org.apache.nifi.processors.standard.InvokeHTTP.setUpClient(InvokeHTTP.java:665) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.apache.nifi.util.ReflectionUtils.invokeMethodsWithAnnotations(ReflectionUtils.java:142) at org.apache.nifi.util.ReflectionUtils.invokeMethodsWithAnnotations(ReflectionUtils.java:130) at org.apache.nifi.util.ReflectionUtils.invokeMethodsWithAnnotations(ReflectionUtils.java:75) at org.apache.nifi.util.ReflectionUtils.invokeMethodsWithAnnotation(ReflectionUtils.java:52) at org.apache.nifi.controller.StandardProcessorNode.lambda$initiateStart$4(StandardProcessorNode.java:1532) at org.apache.nifi.engine.FlowEngine$3.call(FlowEngine.java:123) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748)
Please share solution if any and also the reason for the error.
Thanks
Rups.
... View more
Labels:
- Labels:
-
Apache NiFi