Member since
07-19-2018
613
Posts
101
Kudos Received
117
Solutions
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 5093 | 01-11-2021 05:54 AM | |
| 3421 | 01-11-2021 05:52 AM | |
| 8789 | 01-08-2021 05:23 AM | |
| 8384 | 01-04-2021 04:08 AM | |
| 36687 | 12-18-2020 05:42 AM |
01-31-2020
06:38 AM
@VijaySankar did you get it solved?
... View more
01-28-2020
05:03 AM
Escape the "s in the json data object: "[{\"bin\": \"02608\",\"groupId\": \"52821094\"},{\"bin\": \"02609\",\"groupId\": \"528212387\"}]" Let us know if this works, and if it does please accept this answer.
... View more
01-28-2020
04:57 AM
1 Kudo
I would highly recommend to not use special characters in columns names. Per documentation hive .13 (link) `column?name` should work with Hive, however, there is no gauruntee that other clients, including SQL Workbench will allow this when the special character can be considered a code like character ($ % & ? " , . etc)
... View more
01-25-2020
06:08 AM
I’m the schema remove the second row in fields. So it’s just id1. Now do a test: use generateflowfile with the schema in contents. Then evaluatejson. In this processor click +, and make id1. The value for id1 is then $.value.id1 (this is the code to get the real value. Then route evaluatejson routes to an output port. Run. Inspect the item in the queue and confirm you see the attribute id1. This is a simple example to help you understand how json works, how to get the data from the value object, how to confirm schema is correct, and how to unit test by looking at flowfile in the queue.
... View more
01-24-2020
04:11 AM
1 Kudo
The FlowFile is not valid json. Try something like a basic json example found on the internet: {"results":[{"term":"term1"},{"term":"term2"}..]} Notice the object results is the array of values and everything is "quoted". Something like this based on your sample image: { "world_rank": "1", "country": "China", "population": "1388232694", "World": "0.185" } If you have to use what you have in the sample image, then you will need to extracText (link here for examples of regex to match values) to get the values for world_rank, country, population, world. Each values attribute regex like this: .*world_rank :(.*?) .*
.*country: (.*?) .*
.*population: (.*?) .*
.*world: (.*?) .* Then use attributesToJson to build the Json object of the attributes you defined above which you can then send to the reader and ultimately to MongoDb. If my reply helps you solve your Use Case, please accept it as a solution to close the topic.
... View more
01-23-2020
01:14 PM
1 Kudo
@MattWho best news I heard all day.... after I just finished my POC with new parquet reader/writer 1.10 in 1.9 nifi... was able to get 1.3 billion rows out of a single parquet file on a very small azure cluster!!
... View more
01-22-2020
03:18 AM
@saivenkatg55 Looks like “out of memory error”. You will need to update the min and max memory settings. They are current 128m and 256m Try 512m and 1024m and step up increments until it will start. If this reply solves your issue please mark this response as the accepted solution.
... View more
01-21-2020
02:10 PM
If it worked and you got the expected response, you can be sure the cert was used... i don’t think the cert will actually be “sent” but it is used on the Nifi side (client) to communicate “securely”... just make sure you get the expected response and not, for example, an http (not https) error page...
... View more
01-21-2020
06:11 AM
@Manus This is a perfect Use Case for Wait / Notify. You just need to be aware of the pitfalls, and recognize the behavior when your wait/notify condition doesn't act and of course test that the timeout condition works as needed. The beauty of NiFi is that you should be able to account for every possible scenario, and part of the fun in NiFi for me is being creative, being able to capture exceptions, and either further educate my existing flow to handle them, or by creating new parts of my flow specifically for the exceptions.
... View more
01-21-2020
06:06 AM
You should be able to accept your own reply as solution marking it closed/solved. One thing I do notice, which I HIGHLY recommend against is using "localhost"...
... View more