chaincode becomes active on a channel. • More deliberate chaincode upgrade process In the previous chaincode lifecycle, the upgrade transaction could be issued by a single organization, creating a risk for a chaincode to be upgraded only after a sufficient number of organizations have approved the upgrade. • Simpler endorsement policy and private data collection updates Fabric lifecycle allows you to additional upgrade considerations. Rest assured though, that rolling upgrades from v1.4.x to v2.x are supported, so that network components can be upgraded one at a time with no downtime. The upgrade docs have

chaincode becomes active on a channel. • More deliberate chaincode upgrade process In the previous chaincode lifecycle, the upgrade transaction could be issued by a single organization, creating a risk for a chaincode to be upgraded only after a sufficient number of organizations have approved the upgrade. • Simpler endorsement policy and private data collection updates Fabric lifecycle allows you to additional upgrade considerations. Rest assured though, that rolling upgrades from v1.4.x to v2.x are supported, so that network components can be upgraded one at a time with no downtime. The upgrade docs have

chaincode becomes active on a channel. • More deliberate chaincode upgrade process In the previous chaincode lifecycle, the upgrade transaction could be issued by a single organization, creating a risk for a chaincode to be upgraded only after a sufficient number of organizations have approved the upgrade. • Simpler endorsement policy and private data collection updates Fabric lifecycle allows you to additional upgrade considerations. Rest assured though, that rolling upgrades from v1.4.x to v2.0 are supported, so that network components can be upgraded one at a time with no downtime. The upgrade docs have

smart contracts, and new options for operating nodes. What has stayed the same is the ability to upgrade network components on your own terms, with support for rolling upgrades from v1.4.x, and the ability chaincode becomes active on a channel. • More deliberate chaincode upgrade process In the previous chaincode lifecycle, the upgrade transaction could be issued by a single organization, creating a risk for a chaincode to be upgraded only after a sufficient number of organizations have approved the upgrade. • Simpler endorsement policy and private data collection updates Fabric lifecycle allows you to

chaincode becomes active on a channel. • More deliberate chaincode upgrade process In the previous chaincode lifecycle, the upgrade transaction could be issued by a single organization, creating a risk for a chaincode to be upgraded only after a sufficient number of organizations have approved the upgrade. • Simpler endorsement policy and private data collection updates Fabric lifecycle allows you to additional upgrade considerations. Rest assured though, that rolling upgrades from v1.4.x to v2.0 are supported, so that network components can be upgraded one at a time with no downtime. The upgrade docs have

smart contracts, and new options for operating nodes. What has stayed the same is the ability to upgrade network components on your own terms, with support for rolling upgrades from v1.4.x, and the ability chaincode becomes active on a channel. • More deliberate chaincode upgrade process In the previous chaincode lifecycle, the upgrade transaction could be issued by a single organization, creating a risk for a chaincode to be upgraded only after a sufficient number of organizations have approved the upgrade. • Simpler endorsement policy and private data collection updates Fabric lifecycle allows you to

157 Resolved Issues 158 Server 158 Query Processing 159 Cluster Management 159 Data Flow 159 Upgrade 159 Release 6.24 160 Release 6.24.6 160 Query Processing 160 Server 160 Release 6.24.5 160 Changed Features 161 Resolved Issues 161 Server 161 Cluster Management 161 Query Processing 161 Upgrade 162 Release 6.24.3 162 Changed Features 162 Resolved Issues 162 Server 162 Query Processing Prerequisites 457 Upgrading from 6.x to a Newer 6.x Release 458 Troubleshooting a Failed Upgrade 460 PXF Upgrade and Migration 460 Migrating PXF from Greenplum 5.x to 6.x 461 Prerequisites 461 Step

Greenplum 6 Documentation VMware, Inc. 3 Query Processing 145 Cluster Management 146 Data Flow 146 Upgrade 146 Release 6.24 146 Release 6.24.6 146 Query Processing 146 Server 147 Release 6.24.5 147 Changed Features 147 Resolved Issues 147 Server 147 Cluster Management 148 Query Processing 148 Upgrade 148 Release 6.24.3 149 Changed Features 149 Resolved Issues 149 Server 149 Query Processing Prerequisites 438 Upgrading from 6.x to a Newer 6.x Release 439 Troubleshooting a Failed Upgrade 441 PXF Upgrade and Migration 441 Migrating PXF from Greenplum 5.x to 6.x 442 Prerequisites 442 Step

Prerequisites 462 Upgrading from 6.x to a Newer 6.x Release 463 Troubleshooting a Failed Upgrade 466 PXF Upgrade and Migration 466 Migrating PXF from Greenplum 5.x to 6.x 466 Prerequisites 467 Step Greenplum 6 Documentation VMware, Inc 19 Upgrading PXF When You Upgrade from a Previous Greenplum Database 6.x Version 476 Step 1: PXF Pre-Upgrade Actions 477 Step 2: Registering or Upgrading PXF 477 Migrating Wrapper Helper Functions 640 Greenplum Database Considerations 641 Building a Foreign Data Wrapper Extension with PGXS 642 Deployment Considerations 644 Using the Greenplum Parallel File Server (gpfdist)

Prerequisites 447 Upgrading from 6.x to a Newer 6.x Release 447 Troubleshooting a Failed Upgrade 450 PXF Upgrade and Migration 450 VMware Tanzu Greenplum 6 Documentation VMware, Inc 18 Migrating PXF Privileges to the gphdfs Protocol 460 Upgrading PXF When You Upgrade from a Previous Greenplum Database 6.x Version 460 Step 1: PXF Pre-Upgrade Actions 461 Step 2: Registering or Upgrading PXF 461 Migrating Wrapper Helper Functions 617 Greenplum Database Considerations 618 Building a Foreign Data Wrapper Extension with PGXS 619 Deployment Considerations 620 Using the Greenplum Parallel File Server (gpfdist)