Configure Phoenix-Spark connector using Cloudera Manager

Follow Step 1 to Step 7(b) as mentioned in Configure HBase-Spark connector using Cloudera Manager.
Add the required properties to ensure that all required Phoenix and HBase platform dependencies are available on the classpath for the Spark executors and drivers.
Add the shaded Phoenix-Spark connector JARs to the spark.executor.extraClassPath and spark.driver.extraClassPath parameters. Do not add them to spark.jars or pass them with --jars.
important
Adding the shaded Phoenix-Spark connector through spark.jars or --jars can prevent HBase from loading org.apache.hadoop.hbase.ipc.controller.ClientRpcControllerFactory (Apache Phoenix PHOENIX-7132).
important
Ensure that you add the Phoenix-Spark connector JARs to the configuration properties and you do not remove any of these files added in Step 1.
Spark2:
```
spark.executor.extraClassPath=/opt/cloudera/parcels/cdh/lib/phoenix_connectors/phoenix5-spark-shaded.jar
spark.driver.extraClassPath=/opt/cloudera/parcels/cdh/lib/phoenix_connectors/phoenix5-spark-shaded.jar
```
Spark3:
```
spark.executor.extraClassPath=/opt/cloudera/parcels/cdh/lib/phoenix_connectors/phoenix5-spark3-shaded.jar
spark.driver.extraClassPath=/opt/cloudera/parcels/cdh/lib/phoenix_connectors/phoenix5-spark3-shaded.jar
```
Enter a Reason for change, and then click Save Changes to commit the changes.
Restart the role and service when Cloudera Manager prompts you to restart.

Build a Spark or Spark3 application using the dependencies that you provide when you run your application. If you follow the previous instructions, Cloudera Manager automatically configures the connector for Spark. If you have not:

Consider the following example while using a Spark2 application:

spark-shell --conf spark.driver.extraClassPath=/opt/cloudera/parcels/cdh/lib/phoenix_connectors/phoenix5-spark-shaded.jar --conf spark.executor.extraClassPath=/opt/cloudera/parcels/cdh/lib/phoenix_connectors/phoenix5-spark-shaded.jar --conf spark.jars=hdfs:///path/hbase_jars_common/hbase-site.xml.jar,hdfs:///path/hbase_jars_spark2/hbase-spark-protocol-shaded.jar,hdfs:///path/hbase_jars_spark2/hbase-spark.jar,hdfs:///path/hbase_jars_spark2/scala-library.jar,hdfs:///path/hbase_jars_common/hbase-shaded-mapreduce-***VERSION NUMBER***.jar,hdfs:///path/hbase_jars_common/opentelemetry-api-***VERSION NUMBER***.jar,hdfs:///path/hbase_jars_common/opentelemetry-context-***VERSION NUMBER***.jar

Consider the following example while using a Spark3 application:

spark3-shell --conf spark.driver.extraClassPath=/opt/cloudera/parcels/cdh/lib/phoenix_connectors/phoenix5-spark3-shaded.jar --conf spark.executor.extraClassPath=/opt/cloudera/parcels/cdh/lib/phoenix_connectors/phoenix5-spark3-shaded.jar --conf spark.jars=hdfs:///path/hbase_jars_common/hbase-site.xml.jar,hdfs:///path/hbase_jars_spark3/hbase-spark3-protocol-shaded.jar,hdfs:///path/hbase_jars_spark3/hbase-spark3.jar,hdfs:///path/hbase_jars_common/hbase-shaded-mapreduce-***VERSION NUMBER***.jar,hdfs:///path/hbase_jars_common/opentelemetry-api-***VERSION NUMBER***.jar,hdfs:///path/hbase_jars_common/opentelemetry-context-***VERSION NUMBER***.jar