Member since
09-27-2018
138
Posts
23
Kudos Received
10
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
9734 | 02-28-2021 10:23 PM | |
1937 | 02-08-2021 11:53 PM | |
31753 | 12-16-2020 11:31 PM | |
7600 | 12-14-2020 11:02 PM | |
4841 | 12-14-2020 12:18 AM |
02-16-2021
09:13 AM
@BerniHacker The whole day I couldn't achive to work on this further. Now I found a solution but at the moment I can't document this detailed because "work is calling". In small words: GetFile -> UpdateAttribute (to set NiFi-attribute schema.name) -> PutDatabaseRecord (with CSV-Record Reader) BUT the reader has to use a schema which is defined in the controller services as AvroSchemaRegistry and there has to exist a avro schema for the structure. Maybe this will help you further. Have a look here https://community.cloudera.com/t5/Support-Questions/Loading-a-simple-CSV-file-using-nifi-PutDatabaseRecord-and/td-p/222678 Tomorrow I will describe my solution detailed! Sorry...
... View more
02-15-2021
11:11 PM
@BerniHacker Sorry, my reply was not good. Did not see that you are working with "Use String Fields From Header" and not a separate schema. I will try to get it work on my local installation. If you found a solution by so kind to let us know. Thanks.
... View more
02-15-2021
10:42 PM
@BerniHacker As far as I see the cause could be different column names and in the PutDatabaseRecord the option "Unmatched Column Behavior" is set to "Fail on Unmatched Columns". I suppose the options concerning "Unmatched Field Behavior" or "Unmatched Column Behavior" in connection with "Translate Field Names" causing your problem. Perhaps you like to post your schema-definition? But at the moment I can't give you a concreter answer.
... View more
02-08-2021
11:53 PM
Hi @Jarinek I think you have to set -pv in front of the new value: nifi set-param -u http://localhost:8088 -pcid 85b8b5bf-0177-1000-3881-8ddd8d31fed8 -pn sample.URL -pv newvalue This one worked on my local NiFi. Remark: Haven't seen that you found it yourself. Great!
... View more
02-08-2021
07:30 AM
Hi @ashwinrk maybe this information will help you further: https://community.cloudera.com/t5/Support-Questions/NiFi-InvokeHTTP-POST-JSON/m-p/307990#M223438 It depends on the concrete target whether the "Authorization" has to be base64encoded or you can use basic authentication.
... View more
02-01-2021
01:20 AM
1 Kudo
@believe7 One possibility is shown here. Maybe there is a more comfortable way, but this would be my solution. Flow Details processors Result response If you have further questions please let me know.
... View more
01-27-2021
03:42 AM
@VidyaSargur i have to change my email. Would you be so kind and get intouch with me? Thank you!
... View more
12-16-2020
11:44 PM
@stephane_davy Have only found the correct avro-schema for the JsonTreeReader (see above), unfortunately I failed at the output array definition. When trying to use an online generated output schema, errors occurred continuously. Hope that an avro-guru can come forward and help. I am looking forward to the solution, which I will find after my vacation in January. I'm outta here now, all the best!
... View more
12-16-2020
11:31 PM
2 Kudos
@GMAN Here is my try to help you further. flow Look at the picture of the InvokeHTTP. InvokeHTTP From my experience most options can mostly be left to default values. Your Json-body should be fine and will be send with the request. Remarks: - Authenticaton/Authorization: You have to try the two possibilities I know. For the second you have to add custom-property "Authorization" with the plus symbol on the right above. - Accept: Concerns the response format not sure wether you will need this. Maybe you can first build your request in Postman and after successfull execution then click to "code" -> "HTTP". There you can see the details needed for the request. In the "Settings" of the InvokeHTTP you can autoterminate the "original" flowfile. For "Retry" you can use the shown processor with default values. All "Failure" or "No retry" go to some error-handling. With "Response" you can go further in your flow. Hope this helps you to come forward.
... View more
12-16-2020
12:31 AM
@stephane_davy Found this https://stackoverflow.com/questions/54981540/nifi-recordreader-recordwriter-serialization-error-illegaltypeconversionexcep When I use your above JOLT-spec within JoltTransformJSON it works fine. No need of readers, writers, schemas. Output: [ {
"myfield" : "JustForHavingJson",
"myfield1" : "A",
"myfield2" : "C"
}, {
"myfield" : "JustForHavingJson",
"myfield1" : "B",
"myfield2" : "C"
}, {
"myfield" : "JustForHavingJson",
"myfield1" : "C",
"myfield2" : ""
}, {
"myfield" : "JustForHavingJson",
"myfield1" : "E",
"myfield2" : ""
}, {
"myfield" : "JustForHavingJson",
"myfield1" : "X",
"myfield2" : ""
}, {
"myfield" : "JustForHavingJson",
"myfield1" : "",
"myfield2" : ""
}, {
"myfield" : "JustForHavingJson",
"myfield1" : "D",
"myfield2" : "G"
} ]
... View more