Geospatial queries are up to 38X faster with Lakehouse//RT
From the source: Databricks Blog
Spatial SQL and spatial joins now run on Lakehouse//RT and they're up to 38X faster...
Read the full story on Databricks BlogAsk the square
The story is what was announced. If it raises a question for your team, ask the people who run this technology day to day. Your post links back to this story, so the next reader finds it too.
Recent threads in Data & Analytics
How are you handling semantic layers and metric definitions across BI tools?
dbt semantic layer, a headless BI layer, or definitions living in each dashboard tool? What has reduced the “two numbers for revenue” problem for you?
Is the lakehouse finally the default, or still a migration project?
Share where you are: fully on a lakehouse, hybrid with a warehouse, or not convinced yet, and what drove the decision.
Something wrong or out of date? Suggest a correction. We reply within 5 business days.
More from Databricks
Recent updates from Databricks, so you can tell whether this is a one-off or part of a pattern.
More in Data & Analytics
What other companies in Data & Analytics are doing. The category page shows who’s active, side by side.
