Member since
06-26-2015
505
Posts
129
Kudos Received
114
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
825 | 09-20-2022 03:33 PM | |
2615 | 09-19-2022 04:47 PM | |
1501 | 09-11-2022 05:01 PM | |
1623 | 09-06-2022 02:23 PM | |
2455 | 09-06-2022 04:30 AM |
07-31-2022
02:46 PM
@mohammad_shamim , Any errors or warnings on the Sentry logs? What about the HS2 logs? Cheers André
... View more
07-31-2022
02:45 PM
@hegdemahendra , Have you checked the NiFi logs? Are there any errors or warnings in there? Cheers, André
... View more
07-31-2022
02:44 PM
@NJK , The availability of Atlas (and the number of nines you get) will depend on your implementation. Check this page for more information on Atlas high availability options. The more independent server you have backing the Atlas service, the more nines you'll get. Cheers, André
... View more
07-13-2022
11:20 PM
1 Kudo
@Lewis_King , Here's an idea. You can fork the "a" output of the QueryRecord processor and send it to a sequence of processors as shown below: The ReplaceText processor will simply replace the entire contents of the flowfile with the information you want to register in the log. For example: This will produce one row per flow file with the source type ("a") and the timestamp. You can them send these to a MergeRecord to avoid saving to many small log files and them to a PutFile to persist the log. You can process the "b" output in a similar way. Cheers, André
... View more
07-13-2022
10:48 PM
@Lewis_King , Do you want to append one row for each flowfile or one row for each processed record to this log? André
... View more
07-13-2022
06:44 PM
@Lewis_King , > Keep a log of all SQL commands... What do you mean by the above? The QueryRecord processor always executes the same SQL query, which you configure in the processor as a relationship. The SQL query doesn't change; what changes are the flowfiles that go through the processor. Cheers, André
... View more
07-13-2022
06:45 AM
1 Kudo
@MarioFRS , You can set it to the following: @([^@]*)@ Cheers, André
... View more
07-13-2022
06:42 AM
@AbhishekSingh , You can use the following expression instead to format the date as you want in the UpdateRecord processor: /subscription_start_at_timestamp -> format(toDate(/subscription_start_at, "EEE MMM d HH:mm:ss z yyyy"), "yyyy-MM-dd HH:mm:ss") Cheers, André
... View more
07-12-2022
07:49 PM
@AbhishekSingh You can use the UpdateRecord processor for this with the following configuration: /is_deleted_bool -> contains(/is_deleted, "{1}")
/subscription_start_at_timestamp -> toDate(/subscription_start_at, "EEE MMM d HH:mm:ss z yyyy") The output of that will look like the below: [ {
...
"subscription_start_at" : "Wed Oct 13 15:58:58 IST 2021",
...
"is_deleted" : "{0}",
...
"is_deleted_bool" : false,
"subscription_start_at_timestamp" : "1634133538000"
} ] Cheers, André
... View more
07-12-2022
07:13 PM
1 Kudo
@Lewis_King , This error means that some line(s) in your flowfile have less than 4 fields. Empty lines are typically ignored but if you have a trailing line, for example, with a space in it, that space will be interpreted as the first field (GradeNm) and the other fields will be missing, which could lead to this sort of problem. Check your input file for trailing lines or lines with less than 3 commas in it. If the problem is being caused by a blank line with spaces, for example, you could use the ReplaceText processor to remove those spaces, as shown below: Cheers, André
... View more