## TL;DR
Refresh the cached table schema instead of rewriting the query: Trino caches remote table metadata, so a column dropped at the source keeps failing until the cache is invalidated or the table is re-registered in the connector. The stale schema error means Trino planned the query against a column list that no longer matches the remote table. The query text is fine; the catalog copy of the schema is old.

```text
trino query failed error "schema is stale: column dropped in remote table"
```

## Use this when
- The check or run fails with this symptom: a Trino query fails with schema is stale and a column dropped in the remote table.
- You are working on a Trino catalog over a remote or federated table whose schema changed at the source and the failure repeats on the same data or configuration.
- You need the failing rows, rule, or stage isolated before changing thresholds or code.

## Not for this skill when
- A column that was renamed rather than dropped, where queries need the new name and a cache refresh alone is not enough.
- The error text names a different tool, stage, or root cause. Match the verbatim error first and use that skill.

## Steps
1. Confirm the current remote table schema directly in the source system. Verify: the dropped column is really gone at the source
2. Find queries and views that still reference the dropped column. Verify: every dependent reference is listed before the refresh
3. Invalidate the connector metadata cache for the table, or drop and recreate the table registration where the connector requires it. Verify: Trino describes the table with the new column list
4. Update the dependent queries and views to the current schema. Verify: they plan successfully
5. Rerun the original query. Verify: it completes against the refreshed schema

## Variant phrasings
### trino schema is stale column dropped remote table
The shorter phrasing focused on the named failure.
### trino query failed schema stale error
The symptom phrasing a searcher tries next.
### trino stale schema cache refresh fix
The variant naming the failing stage or tool directly.

Compatibility: Trino 4xx releases, JDBC and metastore backed connectors with metadata caching

## Why it happens
Federated connectors cache table metadata to avoid a remote lookup per query. When the source drops a column, the cache and the real schema diverge, and Trino raises the stale schema error rather than planning against a table shape that no longer exists.

## Edge cases / pitfalls
- A view defined over the table keeps the old column list even after the cache refresh; views must be replaced explicitly.
- Short cache lifetimes hide this in development and expose it in production; align the cache settings across environments.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_z3r5WkU14trZ3jV3nT0NuQ