anchor.diff:  3. Save the information that you gathered above.
   
   
  -## <a id="id_cfg_prop"></a>Initializing, Configuring, and Starting PXF
  +## <a id="id_cfg_prop"></a>Configuring and Starting PXF
   
   PXF does not use the following `gphdfs` configuration options:
   
   | gphdfs Configuration Option | Description |  pxf Consideration |
   |----------+---------------+------------|
   | HADOOP_HOME | Environment variable that identifies the Hadoop installation directory | Not applicable; PXF is bundled with the required dependent Hadoop libraries and JARs | 
  -| CLASSPATH | Environment variable that identifies the locations of Hadoop JAR and configuration files | Not applicable, PXF automatically includes the Hadoop libraries, JARs, and configuration files that it bundles in the `CLASSPATH`. PXF also automatically includes user-registered dependencies found in the `$PXF_CONF/lib` directory in the `CLASSPATH`. | 
  +| CLASSPATH | Environment variable that identifies the locations of Hadoop JAR and configuration files | Not applicable, PXF automatically includes the Hadoop libraries, JARs, and configuration files that it bundles in the `CLASSPATH`. PXF also automatically includes in the `CLASSPATH` user-registered dependencies found in the `$PXF_CONF/lib` (PXF 5.x) or `$PXF_BASE/lib` (PXF 6.x) directory. |
   | gp_hadoop_target_version | Server configuration parameter that identifies the Hadoop distribution | Not applicable, PXF works out-of-the-box with the different Hadoop distributions | 
   | gp_hadoop_home | Server configuration parameter that identifies the Hadoop installation directory | Not applicable, PXF works out-of-the-box with the different Hadoop distributions | 
   
  
positive.code: 
  | Configuration Item | Description | gphdfs Config | pxf Config |
  |----------+-------------+---------------+------------|
  | JAVA_HOME | Environment variable that identifies the Java installation directory | Set `JAVA_HOME` on each segment host | Set `JAVA_HOME` on each segment host | 
  | JVM option settings | Options with which to start the JVM | Set options in the `GP_JAVA_OPT` environment variable in `hadoop_env.sh` | Set options in the `PXF_JVM_OPTS` environment variable in `$PXF_CONF/conf/pxf-env.sh` | 
  | PXF Server | PXF server configuration for Hadoop | Not applicable | Configure a PXF server for Hadoop | 
  | Privileges | The Greenplum Database privileges required to create external tables in the given protocol | Grant `SELECT` and `INSERT` privileges on the `gphdfs` protocol to appropriate users | Grant `SELECT` and `INSERT` privileges on the `pxf` protocol to appropriate users | 
  
  After you determine the equivalent PXF configuration properties, you will:
  
  1. Update the Java version installed on each Greenplum Database host, if necessary. PXF supports Java version 8. If your Greenplum Database cluster hosts are running Java 7, upgrade to Java version 8 as described in [Installing Java for PXF](../../pxf/5-15/install_java.html).
  
  2. Initialize PXF as described in [Initializing PXF](../../pxf/5-15/init_pxf.html).
  
      You must initialize PXF before you can access Hadoop.
  
  3. [Configure the PXF Hadoop Connectors](../../pxf/5-15/client_instcfg.html). This procedure creates a PXF server configuration that provides PXF the information that it requires to access Hadoop.
  
  4. Start PXF in your Greenplum Database cluster as described in [Starting PXF](../../pxf/5-15/cfginitstart_pxf.html#start_pxf).
  
  
negative.code: To migrate your `gphdfs` external tables to use the `pxf` external table protocol, you:
  
  1. [Prepare](#prepare) for the migration.
  2. Map configuration properties, then [configure and start PXF] (#id_cfg_prop).
  3. [Create](#create_pxf_ext_table) a new `pxf` external table to replace each `gphdfs` external table.
  4. [Verify](#verify_pxf) access to Hadoop files with the `pxf` external tables.
  5. [Remove](#remove_gphdfs_ext_table) the `gphdfs` external tables.
  