Limitations_And_Issues

Please consult our FAQ for answers to commonly asked questions.

1. Federated Identity Not Always Populated - Certain call patterns will result in calls to your UDF or Connector which lack a principal arn or contain a principal arn of 'unknown'.
2. There is a known issue with the jdbc connector that limits it to 64mbps scan rate for tables/engine which are not partitioned. Using partitioned tables unlocks significantly greater parallelism but unpartitioned tables appear to be running into some performance limit related to the JDBC driver (or its config). We are aware and investigating.
3. When using the JDBC Connector with Redshift, filters on columns of type 'char' may return fewer rows than they should. For more details please see issue #62.
4. If you are seeing slow performance or excessive throttling while using the cloudwatch-metrics connector, we recommend limiting you Lambda function to a concurrency of 2 by settings it to use reserved capacity.
5. DDL statements (show tables, describe catalog.database.table) will not work with databases or tables that contain special characters.
6. Using connectors or UDFs in Views are not supported.
7. Lake Formation row level filtering is currently not a supported feature of UDFs.