Uploaded July 2026 | Updated November 2026, 13 hours ago
Querying your data, debugging a failed job, or tracking down when a value changed shouldn't require custom tooling every time.
At DevCon 6, Palantir Software Engineer Daniel Falbo announces three updates: SQL Studio reached general availability as a dedicated, low-latency SQL environment that runs on warm, managed compute pools and dynamically routes queries to the most appropriate engine, including non-Spark options like Trino; incremental job debugging now produces standardized, detailed failure reports across every resource and compute type; and time travel, paired with data bisect, lets you inspect a table at any prior point and automatically locate the exact moment a given value changed.
Querying your data, debugging a failed job, or tracking down when a value changed shouldn't require custom tooling every time.
At DevCon 6, Palantir Software Engineer Daniel Falbo announces three updates: SQL Studio reached general availability as a dedicated, low-latency SQL environment that runs on warm, managed compute pools and dynamically routes queries to the most appropriate engine, including non-Spark options like Trino; incremental job debugging now produces standardized, detailed failure reports across every resource and compute type; and time travel, paired with data bisect, lets you inspect a table at any prior point and automatically locate the exact moment a given value changed.










