r/redis • • 16h ago

News Redis SQL Trino 0.4.3: query Redis with SQL, connect BI tools, and join across data sources

3 Upvotes

Hi r/redis — we’ve released Redis SQL Trino 0.4.3.

If you haven’t come across the project, it’s an open-source connector that lets Trino query Redis HASH and JSON data indexed by Redis Query Engine using SQL. Applications and BI tools can connect through Trino’s JDBC interface, and you can join Redis data with other sources supported by Trino.

For example, you could query operational data in Redis from a SQL client or combine it with warehouse data without first copying everything into the warehouse.

The recent work has focused on broader SQL support, correctness, and reducing how much data moves from Redis to Trino. This release includes:

  • More SQL features: ordinary views, table and column comments, column positioning, and TRUNCATE.
  • Better query execution: more eligible filters, counts, DISTINCT counts, grouping, and ORDER BY … LIMIT work handled closer to Redis.
  • Expanded data support: nested JSON writes and additional complex, binary, and temporal types.
  • Redis Software Flex support, within the documented capability restrictions.
  • Better diagnostics: EXPLAIN information showing pushdown policy and applied operations.

Pushdown depends on whether Redis can preserve the query’s SQL semantics. Operations that need Trino execution stay there, including joins and window functions.

This version requires Trino 484 and Java 25. The release includes the plugin ZIP and a PDF user guide.

Code and getting started · Release notes and downloads


r/redis • • 32m ago

Help Have you run into Redis serving stale data after the database was updated?

1 Upvotes

I'm curious how common this is. If you use Redis as a cache in front of a database (Postgres, MySQL, etc.), have you had cases where the database had the new value but Redis kept serving the old one?

If so, I'd like to hear:

  1. What caused it? A delete that never happened, a bulk update or background job that skipped the cache, someone editing the DB directly, a race between a read and a write, a failed DEL during a network blip?
  2. How did you notice? Users, support tickets, monitoring, or by accident?
  3. How long did the stale value stick around, and how hard was it to track down?
  4. What did you change afterwards? Shorter TTLs, versioned keys, invalidating from the DB change stream, or something else?
  5. And if you've never had this problem, what do you do that avoids it?