Member since
01-07-2019
220
Posts
23
Kudos Received
30
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
4576 | 08-19-2021 05:45 AM | |
1676 | 08-04-2021 05:59 AM | |
828 | 07-22-2021 08:09 AM | |
3396 | 07-22-2021 08:01 AM | |
3081 | 07-22-2021 07:32 AM |
02-03-2021
08:22 AM
Apologies to disturb this old thread, but it seems people are still landing on this via search: The discussion here is outdated, especially the exclusions around gateway nodes. Please contact your Cloudera Representative for the latest terms an conditions.
... View more
02-01-2021
06:49 AM
I am not sure if I understand fully what you are trying to achieve, but here are some solution directions that come to mind: 1. Use regex to match the attribute name, perhaps with anyMatchingAttribute https://nifi.apache.org/docs/nifi-docs/html/expression-language-guide.html#anymatchingattribute 2. Cast the attribute name to lower, this may indeed require a script.
... View more
02-01-2021
06:32 AM
This can likely not be resolved without much more detail, so it may be good to log a support ticket for this. The first thing that comes to mind: Are you able to use the rest API at all, does your request reach the node or is there possibly a problem in getting the request there (Firewall, hostname, typo).
... View more
02-01-2021
06:27 AM
9 out of 10 times this message is caused because you run the GetHDFS on multiple nodes. Both nodes see it, perhaps even try to pick it up, but clearly not both of these can delete it. In old versions of NiFi you can fix this by setting the GetHDFS to run only on the primary node. However, that will ofcourse burden the primary node more than it should. So in recent versions (and likely yours) you will find the ListHDFS and FetchHDFS processors (and similar sets for different data sources). The lightweight List processor can then run on the primary node, and loadbalance to all nodes which will then Fetch.
... View more
02-01-2021
06:24 AM
As you can see the Mergecontent processor has several parameters for ensuring messages with a commonality get merged. https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.MergeContent/index.html This could be used in the way that you let each of the two processors give the messages an attribute, and only merge things with the same attribute. You appear to be looking for the opposite. I am not aware of any such parameter, and am also not sure if this is in the spirit of what mergecontent was designed for. Perhaps it is time to step back and see if mergecontent (or even NiFi) is the best tool for this specific job.
... View more
02-01-2021
06:20 AM
What you describe does not (yet) appear to conflict with the explanation in the linked thread. It seems that NiFi attempts to load balance when needed. Perhaps try routing your incoming messages through some heavy processors to the node which receives them consumes it's resources fast and see if it starts to load balance once you are hitting the limits.
... View more
02-01-2021
06:16 AM
I will try to nudge you in the right direction without spoiling everything: Q1: Look into attributes, you could think of having a processor give an attribute to the flowfile when it is loaded in, this can later be used to route or name files. Q2: If it is possible to use recordbased processors and avoid splitting files into individual records...do it. It can be 100x more efficient. Q3: Nifi is great for working with individual messages, not so much for working with context (e.g. is a message a duplicate). I suppose you could do some kind of lookup of new messages against existing messages...but you should avoid this where possible. Think about something like spark/flink or even python or SQL batch solutions to detect duplicates. Q4: I don't think you will soon run into NiFi limitations here, the question is probably more what file format can take all the updates and still perform well enough.
... View more
02-01-2021
06:08 AM
The first thing I would recommend, is attempting to avoid a custom processor. If you need to add columns to a record, the UpdateRecord processor should enable this. (At first I expected the QueryRecord processor to do it as well, but am unable to find any references to this). https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.5.0/org.apache.nifi.processors.standard.UpdateRecord/index.html https://community.cloudera.com/t5/Support-Questions/Adding-columns-to-sql-in-nifi/td-p/224598
... View more
02-01-2021
06:02 AM
The first thing to check is if your version of the platform supports your version of OpenJDK. For instance, if you are on HDF 3.5 or below, then OpenJDK does not appear to be supported: https://supportmatrix.hortonworks.com/ However, if you are on the latest Flow Management version in CDP, then OpenJDK 11.0.8 and above should be fine, as per https://docs.cloudera.com/cfm/2.0.4/support-matrix/topics/cfm-system-requirements.html If you confirmed that you are within the right combination of platform and JDK version and the problem still persists I would recommend to log a support ticket (I did not find other occurances of this error).
... View more
01-31-2021
01:50 PM
Unfortunately most sources are in Dutch but for good measure I will explain the most important data points: 1. Total weekly new covid infections come from the RIVM (dutch official body): https://www.rivm.nl/coronavirus-covid-19/archief-corona-updates 2. For the week of 26 jan, it is mentioned in an article by the RIVM that over one third of the current new infections is of the British Variant: https://www.rivm.nl/nieuws/Britse-variant-wint-terrein-in-Nederland 3. The same article mentions the rate was 8.6% in the period of 4-10 jan These are the most important points, and already show the trend. However, here are the additional sources: 4. In 'early december' the rate was about 1% according to this article on the largest news site of the country: https://www.nu.nl/coronavirus/6101869/wat-weten-we-nu-van-de-britse-coronavariant-ja-die-is-echt-besmettelijker.html 5. In a national press conference on 12 Jan, the minister of health indicated that in the past period the rate was between 2-5%. More frequent updates confirmed that there was steady growth in this period, so for the period between 9 and 29 december, there was likely growth from about 2% to about 5%. This could be off by one or two percentage points. 6. Though there was no clear source, several news sites recently referred to a current rate of 20%, this was likely observed between 13 and 19 jan.
... View more