Trino
PulseAugur coverage of Trino — every cluster mentioning Trino across labs, papers, and developer communities, ranked by signal.
6 day(s) with sentiment data
-
Data lake loses 40TB after Spark table management error
A data lake experienced a catastrophic loss of 40TB of data due to a misunderstanding of table management in a Spark environment. A routine cleanup script, intended to delete old staging tables, instead purged data from…
-
Spark's universal adoption leads to performance failures and cost overruns
A data platform team's decision to standardize on Spark for all workloads resulted in significant performance issues and cost overruns. BI dashboards experienced high latency, a fraud-scoring pipeline missed its SLA, an…
-
AI agent's database deletion prompts new SQL safety tool, Lagaam
An AI agent's accidental deletion of a production database, which occurred in April and involved the tool Cursor, highlighted the critical need for robust safety measures beyond just model capabilities. The incident, wh…
-
Databricks introduces APIs to prevent catalog lock-in for lakehouses
Databricks has introduced new REGISTER and UNREGISTER APIs to enhance data portability within lakehouse architectures. These APIs allow tables to be moved between different catalogs without duplicating data or metadata,…
-
Databricks enhances Apache Iceberg governance with read restrictions
Databricks has introduced new features for Apache Iceberg, focusing on enhancing data governance across various engines. The updates include read restrictions and catalog labels, which aim to make governance policies mo…
-
Databricks Unity Catalog emphasizes user control over data storage
Databricks has detailed its strategy for managing data storage in Unity Catalog, emphasizing user control and open formats. The platform allows users to store managed table data in their own cloud storage accounts, such…
-
Databricks enhances Open Lakehouse governance with Apache Iceberg specs
Databricks has introduced new specifications for Apache Iceberg, focusing on read restrictions and catalog labels to enhance governance within the Open Lakehouse architecture. These advancements aim to make data governa…
-
dbt and SQLMesh co-exist on self-hosted lakehouse via Nessie REST
A technical comparison details the challenges and solutions encountered when running dbt and SQLMesh simultaneously on a self-hosted lakehouse environment. The author outlines a specific stack including PostgreSQL, Seaw…