Resolved -
This has been resolved
Mar 16, 03:05 UTC
Monitoring -
The fix has been deployed to production and we're monitoring the situation
Mar 15, 01:03 UTC
Update -
The fix is almost ready - we expect to deploy it to production late Friday (Mar 14th).
Mar 14, 00:29 UTC
Identified -
The issue has been identified. There was a bug with how results are serialized to the result set cache, which threw an exception that was not handled correctly. The team is working on a fix to handle the error case.
Mar 13, 18:08 UTC
Investigating -
We are currently investigating a bug where query results are empty when result set caching is enabled on a cluster. This seems to affect certain catalog types, but not all. The team is investigating the root cause, but in the meantime if you're affected by this, please disable result set caching on your clusters.
Mar 13, 00:08 UTC