Member since
06-26-2015
515
Posts
140
Kudos Received
114
Solutions
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 2589 | 09-20-2022 03:33 PM | |
| 7006 | 09-19-2022 04:47 PM | |
| 3695 | 09-11-2022 05:01 PM | |
| 4314 | 09-06-2022 02:23 PM | |
| 6833 | 09-06-2022 04:30 AM |
04-05-2022
07:43 AM
@araujo do you have any suggestion for this case ?
... View more
03-31-2022
07:20 PM
You could also have 2 Flows under 1 group. First flow gets the token and caches it .. second retrieves cached token to use where needed.
... View more
03-31-2022
10:06 AM
1 Kudo
Hi André, That is what I needed. Thanks a lot. For those who are facing the same problem in windows; @araujo's solution also works with Powershell
... View more
03-30-2022
02:14 AM
1 Kudo
@PabloO , In Kafka's terminology, a topic is a "distributed logs". The data for each topic's partitions is saved in what's called "log segment files". So, the "log.dirs" and "log.dir" parameters point to the directories where the actual messages are saved, *not* the "error logs". For example, if your "log.dirs" is set to "/data1" and you have a topic named "mytopic". The data for the partition 0 of that topic will be saved in files under the directory "/data1/mytopic-0". Cheers, André
... View more
03-29-2022
06:00 PM
Hi @inyongkim , At the moment this connector has no controls to adjust the flushing mechanism. We're aware of that and Cloudera is working on making that more configurable so that it does not create a small file problem in your destination cluster. Cheers, André
... View more
03-29-2022
04:44 PM
@sheep , You need to add an EvaluateJsonPath processor before your PutHBaseJson to extract the value that you need and save it as an attribute in the flowfile. For example, you could get the value from $.field1.nestedfield and save that as the attribute mynestedfieldvalue. You can then refer to that attribute in your PutHBaseJson processor as ${mynestedfieldvalue}. Please check out this other answer to a similar question: https://community.cloudera.com/t5/Support-Questions/Hash-key-value-missing-putdynamodb-nifi/m-p/339622/highlight/true#M233139 Cheers, André
... View more
03-29-2022
05:49 AM
Thanks, everyone, for the help.
... View more
03-27-2022
11:07 PM
Hi @araujo Many thanks for the explanation, please note M1 doesn't have Virtual box that is the reason i have chosen Docker from the 2nd link you provided do you have any other alternate solution instead of Virtual box ? 1st option - no since its trail 60 days
... View more
03-27-2022
03:42 PM
@mystefied_ , You can download the CDP Trial version from the Cloudera website below: https://www.cloudera.com/downloads/cdp-private-cloud-trial/cdp-private-cloud-base-trial.html Cheers, André
... View more
03-25-2022
10:25 PM
@Boss , These are upper bound values to ensure that the services running on the machine won't run into limitations on the number of processes or open file descriptors. IMO, these are really pertinent parameters when you have gateway servers where tens or hundreds users connect to to run their own processes and you want to make sure no single user will run rogue processes that will starve everyone else of resources. The hosts in a CDP cluster enviroment are typically not hosts where users should be connecting directly to. The services and processes that run on those hosts are well known and managed by the administrator. In this scenario, these parameter are not as critical and we usually set them to a value that get them "out of the way", so that that we never reach them. Specifically to answer your question, though: "nofile" is the limit of open file descriptors. Note that file descriptors are not only associated to files; for example, they are also used to refer to open network sockets/ports and pipes. You can check the file descriptors currently open using the command "lsof" "nproc" is the limit of running processes. You can check that with the command "ps". Cheers, André
... View more