Refer to this topic for information on fixed issues and known limitations associated with Data Observability.
| Issue | Summary | Workaround | Noted on |
|---|---|---|---|
| Quoted object names in database | Observer and profile runs may fail if database objects (tables or columns) contain quotes in their names, such as 'TableName' or 'ColumnName'. | Consider renaming these objects without quotes or adopt naming conventions that avoid the use of quotes. | November 2023 |
| Freshness alerts with Redshift | Freshness alerts using Redshift are
limited because Redshift retains last modified table information for
only up to seven days, restricting alerts to daily or weekly
intervals.
|
None | November 2023 |
| Limited Profile statistics visibility | Statistics may not display immediately after a profile run, especially with a large number of tables, showing "No Statistics available". | Wait a few minutes after the profile run completes before checking statistics. Refreshing the Profiling Results page or toggling between different tables or columns can also help. The statistics for all assets will be displayed within 10 to 20 seconds. | November 2023 |
| GEOMETRY data-type in Snowflake | GEOMETRY data type columns are not supported in Profiles and Observers within Snowflake databases, leading to failures in runs and no statistics generation. | None | November 2023 |