René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"`TrinoOfflineStore` does not cleanup temporary tables","articleBody":"## Expected Behavior\n\nTemporary entity tables created during `get_historical_features()` should be cleaned up after the retrieval job completes, consistent with how BigQuery, Redshift, and Athena handle it.\n\n## Current Behavior\n\nEach call to `get_historical_features()` with a pandas DataFrame `entity_df` creates a permanent table (`{catalog}.{dataset}.feast_entity_df_\u003cuuid\u003e`) that is never dropped, leaking tables in the Trino catalog indefinitely.\n\n## Steps to reproduce\n\n1. This is a known issue in `TrinoOfflineStore` https://github.com/feast-dev/feast/blob/master/sdk/python/feast/infra/offline_stores/contrib/trino_offline_store/trino.py#L486 \t\n\n### Specifications\n\n- Version: 0.50+\n- Platform: Any\n- Subsystem: `TrinoOfflineStore`\n\n## Possible Solution\n\nRefactor `TrinoRetrievalJob` to accept a context manager (`query_generator`) instead of a plain query string, following the pattern used by BigQuery/Redshift/Athena, and add a `DROP TABLE IF EXISTS` in the `finally` block.","author":{"url":"https://github.com/mattiamatrix","@type":"Person","name":"mattiamatrix"},"datePublished":"2026-04-21T14:50:48.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/6306/feast/issues/6306"}