@gbrfilipe You should be able to very easily install 1.21 on a new machine with ssl enabled.  When you do the first startup, nifi will report out the user and password required in the app log:     Generated Username [75db8691-953c-4b96-b488-da2d3abf1b9d] Generated Password [GHl/n4A7RUBKsM48TO0sLxjElR9HJPsR] org.apache.nifi.web.server.JettyServer https://127.0.0.1:8443/nifi You would swap in your EC2 instance host.       If nifi is running, and you are still unable to access it via the EC2 host, this is most definitely aws firewall configs.    I would not use an old version or non https nifi to evaluate. ... View more

@tqiu No, there is no more HDP.  That product is end of life.  Please check out how to upgrade HDP to CDP.     https://docs.cloudera.com/upgrade-companion/cdp_upgrade.html         ... View more

Let's take this a different direction... open up a code box in your reply.  Choose Preformatted:   Insert Lines 0 - 11 here Remove anything sensitive of course.  ... View more

@bhadraka It does not appear like this can be achieved with our CSVReader.   See this JIRA looking for a feature to set the skip rows: https://issues.apache.org/jira/browse/NIFI-8932   If your data's "10 rows" is always known and the same you could use a ReplaceText to get only 11+ rows.   You would match that text, and not replace it, just take the rest.        If the first 10 rows are just ignored and of the same structure as all rows, ie not some prepending lines with headers, etc; you could also use a CSV Reader and program your flow to simply ignore the first 10 flow files.     ... View more

@john0123 There are several ways to include values with the InvokeHttp call.  Custom values in the host/url is not preferred as they may not be noticed there.  Try to add productId as a user-defined property. Click the (+) on properties and create it there.    Then test again. ... View more

@sahil0915 It is not clear what you are asking for here.      Using Nifi to do this replication, you would be well aware of any records that fail as that is the nature of nifi and how nifi works.  NiFi data flows capture failures so you could easily be aware of any records that did not make if from dc1 to dc2 and dc3.  Additionally, nifi handles retries, so a replication flow should be resilient to failures, and notify you at that time versus having to fully audit it after replication.   If you are using a database technology that replicates across regions or some other replication method and intend to use nifi to check if the replication is complete or accurate, you are going to need to make a nifi flow that will pull all 3 data sets and compare.   At the 100 million record row this could be a pretty heavy process with 3 copies of all data coming into NiFi.     It would make more sense to me to allow nifi to handle the replication as described above and take the inherit fault tolerance. ... View more

A solution and a jira, excellent work gents!    ... View more

@janvit04 The pattern you need is this:   ${input_date:toDate("MM/dd/yyyy hh:mm:ss"):format("yyyy-MM-dd HH:mm:ss")} I did this in a test which you can find here.  In this example I have UpdateAttribute with an input attribute called input_date and its string value is  "8/6/2023 12:46 am".   In next UpdateAttribute i do the toDate and format.    With this setup you may need to modify the format in toDate function to match your input string until it gets right format.  For example I thought it should be m/d/yyyy but i got right output using MM/dd/yyyy.   ... View more