The Arrow Flight SQL connector (Server execution type) uses active and pending environments, consistent with the data analytics fabric versioning framework. This allows you to deploy and validate a new connector version in the pending environment while production workloads continue to run on the active version.
After testing and validation are complete, promote the pending version to active. This provides a seamless upgrade with minimal disruption to users and applications. The process helps reduce upgrade risk, supports controlled rollouts, and maintains production stability throughout the connector lifecycle.
| Property | Description |
|---|---|
| Flight Server Active Port | Use this setting to specify the port for the active Arrow Flight SQL Connector (SERVER execution type). Client production traffic uses this port, ensuring uninterrupted access to the currently deployed connector version. Default: 5501 |
| Flight Server Pending Port | Use this setting to specify the port for the the pending (test) Arrow Flight SQL Connector (SERVER execution type). You can use this port to deploy and test a new connector version in a non-production environment before you make it available to users. Default: 5502 |
| Flight Server Active FS | Use this setting to specify the Teradata foreign server for the active Arrow Flight SQL Connector (SERVER execution type) to submit and process export queries. Default:arrow_fs |
| Flight Server Pending FS | Use this setting to specify the Teradata foreign server for the pending Arrow Flight SQL Connector (SERVER execution type) for upgrade validation and testing. Default:arrow_fs_pending |
Supported upgade scenarios: