Member since
07-29-2020
574
Posts
323
Kudos Received
176
Solutions
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 3537 | 12-20-2024 05:49 AM | |
| 3789 | 12-19-2024 08:33 PM | |
| 3583 | 12-19-2024 06:48 AM | |
| 2328 | 12-17-2024 12:56 PM | |
| 3086 | 12-16-2024 04:38 AM |
06-16-2022
09:14 AM
What the screenshot is telling that its still initializing the data flow, so give it some time and refresh.
... View more
06-16-2022
07:24 AM
Sorry I forgot to mention that in the PutSql processor set the Batch Size property to 1
... View more
06-16-2022
07:07 AM
Have you added the nodes in the authorizers.xml under userGroupProvider and AccessPolicyProvider
... View more
06-16-2022
07:04 AM
Im not familiar with the postgress sql but should not be like this: INSERT INTO table(column1, column2, …)
VALUES
(value1, value2, …); Also for the value you need to provide the attribute name , so it should be something like this: INSERT INTO table(jsonDataColumn) VALUES(${data});
... View more
06-16-2022
06:58 AM
Not sure if this is related , but if you are setting up a secure cluster the property nifi.cluster.protocol.is.secure should be true. If not just make sure you follow steps mentioned in the following url and you have not missed anything: https://nifi.apache.org/docs/nifi-docs/html/walkthroughs.html#creating-and-securing-a-nifi-cluster-with-the-tls-toolkit
... View more
06-16-2022
06:29 AM
The way PutDatabaseRecord works is basically once it reads the json , it will try to match the json keys to the DB columns hence the error you are getting if not being able to map fields to columns, in your case it will be looking for columns: name & surename to store their values, so it wont store the whole json in one field. I had similar situation where I needed to store json and the only way I can think of is first load the json into an attribute using the ExtractText Processor, then use PutSQL processor and write the insert statement to the target table where the column is the Data and the value is the attribute contain the json value for example ${JsonDataAttribute}. You have to be careful how big your json is, if its too big then you have to figure out another way, but if its small then no harm from saving into an attribute.
... View more
06-16-2022
05:55 AM
Hi, Can you explain what happen when you use the PutDatabaseRecrod Processor?
... View more
06-15-2022
05:59 AM
Hi, It could be an encoding issue that I faced a while back. please check out this post: https://community.cloudera.com/t5/Support-Questions/Illegal-Arg-Exception-when-parsing-CSV-file-though-the-split/td-p/300565 Try to change the character set to UTF-16 to see if that will work. Hope that helps. Thanks
... View more
06-14-2022
10:06 AM
first you need to check if there is an attribute called filename on the original flowfile and its the same passed the output stream flowfile. If there is, then you should specify it as "filename" in the merge content property and NOT as "${filename}".
... View more
06-14-2022
07:42 AM
how is the original flowfile is generated. usually you should have filename attribute set by default on the original flowfile. this should be unique for the flowfile and this filename could be passed to the output stream, can you check that?
... View more