Explore >> Select a destination
|
You are here 
|
blog.panoply.io | ||
| | | | |
www.zuar.com
|
|
| | | | | Learn about data ingestion tools and methods, and how it all fits into the modern data stack through ETL/ELT pipelines. | |
| | | | |
www.talend.com
|
|
| | | | | Data modeling is the process of creating a diagram that represents your data system & defines the structure, attributes, and relationships of your entities. | |
| | | | |
www.starburst.io
|
|
| | | | | Building data lakes using AWS S3 object storage and deploy Starburst to query and analyze your big data directly where it lives. | |
| | | | |
jack-vanlightly.com
|
|
| | | In today's post I want to walk through a fascinating indexing technique for data lakehouses which flips the role of the index in open table formats like Apache Iceberg and Delta Lake. We are going to turn the tables on two key points: 1. Indexes are primarily for reads. Indexes are usually framed as read optimizations paid for by write overhead: they make read queries fast, but inserts and updates slower. That isn't the full story as indexes also support writes such as with faster uniqueness enforcement and reducing lock contention (for example, by avoiding range locks during table scans) but the dominant mental model is that indexing serves reads while writes pay the bill. 2. OTFs don't use tree-based indexes. Open-table format indexes are data-skipping ind... | ||
