Member since
07-19-2018
613
Posts
100
Kudos Received
117
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
3704 | 01-11-2021 05:54 AM | |
2586 | 01-11-2021 05:52 AM | |
6987 | 01-08-2021 05:23 AM | |
6437 | 01-04-2021 04:08 AM | |
29523 | 12-18-2020 05:42 AM |
08-29-2018
11:24 AM
@Marshal Tito what you describe sounds like an easy task to accomplish using NiFi to execute the HQL statement, capture a value, make the webservice call, and proceed. If this answer is helpful please choose ACCEPT to mark the question as answered.
... View more
08-29-2018
11:18 AM
See the following links for more information: https://community.hortonworks.com/questions/120941/recursive-query-or-better-way-to-build-hierarchica.html https://blog.pythian.com/recursion-in-hive/ https://stackoverflow.com/questions/38765543/recursive-query-in-hive
... View more
08-28-2018
02:14 PM
1 Kudo
Using port 465 here with SMTP TLS set to false
... View more
08-27-2018
01:28 PM
@Mitthu Wagh In order for us to reply specifically you need to completely explain your Use Case Scenario. What format(s) is the CRM Source Data, etc.. ? That said, there are many different ways to get data into Hive using NiFi's Hive Processors and NiFi is an excellent tool to complete your task. I would recommend that you start by searching the HCC for articles and how-tos for Nifi + Hive. Here is a direct link: https://community.hortonworks.com/search.html?f=&type=kbentry&redirect=search%2Fsearch&sort=relevance&q=nifi+hive If this answer is helpful, please choose ACCEPT to mark your question as answered.
... View more
08-27-2018
12:15 PM
Excellent Answer!! Thank you I had forgotten about the archive history. I was able to restore the file too. It appears only the last 7 lines of xml were missing. After fixing the xml, making a new flow.xml.gz, copying that back into /var/lib/nifi/conf, and restarting NiFi my workflow is restored. Was not really able to find a lot of matches here or online for "Cannot load flow.xml.gz" so I wanted to create this thread for anyone having these issues in the future.
... View more
08-27-2018
11:51 AM
1 Kudo
Recently had some disk issues with a NIFI node. Around the same time the cluster was yum updated causing additional issues. Once the cluster was back online all the services are restarted accept for NiFi. Within the nifi log i was able to find: Cannot load flow.xml.gz Moving the file (mv /var/lib/nifi/conf/flow.xml.gz to /var/lib/nifi/conf/flow.xml.gz.off) I was able to restart NiFi. Of course now my workflow has now been reset. When I attempt to unpack the flowfile I get the following error: gzip: flow.xml.gz: unexpected end of file When I attempt to force the output(gunzip -c flow.xml.gz) I can see valid XML up to the point of error including the processor group I want to recover. Is it possible to extract the xml objects from the output and rebuild the flow.xml.gz? I have most of my major work backed up with a template, but there is at least one processor group I was working on that was not saved as a template.
... View more
Labels:
- Labels:
-
Apache NiFi
08-23-2018
11:47 AM
@Aymen Rahal Quite a few errors in the output above. Seems the important one is: Path "/usr/share/logstash/data" must be a writable directory. It is not writable. After setting the permissions of /usr/share/logstash/data your command line should work. However, I would suggest to run Logstash as its proper installed service, with configuration files in /etc/logstash.
... View more
08-22-2018
11:21 AM
As mentioned below: you need to verify the nifi host can see that domain and resolve the url. Another thing you might want to do is tail the nifi log while testing and debugging, it often has more helpful information than the red alert box. Once you have the error, search it here in the HCC and make a new question.
... View more
08-21-2018
02:33 PM
@Veerendra Nath Jasthi You probably want it before PutEmail. Your ExecuteScript should be able to set flowfile content or attributes based on the configuration of the script. If you dont need to pass other attributes into putEmail, i would write the ProcessGroupName, Process ID, and Timestamp to flowfile content. Then use MergeContent to join multiple instances of the errors into a single flow file, and pass this to PutEmail. Hope this makes sense. I would also recommend trying to resolve the errors. A good NiFi Data Flow should not have any errors or should be fault tolerate with a method to route the failures back into the flow. Search HCC for "executescript cookbook" to find a great 3 part article on ExecuteScript.
... View more
08-21-2018
11:31 AM
@Bharath
Sudharsanam
If you have not already, please review this 3 part series on ExecuteScript. It was very helpful for me when I was working with my custom script and ExecuteScript Processor. https://community.hortonworks.com/content/kbentry/75032/executescript-cookbook-part-1.html
... View more