Review the following limitations and usage considerations before you deploy or use the Arrow Flight SQL Connector (SERVER execution type).
| No. | Limitation |
|---|---|
| 1 | An "Interval field overflow" error can occur when you run SELECT queries on certain INTERVAL DAY TO SECOND columns with a JDBC precision/display size of 17. Workaround: Add /* direct_jdbc_call=true */ to the SQL query. This workaround can reduce query performance |
| 2 | SQL statements that reference ST_GEOMETRY, MBB, MBR, DATASET, or PERIOD columns fall back to direct JDBC queries, which can significantly affect query performance. SQL statements that include /* direct_jdbc_call=true */, contain a top-level ORDER BY clause or CTE, or use a HELP queries also fall back to direct JDBC queries |
| 3 | If you change the active or pending port for the Arrow Flight SQL Connector (SERVER execution type), the connector restarts and temporarily interrupts service. Before you apply the change, Viewpoint and Console display a warning |
| 4 | At this time, you can use transactions only for operations that run on a single driver node. You cannot use transactions across multiple driver nodes |
| 5 | You can create a pending ArrowFlightServerConnector version only if a pending Fabric version already exists |
| 6 | The current release supports Azure and GCP deployments with an Application Load Balancer |
| 7 | Substrait query plan support depends on Teradata Database support and is not currently available |