Federated Data - Limitations and Other Considerations When Using Federated Data Configurations

Intended audience: end-users analysts developers administrators

AO Platform: 4.4

Limitations and Other Considerations When Using Federated Data Configurations

MSOs representing data source tables that contain spatial data in the GEOM format cannot be cached (as a Cached MSO) or included in Materialized Views. The GEOM data type is not currently supported by the technology that is used by Trino to persist Cached MSOs and Materialized Views. Therefore, such MSOs with GEOM data types should retrieve data directly from their original data source via Trino.

Queries being executed against Federated Data Sources directly will generate output as AI Response Tables in Easy Answers solutions. This is caused by the fact that statistics have not been generated on the data being retrieved from multiple data sources, and therefore, curations, such as charts, maps, and other visualizations, cannot be auto-generated. See AI Response - Table. To avoid the AI Response Tables in response to Federated Data questions, consider using Cached MSOs and Materialized Views.

Although the Federated Data server technology, Trino, supports a great number of data sources with its plugin connectors, the AO Platform 4.3 release has been tested with the following:
- Snowflake
- Google BigQuery
- SAP HANA
- PostgreSQL