1. Identify compatible version 2. Backup of the existing Cloudera PostgreSQL JDBC driver files(postgresql-42.3.2.jar,postgresql-42.3.3.jar, postgresql-42.2.16.jar) 3. Download the new PostgreSQL JDBC driver files(postgresql-42.6.0.jar, postgresql-42.2.27.jre7.jar, and postgresql-42.3.8.jar). 4. Stop Cloudera services using the Web-UI and command(I do not understand how to Stop Cloudera services using the PostgreSQL JDBC driver) 5. Replace old JAR files: /opt/cloudera/parcels/CDH-7.1.8-1.cdh7.1.8.p0.30990532/jars/postgresql-42.3.2.jar /opt/cloudera/parcels/CDH-7.1.8-1.cdh7.1.8.p0.30990532/jars/postgresql-42.3.3.jar /opt/cloudera/parcels/CDH-7.1.8-1.cdh7.1.8.p0.30990532/jars/postgresql-42.2.16.jar with the new ones /opt/cloudera/parcels/CDH-7.1.8-1.cdh7.1.8.p0.30990532/jars/postgresql-42.6.0.jar /opt/cloudera/parcels/CDH-7.1.8-1.cdh7.1.8.p0.30990532/jars/postgresql-42.3.8.jar /opt/cloudera/parcels/CDH-7.1.8-1.cdh7.1.8.p0.30990532/jars/postgresql-42.2.27.jre7.jar 6. Ensure new JAR files have correct permissions. 7. Start services: Restart Cloudera services. Then the schema registry server will has problem. It do run for a while, and it fail. I cannot successfully restart the schema registry server without put back the old jar file to the folder(/opt/cloudera/parcels/CDH-7.1.8-1.cdh7.1.8.p0.30990532/jars/)
... View more
