Definition
Controls how def~tables are exposed to queries
Hudi supports the following views of stored data
- def~read-optimized-queryQueries see the latest snapshot of the def~table as of a given commit / compaction def~instant-action; exposes only the base / columnar files in latest file slices to the queries and guarantees the same columnar query performance compared to a non-hudi columnar def~table.
Following table summarizes the trade-offs between the different def~query-types.
Trade-off def~read-optimized-query def~snapshot-query Data Latency Higher Lower Query Latency Lower (raw base / columnar file performance) Higher (merge base / columnar file+ row based delta/log files) - def~incremental-queryQueries only see new records written to the def~table, since a given commit /delta-commit def~instant-action; effectively provides change streams to enable incremental data pipelines.
Following table summarizes the trade-offs between the different def~query-types.
Trade-off | def~read-optimized-query | def~realtime-view |
---|---|---|
Data Latency | Higher | Lower |
Query Latency | Lower (raw base / columnar file performance) | Higher (merge base / columnar file+ row based delta/log files) |
Related concepts
- def~read-optimized-query
- def~incremental-query
- def~realtime-view
- def~timeline
- def~table
- def~commit
- def~table-type