About ask_bill_brooks

ask_bill_brooks · ‎07-22-2022

Since you're using an environment only deployed for a 60-Day trial, I don't think it will hurt anything to try manually initiating the user sync as a first attempt at a resolution. You can review the procedure for doing that here: Performing user sync

ask_bill_brooks · ‎07-21-2022

Hi @Ploeplse Your assumption that the 60-day trial of Public Cloud is a great way to get familiar with CDP is correct. You should be able to open a case with via the Cloudera Support portal and request the required administrative privileges granted to you. If for some reason you don't have the ability to open a support case, you'll have to reach out to the appropriate contact person in your organization who can open a support case and have them do it for you.

ask_bill_brooks · ‎07-18-2022

Hi @rafy You didn't say where you looked, or if the NiFi 1.16.3 installation you are running is in the public cloud, on premises or private cloud. What @DigitalPlumber wrote earlier is correct; one of my colleagues provided the following page shot from Cloudera DataFlow (CDF) on CDP Public Cloud: So the processors are clearly available. If for some reason you need to use Pulsar with some other distribution of NiFi, you can try checking the GiitHub repo here: Awesome Apache NiFi + Apache Pulsar

ask_bill_brooks · ‎07-16-2022

Hi @Gobind You didn't indicate where you downloaded that, or whose instructions you followed to "successfully [install] Cloudera in Oracle VM VirtualBox Manager". But I can tell you that the screen shot you've posted is not an error. At this point in time or later, you (or anyone else reading this) should not be attempting to run the QuickStart VM on VirtualBox. The Cloudera Quickstart VM has been discontinued and has been obsolete for some time now, as it was based on CDH 5.13 which reached end of support in the Fall of 2020. Note that Cloudera never supported the QuickStart VM officially and again, it's been obsolete for years now. Cloudera's current Enterprise Data Platform is Cloudera Data Platform (CDP), which in it's on-premises "form factor" was released back on November 22, 2019, over two and a half years ago. CDP supersedes CDH as Cloudera's data platform offering. The on-premises "form factor" of CDP is now called CDP Private Cloud. You can download a trial version of CDP Private Cloud to install on-premises here: CDP Private Cloud 60-day free trial.

ask_bill_brooks · ‎07-11-2022

Hi @Hanni You didn't mention what distribution or version of Hadoop you're using, but in general you have a few widely available options. If you prefer using a low-to-no-code data ingestion engine with a rich graphical user interface and support for processors that provide connectivity, transformation, and content routing, including for JSON, you should investigate Apache NiFi, which powers Cloudera Flow Management (CFM). I would say that's your all-around best alternative, because NiFi has a very complete set of readers and writers for dealing with JSON. If you have programming ability, another alternative would be to write a script using Spark SQL to ingest the data to HDFS. This will require the use of JDBC connectivity to the PostgreSQL DBMS just as Sqoop does. If you don't already know Spark, there's going to be a bit of a learning curve. Lastly, if the source PostgreSQL table allows it, you could try importing the data using the hcatalog import function, which is an approach that was discussed here quite a while ago, using Oracle as the source DBMS in this thread: Sqoop to write JSON in HDFS . I am not aware of anyone getting that approach to actually work in practice using PostgreSQL.

ask_bill_brooks · ‎06-21-2022

p>Hi @FediMannoubi I want to add a bit here and add on to what @ckumar wrote earlier in the thread. What tool did you capture the first screen shot from? Does that tool connect to the Postgresql database server via JDBC and using this Database Connection URL? jdbc:postgresql://127.0.0.1:5432/ATL2 I ask because if you had, that would validate that the connection string you are using is indeed valid. I strongly recommend that you carefully read the documentation for Connecting to the Database, as it has detailed information on how a valid JDBC connection string should be formed. Comparing the available forms described on that page, and comparing the options to the string that you have captured in your page shot, the relevant option for the PostgreSQL JDBC string in this case appears to me at least to be the following form: jdbc:postgresql://host:port/database If the string you've already entered into the Database Connection URL property works, then you can proceed assuming that the final characters are the "database" and so in your case the database would be ATL2 The first screen shot appears to indicate that the database is named rei. I don't know what to make of that difference.

ask_bill_brooks · ‎06-21-2022

Hi @Techie123 Hopefully after reading the link that @SAMSAL shared earlier, you've reached the understanding that no, you don't have to install the database on the same server as the server that NiFi is installed on, but of course the server hosting the database must be accessible to the NiFi server via the JDBC protocol, regardless of where it is located. There are any number of things that could be causing the error message that you are getting. Given what you have shared in this thread, I would recommend that you begin by talking to your DBA or perhaps the person that installed the database on the server. The string that you have entered on the properties tab, as shown in your page shot: jdbc:oracle:thin@hostname:portnumber:sname …needs to be replaced with the values appropriate for the server where your actual database is installed. To be a bit more specific, you have to get the actual literal values for hostname, portnumber and sname necessary to access your database and enter all of them correctly. In my personal experience, you'd also be much better off if you can verify that the database server is accessible via JDBC using some other tool so you have a way to validate the connection string before you get involved with NiFi-specific details.

ask_bill_brooks · ‎06-17-2022

@Uday_Singh2022 There won't be any documentation available from Cloudera regarding Flume because that lack of availability is part of what "not a supported component" means. If you must use Flume, then the documentation on the Apache site that @mszurap pointed you to above is your only option.

ask_bill_brooks · ‎06-15-2022

@Techie123 I strongly recommend that you read over this thread: Problem login for first time in Nifi …and then if you try all the troubleshooting steps described there, post again here, in this thread, and provide a link to the instructions you followed in order to perform your installation and for which version of NiFi.

ask_bill_brooks · ‎05-24-2022

Previously asked and answered in this thread: log4j2 vulnerability (CVE-2021-44228)

Member Since	‎07-29-2019 03:29 PM
Last Visited
Posts	640
Kudos received	108

Cloudera Community

Re: Vulnerability (Text4Shell) (CVE-2022-42889)

Re: ERROR orm.CompilationManager: Sqoop requires a...

Re: How to enable TEZ UI on CDP 7.1.7

Re: CDH HIVE download

Re: Nifi registry architecture.

Re: "View Jobs" not loading

Re: CDP trial version admin rights

Re: PublishPulsarRecord not found.

Re: error while running Cloudera in Oracle VM Virt...

Re: Json object with sqoop

Re: How to select schema in postgresql with NIFI

Re: How to Connect to the Relational Database in N...

Re: Apache Flume required to be run in CDP environ...

Re: NiFi Installation on co-operate Linux Server g...

Re: log4j2 failure (CVE-2021-44228) in cloudera