Skip to content

Incident detail

Possible incorrect results when Galaxy Result Set Caching is enabled

Resolved incidentMinor1 affected service

Timeline window

to

Get alerted the next time Starburst Galaxy breaks

Free email alerts for the handful of vendors you cannot afford to miss. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.

Timeline

Incident updates

Every update on the official status source, oldest to newest, exactly as it appeared there.

  1. 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.

  2. 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.

  3. Identified

    The fix is almost ready - we expect to deploy it to production late Friday (Mar 14th).

  4. Monitoring

    The fix has been deployed to production and we're monitoring the situation

  5. Resolved

    This has been resolved

Keep exploring

More from Starburst Galaxy

Neighboring incidents on Starburst Galaxy's timeline and the rest of their record on OutageDeck.